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

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

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.

NOTE: You can find detailed examples for syntax and usage of scripts on the installation medium in the directory QBM\dvd\AddOn\SDK\ScriptSamples.

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

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.

NOTE: The use of DateTime.Now in scripts must be critically tested. It is better to use DateTime.UTCNow than DateTime.Now to display the value to users.

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)

Related Documents