Events are defined to assign processes to objects. Processes cannot be generated until a link has been created between object, event, and process. The following predefined events are available. These are described in the following table.
Table 78: Predefined events
|
Insert |
Event created when an object is created. Available for all objects. |
|
Update |
Event created when an object is changed. Available for all objects. |
|
Delete |
Event created when an object is deleted. Available for all objects. |
|
Execute |
The event is triggered by the DBQueue Processor when the activation time of a deferred operation is reached. |
|
Assign |
The event is triggered when many-to-many assignments are added. |
|
Remove |
The event is triggered when many-to-many assignments are removed. |
Other events are provided by the Customizer.You can define other custom events to trigger processes.
Detailed information about this topic
If the object event is assigned a program function, users that own this program function by permissions group, can trigger the object event and therefore the process, irrespective of their permissions. Detailed information about managing permissions and running processes with program functions can be found in the One Identity Manager Authorization and Authentication Guide.
To create an event
-
In the Designer, select the process in the Process Orchestration category.
-
Start the Process Editor with the Edit process task.
-
Click on the element for the process in the process document.
-
Select the Events view and click 
.
-
Enter the following information.
Table 79: Event properties
|
Object event |
Name of the object event.
The Object event menu displays the object events of the table specified in the process.
-
Select an existing object event.
- OR -
-
Click and enter the name of the new object event. |
|
Sort order |
Specifies the sort order in which the processes are generated if multiple processes refer to the same event of the base object.
Processes with a lower sort order are generated before processes with a higher sort order. |
|
Event process information |
VB.Net expression for displaying the display name in the process view. |
-
(Optional) Assign a program function to the object event.
-
In the Designer, select the event in the Process Orchestration > Object events.
-
Select the View > Select table relations menu item and enable the QBMEventHasFeature table.
-
In the edit view, select the Program function view and select the program function.
Related topics
The basic permissions for triggering processes are granted to the logged in user by the Common_TriggerEvents program function.
In One Identity Manager, triggering of events on stored processes is linked to the permissions concept. Users can only trigger events on objects like this if they own edit permissions for them. This can lead to table users who only have viewing permissions not being able to trigger additional events for processes.
In this case, it is possible to connect the object events (QBMEvent table) with a program function (QBMFeature table). An event (JobEventGen table), which is defined for a process, is linked with an object event (JobEventGen.UID_QBMEvent column). The object events are linked to a program function (QBMEventHasFeature table). Users with this program function can trigger the object event and therefore the process too independent of their permissions.
TIP: The Common_TriggerSpecificEvents program function allows you to trigger specific events from the front-end. You can assign this program function to custom object events that any user can trigger. The program function is allocated to the QBM_BaseRigt permissions group.
Detailed information about managing permissions and running processes with program functions can be found in the One Identity Manager Authorization and Authentication Guide.
Related topics
You can use simulation to test whether a selected process can be generated successfully or whether the syntax for passing parameters is correct. This makes it easier to alter processes if necessary.
NOTE:
-
The Do not generate option is taken into account when you simulate a process. Disable this option for process simulation.
-
The assemblies generated are saved locally on the workstation on which the simulation is run. A simulation does not, therefore, have any effect on other users.
To generate a process for testing
-
In the Designer, select the process in the Process Orchestration category.
-
Start the Process Editor with the Edit process task.
-
Start the simulation wizard with the Process > View > Simulation view menu item.
-
On the start page of the wizard, click Next.
-
On the Select event page, select the event for which the process is to be generated and specify the database connection for the simulation. Select Designer Database or Main database.
-
On the Select object page, select the object for which the event is to be simulated.
-
(Optional) On the Change object properties page, change the object properties.
-
(Optional) On the Define parameter list page, enter the parameters for the parameter collection. You can run the following actions:
-
Load process steps: For the selected process, all elements of the parameter collections for all process steps are loaded.
-
Insert: Insert individual parameters for the simulation. Enter the parameter name and parameter value.
-
Delete: Delete individual parameters for the simulation.
NOTE: For processes generated with parameter collections, you must specify the parameters and the values to be passed (for example, the SourceDir parameter for copies of profiles or the ConfigName parameter for loading a target system). No parameter collection is used for processes generated for the default events (insert, update, delete).
-
(Optional) On the Define connection variables page, specify the session object global variables to use for the simulation. Click Insert and enter the variable name and the value.
-
(Optional) On the Define preprocessor directives page, select the preprocessor conditions to be taken into account when the process is generated.
-
To start the simulation, click Finish on the last page of the wizard.
The simulation process can take some time. After the simulation is complete the generated process is shown in the Process Editor. The process steps are shown in color depending on the generation result.
Table 80: Simulation color code
|
Light gray |
Process step not generated. |
|
Blue |
Process step successfully generated. |
NOTE:
Double-click on a successfully generated process step in the edit window to display properties and parameters with their specific values.
You can copy parameters values to the clipboard with Ctrl + C.
TIP:
-
You can swap between the edit view and the simulation view using the Process > View menu to post-process the processes.
-
For every simulation, an entry is created in the 
toolbar of the Process Editor, which you can use to rerun the simulation without having to specify the simulation data again.
-
To display the process generation protocol, select the Process > View > Process generator log menu item.
