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 meta values of the local object

Syntax

$[IsLoaded]:Bool$

Table 148: Meta Values and their Meaning
Meta value Meaning
IsLoaded This value specifies whether the object is loaded from the database.
IsChanged This value specifies whether the object is altered when it is loaded from the database.
IsDifferent This value specifies whether the new value is different from the old value. You can access to the column through: Columnname[C].
IsDeleted This value specifies whether the object is marked for deletion.
Related Topics

Using base. Object

With base., the object that is currently loaded is always accessed. The base. object can be used in tasks, selection scripts for object definitions and insert values. However, the base. object cannot be used in templates, formatting scripts and processes.

Syntax
  • Simple value assignment

    Base.PutValue("<column>", <value>)

  • Value assignment with variable replacement (value must be a character string)

    Base.PutValue("<column>", context.Replace(<value>))

Example

Base.PutValue("IsForITShop", 1)

Base.PutValue("UID_ADSContainer", context.Replace("%cont%"))

Calling functions

Functions are stored in the script library (DialogScript table).

Example of a function in the script library

Public Function BuildInternalName(ByVal Firstname As String,ByVal Lastname As String) As String

BuildInternalName = Lastname & Firstname

End Function

Using the function in a template on Person.Internalname

Value = BuildInternalName($Firstname$, $Lastname$)

Pre-scripts for use in processes and process steps

Pre-script code is code that is executed before other scripts are run. You can define process specific variables. Process specific variables are local data spaces when a process is generated. They are used for determining values on a once-off basis within a pre-script, which can then be made further use of within the processes and their processes steps, for example, in generating conditions, server selection scripts or in the parameters.

NOTE: It is recommended only to set process specific variables in the pre-script and to have read access to them during further usage.

Syntax in the pre-script of a process

values("Name") = "value"

Usage in the process and process step code sections

Value = values("Name")

Related Topics
Related Documents