Logging traces allows you to save user actions within the respective application areas in the system long-term.
In the application area Reporting, Planning and OLAP Technology, you can log selected executions of queries and the subsequent query navigations, as well as particular actions, in the planning modeler.
You can trace the following:
You can rerun and control traces, as well as use them to define automatically executable regression tests. For more information, seeTrace Tool Environment.
In the application area Reporting, Planning and OLAP Technology, you can jump directly to thequery monitor using the trace tool.
A successful trace logging comprises the following steps:
It is irrelevant if the activation or deactivation and the execution of the actions takes place in the same mode, or in two different modes.
During activating and deactivating a trace logging, the following cases are supported:
You can determine for each user, if, in addition to logging user actions, they are to be activated or deactivated for generating tests.
Activating the Trace Logging
If, as an administrator, you want to activate another user, enter this name in the Trace User field.
If, as an administrator, you want to activate a user whose name you have entered in the Trace User field, choose Activate.
As a result of your activation, the system displays the activated user as well as the time of activation and the selection for the test generation in the user table.
User Interaction
Deactivating the Trace Logging
If you want to deactivate yourself, or as an administrator, you want to deactivate another user, select the corresponding entry in the user table and choose Deactivate.
If the current session ends during the logging of user actions, the system automatically shuts the trace logging. Therefore, for example, executing the query monitor again, or refreshing the Web browser window interrupts logging. If further interactions take place, a new trace occurs.
If, on the contrary, in a second session, the user for the trace logging is deactivated and then reactivated, and this then executes further interactions in the first session, a new trace occurs.