Chat now with support
Chat with Support

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

Configuration data for displaying many-to-many and object relations on forms

Form properties are specified by the form definition configuration data. The definition of the form properties is written in XML notation.

Recommendations regarding XML notation.

  • Pass multiple line values in one element.

    Example:

    <Property Name="WhereClause">IsITShopOnly=0 and HasReadOnlyMemberships=0</Property>

  • Describe single values in an attribute.

    Example:

    <Property Name="MNTableName" Value="DepartmentHasADSGroup" />

  • To avoid masking XML special characters (<,>,&,",'), pass the value in a CData element.

    Example:

    <Property Name="WhereClause"><![CDATA[UID_UNSGroupB3 <> $UID_UNSGroupB3$]]></Property>

Example: Configuration data structure

<FormPatch FormatVersion="2.0">

<Patches>

<Component Name="MemberRelation1">

<Properties>

<Property Name="MNBaseColumnName" Value="UID_Department" />

<Property Name="MNTableName" Value="DepartmentHasADSGroup" />

<Property Name="RootFilterTableName" Value="ADSDomain" />

<Property Name="RootFilterMemberWhereClause">UID_ADSDomain='%UID_ADSDomain%'</Property>

<Property Name="WhereClause">IsITShopOnly=0 and HasReadOnlyMemberships=0</Property>

</Properties>

</Component>

<Patches>

</FormPatch>

Displaying relations
Table 47: Properties of relation definitions
Component Property Meaning

All

 

Valid for all maps.

 

WhereClause

Limited condition for applying to the displayed objects (member, child).

The expression %column% can be used in the WhereClause to reference values of the base object.

$ expressions are permitted to reach other values from the base object, for example $FK(UID_ADSContainer).UID_ADSDomain$.

Example:

<Property name="WhereClause" value="IsITShopOnly=0" />

 

EditWhereClause

Edit condition. The elements that match the condition can be edited. All other elements are also displayed but cannot be edited.

Example:

<Property name="EditWhereClause" value="XMarkedForDeletion=0" />

MemberRelation1-MemberRelationN

 

Displaying M:N relations

Example:

<Component Name="MemberRelation1">

 

MNTableName

M:N table.

Example:

<Property name="MNTableName" value="OrgHasADSGroup" />

 

MNBaseColumnName

Column of the M:N table that points to the base object.

Example:

<Property name="MNBaseColumnName" value="UID_ADSGroup" />

 

RootFilterTableName

Table for filtering assignable elements from users. If defined, the control element shows a menu with objects from this table. If, for example,

Example:

<Property name="RootFilterTableName" Type="String" value="OrgRoot" />

 

RootFilterWhereClause

Condition for filtering elements of the RootFilterTableName in the menu.

Example:

<Property name="RootFilterWhereClause" Type="String" value="UID_OrgRoot in (select UID_OrgRoot from Org) and exists (select 1 from OrgRootAssign where IsDirectAssignmentAllowed = 1 and UID_OrgRoot=OrgRoot.UID_OrgRoot and UID_BaseTreeAssign='ADS-AsgnBT-ADSGroup')" />

 

RootFilterMemberWhereClause

Condition formatted after selecting a base object and attached to the WhereClause. The condition must always contains a column relation to the base object.

Example:

<Property name="RootFilterMemberWhereClause" Type="String" value="UID_OrgRoot=N'%UID_OrgRoot%'" />

 

ShowExtendedProperties

Specifies whether many-to-many tables with additional columns are offered an additional Extended properties context menu item on the assignment form. You use the context menu item to navigate to the detailed form where you can edit the extended properties.

Example:

<Property name="ShowExtendedProperties" value="True" />

 

HierarchyDetailsMode

Specifies whether the long display pattern (DialogTable.DisplayPatternLong) is used for displaying hierarchically.

Example:

<Property name="HierarchyDetailsMode" value="UseDisplayLong"/>

ChildRelation1- ChildRelationN

 

Displaying parent-child relations.

Example:

<Component Name="ChildRelation1">

 

CRTableName

Table in which child objects are mapped.

Example:

<Property name="CRTableName" value="ADSAccount" />

 

CRColumnName

Child table foreign key that points to the base object.

Example:

<Property name="CRColumnName" value="UID_Person" />

 

ShowForeign

Specifies whether foreign assignments (object assigned to another object) can be displayed.

Example:

<Property name="ShowForeign" value="True" />

GenericRelation1-GenericN

 

Displaying dynamic many-to-many relations.

Example:

<Component Name="GenericRelation1">

 

MNTableName

M:N table.

Example

<Property name="MNTableName" value="ADSPolicyAppliesTo"/>

 

MNBaseColumnName

Column of the M:N table that points to the base object.

Example:

<Property name="MNBaseColumnName" value="ObjectKeyAppliesTo" />

 

MNMembersColumnName

Column of the M:N table that points to the members.

Example:

<Property name="MNMembersColumnName" value="UID_ADSPolicy" />

 

MembersTableName

Tables whose objects must be assigned.

Example:

<Property name="MembersTableName" value="ADSPolicy"/>

Using tabs

Use the components TabPage to display tabs for the mapped relations. Usually tabs are used for forms that map multiple relations, such as FrmCommonTwoMemberRelation or FrmCommonTwoChildRelation. TabPage1 maps the tab for Relation1, TabePage2 maps the tab for Relation2.

Table 48: Properties of tab definitions
Component Property Meaning

TabPage1-TabPageN

 

Displays 1-n tabs for each relation to be shown.

Example:

<Component Name="TabPage1">

 

Caption

Tab captions. Table names or any string can be used as captions.

Example:

<Property name="Caption" value="Department"/>

 

CaptionTranslationSource

Source for translating the tab names.

value="DatabaseSchema" finds the table captions translation from the One Identity Manager schema table given under Caption.

value="TranslationAddOnSource" finds the translation from the text store.

Example:

<Properties>

<Property name="Caption" value="Department"/>

<Property name="CaptionTranslationSource" value="DatabaseSchema" />

</Properties>

<Properties>

<Property name="Caption" value="is member of"/>

<Property name="CaptionTranslationSource" value="TranslationAddOnSource" />

</Properties>

Related topics

Working with overview forms

There is a special control element for displaying the overview form in the user interface. The information to be displayed on the overview form is configured with menu items. The menu items are represented as form elements that are linked to each other on the overview form. A hierarchical structure of menu items is also included in the interface configuration.

The basis is formed by a menu item with the Main form element item type. This menu item specifies the main element on the overview form. An interface form that links to this menu item has to configured in order for it to be displayed in the application. The main form element is always displayed in the middle of the overview form.

The other menu item such as fixed, data-dependent, link, or statistic menu items are configured under the menu item for the main form element. These menu items are grouped around the main form element on the overview form as additional form elements.

The color and positioning of the form elements on the overview form as well as the properties that are shown, are specified by layout information for the menu items and can also be customized for the default overview forms that are supplied.

Figure 15: Example of elements in an overview form

The display text of the menu item, the display text for the objects to be shown and the menu item icon are displayed in the header of a form element. Other data represents the object properties and values. There is a tooltip for each property showing a description for use. Some form element entries are highlighted in color when you click on them with the mouse. You can jump to the referenced object by clicking on the entry with the mouse.

If the form element is used for mapping lists, the items are displayed with their names. The number of items is shown in the form element header. There is also an icon in the form element header for showing and hiding the items. There is no tooltip for list items.

Table 49: Form element icon
Icon Meaning

Show list items.

Hide list items.

NOTE: Objects marked for deletion are struck through on the overview form.

Detailed information about this topic

Creating overview forms

The Overview Form Editor helps you to create overview forms. The Overview Form Editor performs the following steps to create the overview form.

  • Creating a menu item with the Main form element item type.

  • Creates other menu items under the main form element.

  • Creates a user interface form for the main form element.

Figure 16: Design view in the Overview Form Editor

To create a new overview form

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

  2. Select the Create new overview form task.

  3. Enter the basic properties for the overview form.

    Table 50: Basic data for an overview form
    Property Meaning

    Menu item

    Name of the menu item. Assign descriptive names here if possible. These are then propagated in the child structures.

    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.

    Object

    Object definition for which the form should be displayed.

    Parent menu item

    Parent menu item for grouping together the overview forms; usually a menu category.

    Product assignment

    Application in which the form will be shown.

    Group assignment

    Permissions group for which the form will be shown.

    Display columns

    Columns to be displayed on the main form element.

    TIP: Use the Show column captions link to switch between column captions and technical names.

  4. To create the overview form, click OK.

    This displays the overview form design in the Overview Form Editor. You can continue editing the overview form.

Related topics

Adding more form elements to overview forms

For the other form elements on an overview form, create menu items. Different types of menu items are supported.

Menu items can be created as direct list elements or data elements, or as references to existing items. The following special features apply when you create form elements using the Create list element reference and Create reference to data element context menus.

  • The reference entries under the InfoSheets.QIM.Links menu item are used.

  • If the required reference entries are not yet available, new reference entries are created with the names InfoSheet.List.<table> or InfoSheet.Node.<table>.

  • In the reference entry condition, a %<Table>WhereClause% variable is used.

  • A variable with the Text variable type is used on the form element. A condition formulated as a WHERE clause is assigned to these variables on the form element. You can further modify this condition as required. In the Overview Form Editor's edit view, edit the variable in the Variable definitions view.

To add more form elements to the overview form

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

  2. Select the overview form then select the Edit overview form task.

  3. Select the view Object relations.

    All the object foreign key relations (FK), object child relations (CR), and object member relations (M:N) are displayed.

  4. Select the object relation that you want to display and drag and drop it on an element in the element area of the design view.

  5. Select the type of menu item you want to create. You have the following options:

    • Create list element: A fixed menu item with predefined list properties is created.

    • Create data element: A data-dependent menu item is created.

    • Create list element reference: A menu item is created with the Link item type and a reference to a menu item for display as a list.

    • Create reference to data element: A menu item is created with the Link item type and a reference to a data-dependent menu item.

    The menu item’s main data is automatically generated by the Overview Form Editor. The form element is display in the Overview Form Editor's design view.

TIP: Use the Create element context menu to create more menu items, links, or statistics as form elements in the Overview Form Editor's design view. In this case, enter the main data of the menu item, link, or statistics manually.

Related topics
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating