When the simulation ends, the recorded modifications are loaded and displayed in the Manager as a protocol.
Table 2: Logging simulation data
Overview |
This gives you an overview of which actions the applied changes will trigger.
You can export the simulation data and display the report. |
Number of applied changes for each action. |
DBQueue |
The DBQueue log shows the following information. You can show the additional information from the context menu. |
Operation |
Calculation tasks to be run. |
Sort order |
Sort order to process the calculation task. |
Process ID |
Unique process ID. |
Object |
Unique object ID. |
Child object |
Unique ID of the child object. |
Generated process |
Shows processes and process steps generated during simulation due to the changes. The individual properties of the processes and process steps are also displayed with their actual values. |
Process |
Name of the generated process. |
Process steps |
Name of the generated process step. |
Property |
Processes property or process step property. |
Value |
Property value. |
Trigger changes |
Shows all changes made to objects that have been triggered during the simulation. |
Table |
Display text of the table to which the record belongs. This is used to group the objects. |
Object |
Object affected by the change. |
Column |
Column that was changed. |
Old value |
Column value before the change. |
New value |
Column value after the change. |
Changed objects |
Shows objects and their properties if they were affected by the changes made during simulation. |
Table |
Display text of the table to which the record belongs. This is used to group the objects. |
Object |
Object affected by the change. |
Column |
Column that was changed. |
Old value |
Column value before the change. |
New value |
Column value after the change. |
Rule evaluation |
During the simulation, the system recalculates all the rules that are affected by the changes. New rule violations and rule violations that no longer apply as a result of the recalculation are displayed. |
Employee |
Employee who has newly violated the rule or is no longer violating the rule for the first time. |
Rule violation |
Type of change (rule no longer violated or new rule violation) and the affected rule. |
Description |
Description of the rule violation. |
Related topics
To export and display the simulation data as a report:
- In the simulation log, select the Overview view.
- Click the button next to the list of actions.
- Use the file browser to select the directory path for the report and enter a file name for the report.
- To generate the .PDF report, click Save.
- Click Yes to show the report now.
Related topics
As a rule, deferred deletion of user accounts by processes is defined in the table definitions as 30 days. After the deferred deletion limit has expired, the user accounts are deleted from the database In addition, in the Manager, you can create, change, or delete an object at a specified point in time. The DBQueue Processor checks whether scheduled operations exist. When the scheduled time is reached, the operation is executed by the One Identity Manager Service.
To execute operations at a specified point in time
-
In the Designer, check if the Common | DeferredOperation configuration parameter is set. Check the value of the configuration parameter and adjust it if necessary. Permitted values are:
-
1 (default): In the Manager, you can schedule the time of execution for creating, changing, or deleting an object.
-
0: Deferred deleted operation are carried out, such as, deferred deletion of user accounts. It is not possible to schedule the time of execution in the Manager.
You must recompile the database if you enable or disable the configuration parameter.
-
In the Designer, check the Common | DeferredOperation | AllowUpdateInInsertMode configuration parameter and adapt it to the required behavior.
-
If this configuration parameter is disabled, an error occurs during processing if you try to insert an object that already exists in the database.
-
If this configuration parameter is enabled, when you insert an object that already exists in the database, the object is updated.
-
In the Designer, check the Common | DeferredOperation | IgnoreMissingOnDelete configuration parameter and adapt it to the required behavior.
-
If this configuration parameter is disabled, an error occurs during processing if you try to delete an object that no longer exists in the database.
-
If this configuration parameter is enabled, missing objects are ignored during deletion.
Detailed information about this topic