The basic permissions for triggering processes are granted to the logged in user by the Allow to trigger any events from the frontend program feature (Common_TriggerEvents).
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). If the object event is assigned a program function (QBMEventHasFeature table), 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 executing 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 executed. 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 execute 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 112: Simulation color code
| Grey |
Process step not generated. |
| Blue |
Process step successfully generated. |
NOTE: Double-click on a successfully generated process step to display properties and parameters with the simulated data in the edit view.
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.
NOTE: Before you compile a process, you should carry out a validity check of the process and process steps.
To check a process
-
In the Designer, select the process in the Process Orchestration category.
-
Start the Process Editor with the Edit process task.
-
Select Process | Error checking.
The result of the check is displayed in the Validity check view and is retained until the next check.
Table 113: Icons used in the validity check
 |
No errors found. |
 |
Errors. |
 |
Warning, Information. |
TIP:
-
Process or process step controls are highlighted in yellow to indicate a warning or information. If errors occur, the process or process step controls are highlighted in red.
-
Double-click an error message in the Validity check view to jump to the corresponding entry in the process.
Table 114: Possible reasons for process failure
|
Errors |
The process does not have a name.
No base object given.
The given generating condition does not correspond to required notation (value =). |
|
Warning |
The process does not have a base process step.
The process has no event. |
|
Information |
The option Do not generate is set. |
Table 115: Possible reasons for process step failure
|
Errors |
The process step does not have a name.
No process task assigned.
The given generating condition does not correspond to required notation (value =).
No execution server specified (server selection script or server mask).
Process step name not unique.
Process step has no parameters.
The given parameter value does not correspond to required notation (value =). |
|
Warning |
Process step not linked into the process. |
Related topics
.