Chatee ahora con Soporte
Chat con el soporte

Identity Manager 9.3 - 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 The full-text search in One Identity Manager 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 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 Displaying messages in the user interface Referencing packages and files in scripts 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 Committing and compiling script changes 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 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
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 Processor tasks Structure of the Jobservice.cfg configuration file

Forms for custom extensions

One Identity Manager provides an array of form templates and definitions in the default installation. These can be used for easily creating your own forms.

Table 107: Form templates and definitions for custom extensions
Form template

Form definition

 Usage

FrmCommonChildRelationGrid

VI_Common_ChildRelation_Grid

For editing many-to-many relations with extended properties in the form of a table.

FrmCommonOneChild
AndMemberRelation

FrmCommonOneMember AndChildRelation

A custom form must be created on which the data to be configured is displayed.

Assigns many-to-many relations and object relations (parent/child relations) on one form. Two tabs for displaying the data are shown on the form.

FrmCommonOneChildRelation

A custom form must be created on which the data to be configured is displayed.

Mapping object relations (Parent/ChildRelation).

If several additional object relations are mapped on a form, the FrmCommonTwoChildRelation and FrmCommonThreeChildRelation form templates can be used as alternatives. One tab is shown per object relation.

FrmCommonOneDynamicRelation

A custom form must be created on which the data to be configured is displayed.

Displays dynamic many-to-many relations whose assigned object is referenced through a dynamic Permitted dynamic objects are found in the DialogValidDynamicRef table. A drop-down is provided for choosing the object type.

FrmCommonOneGenericRelation

A custom form must be created on which the data to be configured is displayed.

Displaying dynamic many-to-many relations.

  • Base object can be referenced through a dynamic key.

    - OR -

  • Assigned object is referenced through a dynamic key. In this case, the MembersTableName property must be defined in the form configuration.

FrmCommonOneMemberRelation

A custom form must be created on which the data to be configured is displayed.

Assigning many-to-many relations.

If several additional many-to-many relations are mapped on a form, the FrmCommonTwoMemberRelation, FrmCommonFourMemberRelation, and FrmCommonFiveMemberRelation form templates can be used as alternatives. On tab is shown per many-to-many table.

FrmElementNavigation

VI_ElementNavigation

For displaying the overview form.

frmGeneric

VI_Generic_MasterData

For editing object main data.

ReportForm

VI_Report

For displaying reports.

WizardForm

VI_Wizard

For including wizards. The forms are displayed in a modal dialog window.

Related topics

Hierarchical display of data on assignment forms

Forms of the MemberRelation type are used to display the data in an assignment list (many-to-many relations). Enter the hierarchy path in the table definition to display the table hierarchically. Enter the foreign key column that the hierarchy should be based on.

Example: Hierarchy path

An Active Directory user account (ADSAccount table) is typically displayed on an assignment form below its Active Directory container (UID_ADSContainer). The Active Directory container (ADSContainer table) is, on the other hand, displayed underneath its Active Directory domain (column UID_ADSDomain). The path for the hierarchy structure is entered as follows:

Table Hierarchy path

ADSAccount

UID_ADSContainer, UID_ADSDomain

ADSContainer

UID_ADSDomain

You can specify an alternative list for objects that do not have values in all foreign key columns after a pipe (|).

Example:

(UID_ADSContainer,UID_ADSDomain|UID_ADSDomain)

Related topics

User interface form properties

The following properties are displayed for interface forms.

Table 108: User interface form properties
Property Meaning

Form name

The form name is used to quickly select interface forms, for example, in the Designer.

TIP: The form name is displayed in the administration tool as extra navigation information.

Form definition

Form definition linked to the user interface form.

NOTE: Use next to the input field to link in a new form definition for the interface form.

Caption

Caption shown on the user interface form. The caption is used to represent the user interface form in the task view and in the form context menu of the user interface. Translate the given text using the button.

Online help link

The form's help key for navigating to the relevant chapter in the online help.

Description

Detailed description of the user interface form.

TIP: The description is shown as a tooltip in the task view.

Icon

Icon marks the user interface form in the user interface.

Sort order

The sort order determines the position of the interface form in the task view and in the form’s context menu in the administration tools.

NOTE: When you enter objects in the Manager, the user interface form of the Edit form type is always displayed with the lowest sort order.

Preprocessor condition

User interface forms can be given a preprocessor condition. This means that an interface form is only available when the preprocessor condition is fulfilled.

NOTE: In the Designer, you can find an overview of existing preprocessor dependencies in the One Identity Manager Schema > Preprocessor dependencies category.

Control deactivation

Specifies which buttons in the toolbar are to be disabled in the front-ends

Permitted values are:

  • Insert object: The button is disabled.

  • Update object: The button is disabled.

  • Delete Object: The button is disabled.

  • Save to database: The button is disabled

Deactivated

Use this option to label interface forms that should not be shown in the user interface.

NOTE: This change is also permitted for user interface forms in the default user interface and is not overwritten on schema installation.

Disabled by preprocessor

If an object definition is excluded through a preprocessor condition, this option is set by the Database Compiler.

Show modal

Specifies whether the form is displayed in a separate dialog. Used by wizards for entering data.

Open on new tab

The form is opened on a new tab.

Configuration

The configuration is used to limit the tables and columns on display. Templates for the configuration data definition are found in the pop-up list XML templates.

In the Properties section, you can transfer special properties of the form that were implemented during form development. For example, the report name and special report parameters can be passed to the report interface form by using this section.

Insert values

Insert values are only of relevance to interface forms of the Edit form type. With them you can specify the default values for the columns that are assigned when a new object is added. The input is in VB.Net syntax.

NOTE: The database needs to be complied after modifying the inserted values.

Related topics

Form definitions and form templates

Form definitions and form templates make up the basis of interface form design. Form definitions contain information about the data that will appear on the forms such as, tables, and columns as well as titles for form tabs and root nodes in hierarchically ordered elements (ChildRelationControl, membership tree) for the form templates defined in the form archives.

Detailed information about this topic
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación