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

Identity Manager 9.3 - 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 The full-text search in One Identity Manager 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 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 Displaying messages in the user interface Referencing packages and files in scripts 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 Committing and compiling script changes 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 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
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 Processor tasks Structure of the Jobservice.cfg configuration file

Assigning menu items to applications

All menu items to be displayed in an application user interface must be assigned to an application.

To assign a menu item to an application

  1. In the Designer, select User interface > User interface navigation category.

    The menu items are loaded and displayed in the User Interface Editor for editing.

  2. Select the menu item in the navigation overview.

  3. In the edit view, select the Application view and then the application.

  4. Select the Database > Save to database and click Save.

TIP: Use the Recursively assign application context menu to assign the application to the selected menu item and its child menu items. Use the Recursively remove application context menu to remove the application’s assignment to the selected menu item and its child menu items.

Related topics

Assigning menu items to permissions groups

All menu items to be displayed in an application user interface must be assigned to a permissions group. Assign the menu items to permissions groups for non role-based and role-based login. The menu items are available to system users depending on their permissions group memberships. For more information about permissions groups, see the One Identity Manager Authorization and Authentication Guide.

To assign a menu item to a permissions group

  1. In the Designer, select User interface > User interface navigation category.

    The menu items are loaded and displayed in the User Interface Editor for editing.

  2. Select the menu item in the navigation overview.

  3. In the edit view, select the Permissions group view and select the permissions groups.

  4. Select the Database > Save to database and click Save.

TIP: Use the Assign permissions group recursively context menu to assign the permissions group to the selected menu item and its child menu items. Use the Remove permissions group recursively context menu to remove the permissions group assignment to the selected menu item and its child menu items.

Related topics

Menu item properties

The following properties do not depend on the entry type of a menu item. The type of menu item determines the availability and the editability of the properties.

Table 101: General menu item properties
Property Description

Menu item

Unique menu item relation. You should assign descriptive names here if possible. These are then propagated in the child structures. This makes it easier to trace the position of child menu items. The parent menu item and the hierarchy is determined by the insert position in the user interface navigation. The menu item name can contain variables in order to represent the menu items.

Entry type

Menu item entry type. Permitted values are:

  • Menu category

  • Fixed menu item

  • Data-Dependent Menu Item

  • Task category

  • Task

  • Detached Menu Item

  • Link

  • Main Form Element

  • Statistics

For more information, see Components for navigation.

Menu item link

Reference entry that is shown when the link is opened during runtime.

Caption

Language-dependent caption for displaying the menu item in the user interface. The caption for data-dependent menu items can contain fixed strings and variables. The caption for recursive data-dependent menu items is inherited from the parent menu item. Translate the given text using the button.

Sort order

If several menu items have the same parent menu item, the sort order of the individual menu items specifies their position in the display order.

If the configuration flag Re-sort data submenu items by caption is set for the parent menu item, the sort order specified here is invalid.

Icon

Icon for displaying the menu item in the navigation If no icon is specified for recursively data-dependent menu items, the icon from the parent menu item is inherited.

Launchpad action

Action to run in the Launchpad.

FK object to activate (data node)

Path to the FK object to be loaded when an entry is selected in the front-end. Enter the base object path in the VI.DB ObjectWalker notation.

Example: FK(UID_ADSGroup)

Table

Table that the values are read from.

Condition

Specifies the conditions under which the menu item is displayed in the navigation. The input must satisfy the WHERE clause database query syntax. You can use variables to formulate a condition.

If the menu items are data-dependent, the condition is used to limit the number of results. If the menu items are recursively data-dependent then variables have to be used.

NOTE: The condition must not contain a JOIN and the query may need to be formulated as a subquery.

Sort order

Display elements are sorted by these table columns. The input must satisfy the Order By syntax of database queries. Sorting is given by the columns of the display template if no value is entered. You should use a sort order if the data has a date or represents language-dependent data.

NOTE: For language-dependent sorting, use the Re-sort data dependent menu item by caption configuration switch.

Configuration flag

Special functions are set for menu items with the configuration flag. For more information, see Table 102.

Preprocessor condition

You can add preprocessor conditions to menu items. This means that a menu item is only available when the preprocessor condition is fulfilled.

NOTE: In the Designer, you can find an overview of existing preprocessor dependencies in the One Identity Manager Schema > Preprocessor dependencies category.

Description

 Text field for additional explanation.

Disabled

Specifies whether the menu item is displayed in the user interface. Disabled menu items are never displayed in the user interface.

NOTE: This change is also permitted for menu items in the default user interface and is not overwritten on schema installation.

Disabled by preprocessor

If a menu item is excluded through a preprocessor condition, this option is set by the Database Compiler.

Show under "My One Identity Manager"

This option marks the menu items in the Manager to be displayed in the My One Identity Manager category.

Unique

The query result cannot contain doubled items. By setting the Unique option, any doubt is eliminated.

Menu items that are labeled with the Unique option have to contain variables in their names to achieve uniqueness.

If, for example, all software applications (Application table) are grouped by language, the name of the corresponding menu item must contain a variable, which references the UID_DialogCulture column in the Application table.

NOTE: No interface forms are shown for objects that result from a database query.

NOTE: The option is disabled if the configuration switch Force open menu item is set.

Recursive calling

This menu item is the recursive successor of the previous menu item. If the option is not set, the results are represented by a flat structure. Set the option if the menu item is required to represent a hierarchical structure. You can only define recursive data-dependent menu items below a data-dependent item without recursion.

Do not merge columns

For use in displaying columns in the form elements on overview forms. Specifies whether columns defined for this menu item are merged and displayed with the default table columns.

Enable the option to display only those columns defined in the menu item. Columns that are regularly displayed for a table, are not shown.

Initialization script

VB.Net expression for overwriting values of this menu item respective to the data. The script allows you to initialize variables that you can then use when designing the display texts on overview forms.

Example:

Initializing the variable in the script: Variables("MyNewCaptionValue") = "New caption value".

Usage: %MyNewCaptionValue%

Overlay icon definition

VB.Net expression for defining overlays for the icon. Used to display the status in the Launchpad.

Table 102: Configuration flags for special functions
Configuration flag Description

Auto-reload on insert

If this configuration flag is set, the menu item is reloaded after new data is added.

Hide on empty result

If no submenu items are generated for a menu item labeled the same way during runtime, the menu item is similarly hidden in the user interface.

Not expandable by user

Menu items with this configuration flag set, cannot be opened even if submenu items are available. The configuration flag is mainly used in the info system for displaying statistics.

Ignore user interface forms

This configuration flag can be used for data-dependent menu items. If the configuration flag is set, no object-dependent interface forms are displayed when the menu item is selected in the user interface. This configuration flag is mainly used for structuring the user interface for Web front-ends.

Force open menu item

If this configuration flag is set, the menu item is always open. There is no test to see if the menu item is assigned to something, for example, the interface form.

Re-sort data submenu items by caption

The configuration flag should be set if language-dependent data is displayed. If the configuration flag is set, the data for all submenu items to be shown are sorted by language.

This enables all user accounts, groups, and containers in a container structure, for example, to be sorted alphabetically. The sort order not only affects data-dependent menu items but also all submenu items.

Re-sort data-dependent menu item by caption

This configuration flag can be used for data-dependent menu items. The configuration flag should be set if language-dependent data is displayed. If the configuration flag is set, the data for menu navigation to be shown is sorted by language after it is loaded.

Take navigation context into account on enabling

If this configuration flag is set, the location in the navigation where the menu item is opened is taken into account when the objects are loaded. If an object appears several times within a navigation structure, the content is loaded and displayed depending on the location of the navigation structure.

If the configuration flag is not set, the data is retained, even if the object is opened again from another location in the navigation.

Related topics

Creating database queries for data-dependent menu items

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.

For property descriptions of menu items, see Menu item properties. The following properties are necessary to put together a database query:

Table 103: Database query properties
Property Description

Table

Table that the values are read from.

Sort order

Display elements are sorted by these table columns. The input must satisfy the Order By syntax of database queries. Sorting is given by the columns of the display template if no value is entered. You should use a sort order if the data has a date or represents language-dependent data.

NOTE: For language-dependent sorting, use the Re-sort data dependent menu item by caption configuration switch.

Condition

Condition for limiting the number of results displayed. The input must satisfy the WHERE clause database query syntax. You can use variables for formulating a condition. If the menu items are recursively data-dependent then variables have to be used.

NOTE: The condition must not contain a JOIN and the query may need to be formulated as a subquery.

Unique

The query result cannot contain doubled items. By setting the Unique option, any doubt is eliminated.

Menu items that are labeled with the Unique option have to contain variables in their names to achieve uniqueness.

If, for example, all software applications (Application table) are grouped by language, the name of the corresponding menu item must contain a variable, which references the UID_DialogCulture column in the Application table.

NOTE: No interface forms are shown for objects that result from a database query.

NOTE: The option is disabled if the configuration switch Force open menu item is set.

Recursive calling

This menu item is the recursive successor of the previous menu item. If the option is not set, the results are represented by a flat structure. Set the option if the menu item is required to represent a hierarchical structure. You can only define recursive data-dependent menu items below a data-dependent item without recursion.

FK object to activate (data node)

Path to the FK object to be loaded when an entry is selected in the front-end. Enter the base object path in the VI.DB ObjectWalker notation.

Example: FK(UID_ADSGroup)

Related topics
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택