Chat now with support
Chat with Support

Identity Manager 8.1 - Configuration Guide

About this guide One Identity Manager software architecture Customizing the One Identity Manager default configuration Adjusting 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
Setting up Job servers in Designer Configuring the One Identity Manager Service Handling processes in One Identity Manager
Tracking changes with process monitoring Conditional compilation using preprocessor conditions Scripts in One Identity Manager 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 Appendix: Configuration files of the One Identity Manager Service

Displaying custom columns and tables on master data forms

Displaying Columns in Custom Tables

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

  • Create a user interface form using the form definition VI_Generic_MasterData. This form definition allocates the control element for editing master data in the user interface.
  • Specify the order for displaying input fields in the Designer in the property Sort order (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 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 master data forms.

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

  • Master data form already has tabs. Simple master 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 (DialogColumn.SortOrder) property of the database columns. Columns with a sort order of less that one are not displayed.
  • Database columns are grouped. In 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 tables UNSAccountB, UNSContainerB, UNSGroupB, UNSItemB and UNSRootB. For detailed information, see the One Identity Manager Administration Guide for Connecting to Custom Target Systems.
Related Topics

Forms for custom extensions

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

An other way to create custom forms is to make custom form archives available. Normally, default forms in One Identity Manager are replaced with self developed forms.

Table 45: 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 form templates FrmCommonTwoChildRelation and FrmCommonThreeChildRelation 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 table DialogValidDynamicRef. 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 property MembersTableName 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 form templates FrmCommonTwoMemberRelation, FrmCommonFourMemberRelation, and FrmCommonFiveMemberRelation 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 master 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 (table ADSAccount) is typically displayed on an assignment form below its Active Directory container (UID_ADSContainer). The Active Directory container (table ADSContainer) 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 46: 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

Replacing default forms with custom forms

Self developed form templates can be provided for custom forms in a form archive (*CustomForms.*.vif). You need to add the form template, form definition and interface form with help of the Form Editor if you want to display your custom forms in the user interface.

A wizard is available to swap a default form with all its dependencies for a custom form. The wizard creates the interface form with the form definition and the form template. The properties of the new form are taken from the form it is replacing. The necessary assignments (object definition, menu item, permissions group and application) are created for the new form and the replaced form is disabled.

To replace custom forms with all dependencies

  1. In Designer, select User interface | Forms | User interface forms.
  2. Select hierarchical representation of the form overview. Set the menu option Options | Tree/list view to do this.
  3. At the highest hierarchy level of the form overview, select the form template of the form to be replaced and start the wizard using the Replace by context menu.
  4. On the start page of the wizard, click Next.
  5. On the Select file and form page, enter the following information.

    • Form archive file: Select the form achive file (*.CustomForms.*.vif).
    • Form template: Select the form template for the new user interface.
  6. On the Define form structure page, check the names of the form definitions and user interface forms. The names of the form definitions and user interface forms should all begin with CCC. Use F2 to change the names and select Enter to save the change.
  7. On the Select permissions group page, select the permissions group to which the new user interface form should be assigned. Use the button to create a new permissions group.
  8. The last page of the wizard summarizes the settings for replacing a form. To replace the form, click Finish.

    The wizard is closed after replacement is complete. The new form is displayed in the Form Editor form overview after the wizard is complete and you can continue editing it. The replaced form is disabled and can therefore no longer available in the user interface.

Related Topics
Related Documents