Identity Manager 9.3 - Configuration Guide

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 45: Event properties
Property	Description
Object event	Name of the object event. The Object event drop-down 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.
1. In the Designer, select the event in the Process Orchestration > Object events.
2. Select the View > Select table relations menu item and enable the QBMEventHasFeature table.
3. In the edit view, select the Program function view and select the program function.

Related topics

Creating events for processes

Simulating process generation

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 46: Simulation color code

Color Meaning

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.

Table 46: Simulation color code
Color	Meaning
Light gray	Process step not generated.
Blue	Process step successfully generated.

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.

Checking the validity of a process

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 the Process > Error checking menu item.

The result of the check is displayed in the Validity check view and is retained until the next check.

Table 47: Icons used in the validity check

Icon Meaning

No errors found.

Errors.

Warning, Information.

Table 47: Icons used in the validity check
Icon	Meaning
	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 48: Possible reasons for process failure
Error Category	Possible cause
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 49: Possible reasons for process step failure
Error Category	Possible cause
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 executing 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 =). The two process step properties Ignore errors and Wait mode on error are set. The process step is never repeated because all errors are ignored. The two process step properties Ignore errors and Stop on error are set. The process step never goes into a FROZEN state because all errors are ignored. The two process step properties Ignore errors and Split processing are set. The split error is never processed.
Warning	Process step not linked into the process. The two process step properties Split processing and Wait mode on error are set and no retries are defined. If errors occur, the process step is stopped immediately and therefore processing does not split off.

Please select your product:

To serve you better, please complete the Purpose of your Chat:

Recommended Solutions for Your Problem

Identity Manager 9.3 - Configuration Guide

Creating events for processes

Related topics

Permissions for triggering processes

Related topics

Simulating process generation

Checking the validity of a process

Related topics