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

Testing the Existence of Certain Database Entries

NOTE: The test should take place without taking access permissions into account.

Syntax

Session.Source().Exists("<Tablename>","<WhereClause>")

Example

Session.Source().Exists("Person", "CentralAccount = '" & accnt & "' and uid_person <> '" & uid_person & "'")

Related Topics

Querying Session Object Global Variables

Global variables are allocated by the set up program. All environment variable and custom variables defined for the session object can be used in addition to predefined variables. Custom session variables can be defined, for example, through scripts, methods or customizers.

NOTE: If a custom session variable is defined, it must be removed again afterward. Otherwise it remains for the rest of the session and, in certain circumstances, the wrong processes can be generated.

Syntax:

Variables("<Variable name>")

Example for use in process step parameters:

Value = Variables("GENPROCID")

Value = CBool(Session.Variables("FULLSYNC"))

Table 268: Permitted Predefined Global Variables
Variable Meaning

EnvUserName

 

 Name of user to be authenticated in the environment, for example, "Domain\User" in Active Directory.

FullSync

 

 Variable is set by all synchronizers ("True", "False").
GenProcID Unique Process ID number
LogonUser DialogUser.Username of the currently logged in user.
DialogUserUID DialogUser.UID_DialogUser of the logged in user.
UserName Name displayed in XUserInserted or XUserUpdated.
UserUID Logged in user’s UID_Person, if user related authentication is being used.
ShowCommonData Specifies whether system data is shown (1) or not shown (0). The variable is evaluated in Designer by the program setting "Show system information".
Feature_<Featurename> Queries additional program functions (DialogFeature) that are available for the user. The value is "1" when the program function is available, otherwise the variable is not set.

ManageOutstandingOperation

This variable is used to differentiate between executing operations during post-processing of outstanding objects in target system synchronization. Permitted values are "Delete", "DeleteState" and "Publish".

Related Topics

Using #LD Notation

#LD notation is used for displaying language dependent information. #LD notation is mainly used in process tracking and processing notification, but it can also be used in scripts that are stored in the script library.

Table 269: Using #LD Notation
Context Table.column
Process tracking Job.ProcessDisplay - based on DialogProcessStep.Displayname
JobChain.ProcessDisplay - based on DialogProcessChain.Displayname
JobEventgen.ProcessDisplay - based on DialogProcess.Displayname
Process handling notification Job.NotifyAddress and Job.NotifyAddressSuccess
Job.NotifyBody and Job.NotifyBodySuccess
Job.NotifySender and Job.NotifySenderSuccess
Job.NotifySubject and Job.NotifySubjectSuccess
JobRunParameter.ValueTemplate (only process components: MailComponent)
Templates DialogColumn.Template and DialogColumn.CustomTemplate
Formats DialogColumn.FormatScript and DialogColumn.CustomFormatScript
Method definitions DialogMethod.MethodScript
Insert values DialogObject.InsertValues, DialogTable.InsertValues, DialogTree.ListInsertValues and DialogSheet.InsertValues
Selection scripts DialogTable.SelectScript and DialogObject.SelectScript
Process generating scripts JobChain.GenCondition and Job.GenCondition
JobChain.PreCode and Job.PreCode
Job.ServerDetectScript
Syntax

Value=#LD[<language>](<key>,{<parameter>}*)#

where:

<Language>

 Optional language or culture for the output.

<Key>

 Basis string with place holder. The place holder syntax corresponds to a format place holder in .Net ({0} to {9})

<Parameter>

 Parameter for replacing the place holder (comma delimited)
Related Topics

Example for Use in Process Tracking

A change is made to an employee (e.g. because they have moved). The process information for the event "Update" on the base object "Person" could be formulated as:

Value = #LD("Change properties of employee {0}.", $Internalname$)#

with:

Internalname = JSmith

results in the following output text in the process view:

Änderung der Daten der Person JSmith.

NOTE: Prerequisite for language dependent representation is the definition of the corresponding caption for displaying the text in the active languages.

The captions for language dependent text are entered in DialogMultiLanguage when the script is compiled. The key (column Entrykey), the language (column Ident_Language) and the language dependent replacement (column EntryValue) are entered in this table. The key should be in the corresponding default language. If a language caption has not been entered, the key is used as the display text. Use the Language Editor to add translations for the captions in other languages.

In order to display the language dependent process information for the example above, it could be formulated as follows:

Display text caption in the DialogMultiLanguage table:

Language

Key

Value

English

Changed properties of employee {0}.

Changed properties of employee {0}.

Language

Key

Value

German

Changed properties of employee {0}.

Änderung der Daten der Person {0}.

Template for the process information:

Value = #LD("Change properties of employee {0}.", $Internalname$)#

with:

Internalname = JSmith

results in the following display text in the process view:

System's user language:

German

English

Output:

Änderung der Daten der Person JSmith.

Changed properties of employee JSmith.

Related Topics
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating