Define value templates in VB.Net syntax. The following statements can be used for allocating values:
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$
Syntax:
Value = $PC(<parameter name>)$
Example:
Value = $PC(SRCUID_Application)$
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)&"
Syntax:
Value = Variables("<variable name>")
Example:
Value = Variables("GENPROCID")
Value = Variables("FULLSYNC")
Syntax:
Value = values("Name")
Example:
Value = Values("FirstHomeServer")
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")
Enter any statements in VB.NET syntax.
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.
Event | Comment |
---|---|
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 time of execution of a deferred operation is reached. |
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.
To create an event
Property |
Description |
---|---|
object event |
Name of the object event. The Object event menu displays the object events of the table specified in the process.
|
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. |
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:
|
To generate a process for testing
|
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). |
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.
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. |
|
TIP:
|
© 2021 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy