Chat now with support
Chat with Support

Identity Manager 9.2.1 - Configuration Guide

About this guide One Identity Manager software architecture Customizing the One Identity Manager default configuration Customizing the One Identity Manager base configuration One Identity Manager schema basics
Overview of the One Identity Manager schema Table types and default columns in the One Identity Manager data model Notes on editing table definitions and column definitions Table definitions Column definitions Table relations Dynamic foreign key Supporting file groups
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
Mapping processes in One Identity Manager Setting up Job servers
The One Identity Manager Service functionality Tracking changes with process monitoring Conditional compilation using preprocessor conditions Scripts in One Identity Manager
Visual Basic .NET scripts usage Notes on message output Notes on using date values Tips for using PowerShell scripts Using dollar ($) notation Using base objects Calling functions Pre-scripts for use in processes and process steps Using session services Using #LD notation Script library Support for processing scripts in the Script Editor Creating and editing scripts in the Script Editor Copying scripts in the Script Editor Testing scripts in the Script Editor Testing script compilation in the Script Editor Overriding scripts Permissions for running scripts Editing and testing script code with the System Debugger Extended debugging in the Object Browser
One Identity Manager query language Reports in One Identity Manager Adding custom tables or columns to the One Identity Manager schema Web service integration One Identity Manager as SCIM 2.0 service provider Processing DBQueue tasks One Identity Manager Service configuration files

Accessing objects' display values

Syntax

Display pattern corresponding to an object's DisplayPattern column:

$[Display]$

Display pattern corresponding to an object's DisplayPatternLong column:

$[LongDisplay]$

Example of usage on the base object

$[Display]$

Example of usage over foreign key relation

For assignments ofActive Directory groups to departments, use the ADSGroup's DisplayPatternLong.

$FK(UID_ADSGroup).[LongDisplay]$

Related topics

Using base objects

The Base. syntax always accesses the object that is currently loaded. 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, or 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

Usage of 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 run 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 one-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 or 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

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating