Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Identity Manager 8.2 - 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 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 Windows 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 SOAP Web Service One Identity Manager as SPML provisioning service provider Processing DBQueue tasks One Identity Manager Service configuration files

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 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

Using session services

The session object is the instance that makes data available to a user session. This includes the current user, their permissions groups and program functions. Furthermore, the session object makes various services available for accessing data. The services provided by the session object are made available through a generic interface (Resolve (Of Service)()). In the following sections, examples are provided of frequently used service.

NOTE: You can find a complete description of all parameters in the VI.DB.DLL documentation.

Detailed information about this topic

Querying configuration parameters

The full path for the configuration parameter always has to entered when configuration parameter are queried.

Syntax

Session.Config().GetConfigParm("<full path>")

When a configuration parameter is tested in a generating condition in VB.Net syntax, the function returns a string. In order to compare this value to a numerical value, the configuration parameter has to be set and contain a numerical value. This depends on the implicit value type conversion from VB.Net. If the configuration parameter is not enabled, the function returns an empty string ("") that cannot be compared to a numerical value. This results in a VB.Net runtime error. Configuration parameter values are therefore always compared to strings.

Do not use:

Session.Config().GetConfigParm("QER\Person\User\DeleteOptions\Homedir")=1

Use instead:

Session.Config().GetConfigParm("QER\Person\User\DeleteOptions\Homedir")="1"

In order to ensure that a logical value is always returned, the VID_IsTrue function should be used.

Example

If VID_IsTrue(Session.Config().GetConfigParm("QER\Person\User\DeleteOptions\Homedir")) Then ...

Related topics
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation