|Exclusive||Objects labeled with this option are considered exclusive. That means, all other possible matching object definitions are not accepted as valid. If several object definitions of one table are labeled as exclusive, the object definition with the lowest sort order applies.|
|Display template||The display template specifies the form in which the data sets in the administration tool result lists are displayed.|
|Display name||The object's display name is used, for example, to identify the table in a database search or for error output. Display names can be given in more than one language.|
|List caption||Caption used to display the list title in the user interface.|
|Form caption||Caption used to display the form title in the user interface.|
Selection script as a VB.Net term, to determine during runtime whether the database object passed down belongs to this object definition.
Object processing status.
Condition required for the object definition to be used for displaying in lists. The condition is defined as a database query WHERE clause.
|Remarks||Spare text box for additional explanation.|
|Disabled by preprocessor||If an object definition is excluded through a preprocessor condition, this option is set by the Database Compiler.|
Default settings for fields that are assigned when a new data set is added. The input is in VB.Net syntax.
|Background color||Color, with which the control for this object is displayed in the schema overview.|
|Object name||Name of the object.|
Object definitions can have preprocessor conditions added. This means, an object definition is only available when the preprocessor condition is fulfilled.
The sort order is used for displaying the form title when an object is selected. The smaller the sort order magnitude, the stronger the restrictions defined for the object.
|Icon||Icon for displaying the object definition.|
|Table||Table for which the object definition is created.|
One Identity Manager administration tools with their own user interface are given their own navigation view. The navigation defines specific entry points into the One Identity Manager tool's user interface and controls the user oriented navigation down to the selection of an object in the result list. You can set up the structure of the user interface navigation through a menu. There are different types of menu items with specific uses. You can design a multifaceted navigation by combining different types of menu items.
|Menu category||Menu categories are displayed at the navigation top level and provide a method of grouping the data to be managed from different viewpoints. Menu categories constitute entry points into the interface navigation view. Menu categories are displayed as categories in the user interface.|
|Fixed Menu Item||Fixed menu items are used to organize data more clearly within menu categories. These menu items are always shown in the navigation view. List properties can only be defined for fixed menu items. These specify how the table entries are displayed in the user interface result list.|
|Data Dependent Menu Item||Data dependent menu items are generated by a database query that returns several data sets as output. These menu items are therefore not individual menu items, but a set of menu items depending on the output of the database query. List properties can be defined for data dependent menu items. These specify how the table entries are displayed in the user interface result list.|
|Detached Menu Item||Detached menu items are used to group other menu items or to define a main menu item for an application. For example, you can specify a web interface home page with a detached menu item. Detached menu items should always be created at the navigation top level. However, they do not appear in the administration tools navigation view.|
Links support the navigation configuration. They are used to reference frequently accessed menu items. Parts of the navigation interface that require an application several times, only need to be set up once. The referenced menu items are always shown in navigation interface as opposed to the links.
|Main Form Element||Main form elements are not menu items in the navigation view, but are used as the main elements in object overview forms. All child menu items are assigned to the main element.|
Task categories are represented at navigation top level and are used to organize task oriented workflows. Task categories are not mapped in the navigation view but on a special form in the administration tools.
Tasks are used to map single tasks within a task category. They are used, for example, as starting points for administration tool wizards. Tasks are always listed under a task category menu item. Task categories and their tasks are not displayed in the navigation view but on a special form.
|Statistics||This menu item is used to display statistics. Statistics are typically displayed in the info system. All statistics that are defined in one menu level can be displayed on one form or as individual menu items. Statistics can also be linked in as form elements.|
TIP: You can define display templates for menu items, object definitions and tables.
The display template is determined by the following in order:
||TIP: It is best to define the required variable already in the menu item for the menu category. Variables are inherited within a hierarchical navigation. This means that variables can be reused or overwritten on lower hierarchy levels. At run-time the actual value is passed to the variables.|