Chat now with support
Chat with Support

Identity Manager 8.1 - Configuration Guide

About this guide One Identity Manager software architecture Customizing the One Identity Manager default configuration Adjusting the One Identity Manager base configuration One Identity Manager schema basics Editing the user interface
Object definitions for the user interface User interface navigation Forms for the user interface Statistics in One Identity Manager Extending the Launchpad Task definitions for the user interface Applications for configuring the user interface Icons and images for configuring the user interface Using predefined database queries
Localization in One Identity Manager Process orchestration in One Identity Manager
Setting up Job servers in Designer Configuring the One Identity Manager Service Handling processes in One Identity Manager
Tracking changes with process monitoring Conditional compilation using preprocessor conditions Scripts in One Identity Manager Reports in One Identity Manager Adding custom tables or columns to the One Identity Manager schema Web service integration SOAP Web Service One Identity Manager as SPML provisioning service provider Processing DBQueue tasks Appendix: Configuration files of the One Identity Manager Service

Accessing columns of an object connected by a relation

The only relation currently permitted is the foreign key relation.

Syntax

$FK(<foreign key column>).<column name>:<data type>$

Example for use in templates:

An Active Directory user’s first name should based on the assigned employee. The template for ADSAccount.Givenname is:

Value = $FK(UID_Person).Firstname$

Related Topics

Accessing the old column value

Syntax

$columnname[o]$

Example for use in process step parameters:

Optional process step parameters are not generated if the value is set to Nothing or not assigned in the value template. This makes it possible to limit the number of parameters for target system components. If such a value should be cleared, an empty string should be transferred instead of Nothing.

A value template may look like this:

If $Lastname[o]$ <> $Lastname$ Then

Value = $Lastname$

End If

NOTE: For some standard columns such as XDateInserted, XDateUpdated, XUserInserted, XUserUpdated, XOrigin, XIsInEffect and XMarkedForDeletion , the new values are only determined after saving the object. This means that when processing the templates, the new column value is always the same as the old value (e.g. $XDateUpdated[o]$ = $XDateUpdated$).

Related Topics

Accessing the display value of a column

When a display value for a column is created, the properties Multilingual (IsMultiLanguage) and List of permitted values (LimitedValues) are resolved.

Syntax

$columnname[D]$

Example of use:

A list of permitted values is defined for the restriction type of the IBM Notes server restrictions.

PrivateList=Run Personal Agent RestrictedList=Run Restricted Agent UnrestrictedList=Run Unrestricted Agent

If a server restriction has the value PrivateList, the value Run Personal Agent is displayed on the information form.

Example for use in templates:

The display value for the server restriction should be formatted from the name of the IBM Notes user and the display value of the restriction type.

Value = vid_Left($FK(UID_NotesUser).FullName1st$,39) & " [" & vid_Left($NotesAgentMgrType[D]$, 22) & "]"

Related Topics

Accessing references in comments

The preprocessor also interprets references that are embedded in comments, for example, $Lastname$. Referencing a column in a script comment results in the script being run when the column value is changed.

Example for use in templates:

An employee’s starting date is filled with a template. This template should run when the employee’s surname changes. The template for Person.Entrydate is therefore:

'$Lastname$

Value = Date

Related Topics
Related Documents