Chat now with support
Chat with Support

Identity Manager 8.0 - Configuration Guide

One Identity Manager Software Architecture Working with the Designer Customizing the One Identity Manager Default Configuration Checking Data Consistency Compiling a One Identity Manager Database Working with Change Labels Basic System Configuration Data
One Identity Manager Authentication Module Database Connection Data Configuration Parameters for System Configuration Setting up the Mail Notification System Enabling More Languages for Displaying and Maintaining Data Displaying Country Information Setting Up and Configuring Schedules Password Policies in One Identity Manager Reloading Changes Dynamically TimeTrace Databases Machine Roles and Server Functions Files for Software Update Operating Systems in Use System Configuration Reports Using Predefined Database Queries Managing Custom Database Objects within a Database
The One Identity Manager Data Model Granting One Identity Manager Schema Permissions Working with the User Interface
Object definitions for the User Interface User Interface Navigation Forms for the User Interface Statistics in the 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 Language Dependent Data Representation
Process Orchestration in One Identity Manager
Declaring the Job Server One Identity Manager Service Configuration Handling Processes in the One Identity Manager
Tracking Changes with Process Monitoring Conditional Compilation using Preprocessor Conditions One Identity Manager Scripts Maintaining Mail Templates Reports in the One Identity Manager Custom schema extensions Transporting One Identity Manager Schema Customizations Importing Data Web Service Integration SOAP Web Service One Identity Manager as SPML Provisioning Service Provider Searching for Errors in the One Identity Manager Processing DBQueue Tasks One Identity Manager Configuration Files

Using Dollar ($) Notation

NOTE: Dollar notation is used to access object properties in One Identity Manager.

If you want to user dollar notation in scripts with it representing access to column names, the character must be doubled to mask.

Example:

In Windows PowerShell scripts, instead of:

theScript.AppendLine("foreach ($Domain in $Domains)")

use:

theScript.AppendLine("foreach ($$Domain in $$Domains)")

If you are using dollar ($) notation you need to ensure that the value is allocated the correct data type. Dollar notation returns a "String" type as default. If another data type is given it is internally converted with "ToString".

Permitted data types are:

Binary

Bool

Byte

Date

Decimal

Double

Int

Long

Short

String (default)

Text

Detailed information about this topic

Accessing Local Object Columns

Syntax

$<column name>:<data type>$

Example for use in templates:

The Active Directory user display name should comprise of the first and last name of the Active Directory user. The template for ADSAccount.Displayname is:

If $Givenname$<>"" And $Surname$<>"" Then

Value = $Surname$ & " " & $Givenname$

ElseIf $Givenname$<>"" Then

Value = $Givenname$

ElseIf $Surname$<>"" then

Value = $Surname$

End If

If an employee is disabled, the leaving date should be set. The template for Person.Exitdate is:

If $IsInActive:bool$ Then

Value = Date.Today

End If

Related Topics

Accessing Object Columns 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 the value template is not assigned. This makes it possible to limit the number of parameters for target system components. If such a value should be emptied then an empty string should be given instead of "nothing".

A value template may look like this:

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

Value = $Lastname$

End If

Related Topics
Related Documents