General configuration settings are specified in a configuration file Designer.exe.config. Valid global configuration settings can also be defined through the global configuration file Global.cfg in One Identity Manager's own format. The configuration files are stored in the program directory. For detailed information, see the One Identity Manager Process Monitoring and Troubleshooting Guide.
To change the program settings in the Designer
Related topics
On the User tab, configure your user-specific program settings. These settings are stored in the One Identity Manager database user configuration.
General
-
Show balloon tips: Specifies whether speech bubbles, which provide information about program functionality, are shown in the program.
-
Show large images in navigation panes: Specifies whether smaller or larger icons are displayed on the categories.
-
Show additional icons: Specifies whether icons are shown in the task list in addition to the descriptions.
-
Use single clicks: Specifies whether objects are loaded with a single click or by double-clicking.
-
Show additional navigation information: If this option is activated, additional information is shown for individual interface components.
NOTE: The option is not saved permanently. It has to be reset each time the program is started.
After starting
- Visible root nodes: The number of categories to be displayed initially in the navigation view. Changes become effective after a restart.
Behavior
-
Enable quick edit mode: Specifies whether quick editing is enabled.
By default, an object‘s overview form is displayed first. You can, however, configure the program to show the edit form for the object first, which allows faster editing. In order to do this quick edit mode has to be enabled. Quick edit mode is indicated by an additional icon in the program’s status bar.
-
Show "Getting Started": Specifies whether the Getting Started category is shown or hidden.
-
Show system data: Specifies whether comprehensive system information such as system tables, script occurrences, preprocessor dependencies are shown.
-
Enable list limit: Specifies whether the number of elements shown in the result list and list items in controls should be limited.
If this option is enabled, the number of elements must be entered. To do this, you can choose between the global system settings or the local, personal setting for the user.
-
Use system settings: Specifies whether the system settings should be used for the list limit.
If this option is activated, then the global system settings from the Common | DBConnection | ListLimit configuration parameter are used. If the number of results is greater than the defined number, a filter dialog opens.
-
Objects: Personal setting for the object list limit. If the number of results is greater than the defined number, a filter dialog opens.
Usage
-
Form history length: Number of forms available to browse through in the form history. You find the form history in the menus attached to the <Back> and <Forward> buttons in the main toolbar.
-
Entries in the search history: Number of entries available in the search history.
Related topics
On the Program tab, enter the common program settings. These settings are saved in the registry database on the workstation.
Language settings
-
Language: Language used for formatting data, such as date formats, time formats, and number formats.
-
Other user interface language:Language for the user interface. The initial program login uses the system language for the user interface. Changes to the language settings take effect after the program has been restarted.The language is set globally for all One Identity Manager programs, which means the language setting does not have to be configured for each program individually.
Designer database settings
-
Load all system data at program startup: Set the loading behavior for system data.
If this option is not enable, only the tables that are absolutely necessary are loaded when the Designer starts. The rest of the table are loaded in background and the user can already start using the program. The progress of the filling procedure is shown in the program’s status bar.
If this option is enabled, all tables are loaded when the program starts. The user cannot start using the program until all the tables have been loaded. The changes take effect once the Designer has restarted.
-
Load BLOB fields from database on program start: If this option is not enabled, the contents of binary fields are only loaded when they are required.
If the option is enable, this data is already loaded at program startup. The means that program startup takes longer.
The changes take effect once the Designer has restarted.
-
Save databases locally: If this option is enabled, the internal database is not deleted when the program ends. This accelerates restarting the program the next time since only the changes connected with the One Identity Manager database need to be reloaded.
If the option is not enabled the internal database is deleted from the hard disk when the program ends. This means that all the data has to be loaded from the One Identity Manager database when the program is restarted.
-
Use RAM to store the system data (no crash recovery): If this option is not enabled, the internal database is saved on the workstation hard disk.
If the option is enabled, the internal database is loaded into the workstation’s RAM. In this case the database cannot be restore if the program crashes.
The changes take effect once the Designer has restarted.
-
Database directory: If the Save database locally option is enabled, the internal database is stored in the %LocalAppData%\One Identity\One Identity Manager\Designer\Cache directory. You save the database somewhere else by selecting another database directory.
-
Clear local cache: Click the button to empty the local cache directory %LocalAppData%\One Identity\One Identity Manager\Cache.
Related topics
All changed objects in the Designer are created in the internal database. Permissions, formatting rules and side-effects of the Customizer are taken into consideration. Changes made by the user are also recorded in a change log.
To display change data in the Designer
The entries in the change log are grouped by editor. Actions (add, change, and delete) that have been run and changes to the object’s properties with old and new values are displayed in the log.
Table 42: Icons in the change log
|
|
Adds the object. |
|
|
Deletes the object. |
|
|
The object has been changed. |
The following functions are available in the change log:
-
Enable and disable individual changes
You can disable individual changes in the change log. These changes are not transferred to the One Identity Manager database when the data is saved. You can however, re-enable changes at a later date. You can enable or disable each change using the corresponding icon in the change log toolbar.
-
Define change label
It is also possible to create a group of all the changes in the change log, under one label.
-
Before saving the recorded changes in the change log, select the required change label in the Change label menu.
-
To assign individual changes to different change labels, use the Special change label context menu entry in the change log.
When the changes are transferred to the One Identity Manager database, the change label is applied to the relevant changes. For more information about working with change labels, see the One Identity Manager Operational Guide.
-
Saves changes
All changes are saved to the One Identity Manager database as specified. This is done at object level so that, for example, processes are generated and formatting rules are observed. The principle "last writer wins" applies here as opposed to the previous object processing. That means that changes made by a user to object properties in the mean time are overwritten.
Table 43: Functions in the change log toolbar
|
|
Enables change/section. |
|
|
Ignores change/section. |
|
|
Edit a change label. |
|
|
Specifies a default change label. This change label is used for all subsequent changes. |
Related topics
