지금 지원 담당자와 채팅
지원 담당자와 채팅

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

Assigning user interface forms to menu items

You can assign user interface forms for individual menu items. The user interface form is displayed when a user selects the menu item in the navigation view or an entry in the result list. It is displayed irrespective of the user’s permission groups.

To assign a user interface form to a menu item

  1. In the Designer, select the User interface > Forms > User interface forms category.

  2. Select the Edit form task.

  3. In the Form Editor, select the user interface form.

  4. In the edit view, select the Menu assignment view and select the menu item.

  5. (Optional) Enable the Show in navigation option to open the form from the navigation view.

  6. Select the Database > Commit to database and click Save.

Related topics

Displaying custom columns and tables on main data forms

Displaying columns in custom tables

To display custom database table in the administration tool user interfaces and edit the main data:

  • Create a user interface form using the form definition VI_Generic_MasterData. This form definition allocates the control element for editing main data in the user interface.

  • In the Designer, specify the order for displaying input fields in the Sort order property (DialogColumn.SortOrder). Columns with a sort order of less that one are not displayed.

  • Achieve a better overview of the input fields by grouping database columns. In the Designer, customize the Group property (DialogColumn.ColumnGroup) in the column definition. Each group has its own tab. The name of the tag corresponds to the group.

  • Columns whose data contents can be multiline are displayed in a multiline field on the generic form. Label these columns as multi-line.

Displaying custom columns in predefined tables

Separate tabs can be shown for custom column extensions to default tables on the predefined main data forms.

The preceding features apply if the predefined main data form uses the VI_Generic_MasterData form definition. Otherwise the following prerequisites are required for using this functionality:

  • Main data form already has tabs. Simple main data forms without tabs are not extended.

  • To change the sort order in which the input fields on the form are displayed, select the Sort order property (DialogColumn.SortOrder) of the database columns. Columns with a sort order of less that one are not displayed.

  • Database columns are grouped. In the Designer, customize the Group property (DialogColumn.ColumnGroup) in the column definition. Each group has its own tab. The name of the tag corresponds to the group. If no group is specified, a tab with the name Custom is displayed.

NOTE: Other special features apply to displaying custom schema extensions on the UNSAccountB, UNSContainerB, UNSGroupB, UNSItemB, and UNSRootB tables. For more information, see the One Identity Manager Administration Guide for Connecting to Custom Target Systems.

Related topics

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 41: 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 menu 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:

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 42: Example of a hierarchy path
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
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택