Data Dependent Menu Item Uniqueness
Menu items that are labeled with the option unique have to contain variables in their names to achieve uniqueness.
IF, for example, all applications (table Application) are grouped by language, the name of the corresponding menu item must contain a variable, which references the column Ident_Language in the table Application.
Figure 27: Example of Data Dependent Menu Item without Uniqueness (left) and with Uniqueness (right)
Related Topics
Recursively Data Dependent Menu Items
The heart of the hierarchy is variable replacement. Variables are passed down through the hierarchical navigation view and can therefore be used at lower levels or can be overwritten. In the case of recursive data dependent menu items, the variable contained in a database query is initially replaced by the existing variable value from the parent level and then the query is started. The resulting value immediately determines a new value for the variable that is processed again in the parent node’s next step. The original value of the old variable is no longer available after the database query has been executed. If the database query delivers an empty result, the recursion is stopped.
Figure 28: Example of Data Dependent Menu Items with Recursive Calling (left) and without Recursive Calling (right)
Related Topics
Editing Lists
You can apply list properties to fixed and data dependent menu items. These properties determine how the table entries are displayed in the user interface result list.
For more information about general properties of menu items, see General Menu Item Properties. To define a list, you need to use the following properties:
| Property | Meaning |
|---|---|
| Display template |
The display template for displaying table entries in the administration tool result lists are displayed. If a customer specific display template exists it is used instead of the default display template. Syntax: %column name% |
| Object | Definition of the object which determines the list items. |
| Condition |
Condition for limiting the number of results. The input must satisfy the "WHERE clause" database query syntax. The condition relates to the given object definition. The condition is consolidated with the condition which is already stored for the object definition. The variables can be used that are available in the navigation interface. |
| Icon | Icon for displaying the items in the list. |
| Order by |
Columns to use for the list order. The input must satisfy the "Order by" database query syntax. You should use a sort order if the data has a date or represents language dependent data. Use the configuration flag "Re-sort result by caption" for a language dependent sort order. |
| Insert values |
Insert values initialize individual values when a new data set is added over the result list. Enter insert values in VB.Net syntax. When defining insert values, you can apply the variables currently available in the navigation. |
| Insert in list permitted | Specifies whether inserting with the context menu is permitted in the corresponding result list. This option is set by taking ‘can insert’ permissions into account. |
| Permit deletion in list | Specifies whether deleting with the context menu is permitted in the corresponding result list. This option is set by taking ‘can delete’ permissions into account. |
Related Topics
- General Menu Item Properties
- Display Template for Displaying a List
- Defining Insert Values
- Using Variables
- Language Dependent Data Representation
- Object definitions for the User Interface
- Editing Permissions for One Identity Manager Schema Tables and Columns
Display Template for Displaying a List
You use a list display template to specify the form in which the table entries will be represented in the administration tool result list. You can define display templates for menu items, object definitions and table lists.
The display template is determined by the following in order:
- List display template for the menu item
- Object definition display template
- Table display template
The display template for displaying a list can be described in the following syntax:
%columnname%
All the columns that belong to the table that will be displayed can be used in the display template. Variables may not be used in display templates for lists.
Replacing the display templates supports the ?? operator. Thus you can formulate conditional display templates with the following syntax.
%columnname1??columnname2??columnname3%
%columnname1 ?? columnname2%
The first column that returns a value from the list of column names is used. Spaces are permitted before and after the ?? operator but not at the begining and end of the display template on performance grounds.
Example of a Display Template
The Active Directory user account (table ADSAccount) should be shown as follows:
Common Name (fully qualified domain name)
The display template for the table ADSAccount to be specified for this purpose is:
%cn% (%CanonicalName%)