One Identity Manager Scripts

One Identity Manager Scripts

Scripts are used in the One Identity Manager to monitor and maintain data consistency and customer business logic in the database. Scripts can be used to:

• Test column values
• Trigger events
• Create, change and delete objects and therefore manipulate the database

Detailed information about this topic

• Using Scripts
• Message Output
• Implementing Dates
• Using Dollar ($) Notation
• Using base. Object
• Calling Functions
• Pre-scripts for using in Processes and Process Steps
• Using Session Services
• Using #LD Notation
• Scripts in the Script Library
• Testing Scripts with the System Debugger

Using Scripts

One Identity Manager scripts are written in VB.Net syntax, which allows all VB.Net functions to be used. The values to be edited are given as preprocessor instructions.

You can use scripts in:

• Templates and formatting scripts (DialogColumn table)
• Table scripts (DialogTable table)
• Script library (DialogScript table)
• Tasks (DialogMethod table)
• Object definition selection scripts (DialogObject table)
• Views selection scripts (DialogTable table)
• Scripts to find the servers to execute process steps (Job table)
• Process step parameters (Jobrunparameter table)
• Process control notification (Job table)
• Generating conditions for process steps and processes (Job and JobChain tables)
• Process step and process pre-scripts (Job and JobChain tables)
• Process information (Job, JobChain and JobEventgen table)
• Mail templates (table DialogRichMailBody)

Message Output

You should never use the VB.Net functions Msgbox and Inputbox on servers. Use the functions VID_Write2Log, RaiseMessage or AppData.Instance.RaiseMessage.

Related Topics

• Outputting Custom Messages in the One Identity Manager Service Log File

Implementing Dates

Time stamps, such as insert dates or modification dates, are stored in the database with the respective UTC. The object layer transforms this time data into the currently valid time zone data when an object is loaded. The user, therefore, sees all the values in local time. When an object is saved the current time zone data is transformed into UTC data.

It is not recommended to convert dates, in non-U.S. notation, from type "String" to type "DateTime" in scripts:

Value = CDate("31.12.2014")

This always causes a problem if the script is running on a U.S. system. In the best case, you are sent an error message like "Cast from string...to type Date is not valid". In the worst case the wrong date is returned as month and day are swapped (3.12.2014 becomes 12.3.2014).

If possible, you should avoid a string conversion altogether in this case. The type "DateTime" provides several functions for this purpose. For the example above, that would be:

Value = new DateTime(2014, 12, 31)

If the data type "String" however, should be used then the ISO date notation should be applied as it is always converted correctly:

Value = CDate("2014-12-31")

Value = CDate("2014-12-31 15:22:12")

The complicated version is to input the language code format for the date:

Value = DateTime.Parse("12.31.2014", new CultureInfo("en-US"))

Value = DateTime.ParseExact("12.31.2014", "mm.dd.yyyy", CultureInfo.InvariantCulture)