Identity Manager 8.1 - Configuration Guide

Allocating parameter values

Define value templates in VB.Net syntax. The following statements can be used for allocating values:

• None
• Columns of an object or columns of an object connected by a relation

  Syntax:

  Value = $<column name>:<data type>$

  Value = ${FK(<foreign key>).}<column name>:<data type>$

  Example:

  Value = $Lastname$

  Value = $PasswordNeverExpires:bool$

  Value = $FK(Ident_Domain).Description$

• Parameter from the optional parameter collection

  Syntax:

  Value = $PC(<parameter name>)$

  Example:

  Value = $PC(SRCUID_Application)$

• Out-parameter

  Parameters of the OUT or INOUT type are parameters that a process component can use to output a value. This value is then available in all subsequent process steps in the process and can be used as a value for parameters of the IN type.

  When you use OUT parameters, you need to take care that these contain data at runtime. Alternatively, when the text is processed "&OUT(<parameter name>)&" is entered, which means that the variable will not be replaced.

  Syntax:

  Value = "&OUT(<parameter name>)&"

  Example:

  Value = "&Out(FileSize)&"

• Global variables allocated by the set-up program

  Syntax:

  Value = Variables("<variable name>")

  Example:

  Value = Variables("GENPROCID")

  Value = Variables("FULLSYNC")

• The local variables of the process step or of the process generated by the pre-script

  Syntax:

  Value = values("Name")

  Example:

  Value = Values("FirstHomeServer")

• Querying Configuration Parameters

  The full path for the configuration parameter must always be entered.

  Syntax:

  Value = Session.Config().GetConfigParm("<full path>")

  Example:

  Value = Session.Config().GetConfigParm("TargetSystem\ADS\RestoreMode")

• VB.Net

  Enter any statements in VB.NET syntax.

Related Topics

• Properties of process step parameters
• Using scripts

Events for processes

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.

Other events are provided by the Customizer. These events are described in the Customizer documentation. You can define other custom events to trigger processes.

Detailed information about managing permissions and executing processes via program functions can be found in the One Identity Manager Authorization and Authentication Guide.

Detailed information about this topic

• Creating events

Creating events

To create an event

1. Select the process in the Process Orchestration category in the Designer.
2. Start the Process Editor using Edit process.
3. Click on the element for the process in the process document.
4. Select the Events view and click .
5. Enter the following information.

   Table 125: Event properties

   Property	Description
   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.

Related Topics

• Logging process information during process handling

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.

To generate a process for testing

1. Select the process in the Process Orchestration category in the Designer.
2. Start the Process Editor using Edit process.

1. Start the simulation wizard with the Process | View | Simulation view menu item.
2. On the start page of the wizard, click Next.
3. 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.
4. On the Select object page, select the object for which the event is to be simulated.
5. (Optional) On the Change object properties page, change the object properties.
6. (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).

7. (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.
8. (Optional) On the Define preprocessor directives page, select the preprocessor conditions to be taken into account when the process is generated.
9. 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 126: Simulation Color Code

   Color	Meaning
   Gray	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.