During the startup process the Designer fills an internal database. SQLite is used for the database system. This internal database contains the schema and files from the system part of the connected One Identity Manager database.
Depending on the program’s configuration, the internal database is either loaded into main memory or copied to the hard drive of the workstation. To avoid data inconsistencies, only one instance of the program should be started per database. If the database from the first instance is copied to hard disk then the databases for all other instances are loaded into main memory.
All changes to objects in the program are made in the internal database. Rights, formatting rules and side-effects of the Customizer are taken into consideration. Changes made by the user are recorded in a change log. If the internal database is stored on the hard drive, all additional changes are also logged to this database. This means that you can restore to the last working state after connecting to the database if the program crashes.
When the data is transferred all recorded changes are made to the One Identity Manager database. 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 have been made by a user to object properties in the mean time are overwritten.
Depending on the program settings, the internal database is deleted from the hard drive when the program has finished. This means that all the data has to be loaded from the One Identity Manager database when the program is restarted. If the internal database is not deleted when the program finishes, the next program start up can be accelerated because only changes from the One Identity Manager that is connected have to be loaded.
|Menu||Menu Item||Meaning||Key Combination|
|Database||New connection...||Creates a new database connection.||Ctrl + Shift + N|
|Save to database...||Displays the change log.Changes to the data can be saved to the One Identity Manager database.||CTRL + SHIFT + S|
|Reload data||Data is reloaded from the One Identity Manager database.|
|Compile database...||Starts the Database Compiler.||
CTRL + SHIFT + B
|Change management...||Opens a dialog box for editing change labels.|
|Check data consistency...||Opens the Consistency Editor. This item is available when the logged in user is authorized to use this functionality.|
|Run SQL editor...||Starts the SQL editor. This item is available when the logged in user is authorized to use this functionality.|
|Change password...||Changes current user’s password.|
|Settings...||For configuring program settings.|
|Exit||Exits the program.||Alt + F4|
|View||Navigation||Activates the navigation view.||CTRL + Q|
|Task||Shows/hides task field.||Ctrl + T|
|Error log||Shows/hides the error log.||Ctrl + E|
Shows/hides the view for objects to be imported.
CTRL + I
|Search||Shows/hides search dialog box.||CTRL + SHIFT + F|
|Close current document||Closes the current document.|
|Close all documents||Closes all documents that are open in the document view.|
|Activate document||Shows all open documents in a selection list.|
|Layout||Restores the default layout of the program’s graphical interface. You can save layouts and load them again.|
|Enable quick edit mode||Activates/deactivates quick edit mode.|
Opens the One Identity Manager community website.
Opens the One Identity Manager product support website.
Opens the One Identity Manager training portal website.
Opens the One Identity Manager documentation website.
Opens the search dialog box.
|Help for the Designer||
Opens program help.
|transport history||Display a chronological list of migration, imports and exports of transport packages|
|Info...||Shows the version information for program.|
|Saves changes to the One Identity Manager database.|
|Shows the previous object in the order that the forms were viewed (object history).|
|Shows next object in the order they have already been viewed (object history).|
|Database column help. Clicking on the help icon changes the cursor into the help icon. Then when you click on a column description, tips for using the column are displayed in the form of tooltips.|
|Prints the edit view. Printer settings are configured in the configuration menus.|
The following views are displayed in the Designer: There are several editors used for editing data. Their functionality and methods are tailored to the different configuration tasks.
|Navigation Overview||The navigation structure of the user interface is hierarchical and allows users to drill down to the selection of an object definition. The top level of the hierarchy is used to classify One Identity Manager data into specified categories.|
Overview forms and selected editors are displayed in the document view. When an object is selected in the navigation view, the corresponding overview form is displayed.
|Task view||When an object is selected in the navigation view, the available editors are displayed together with their executable tasks. The relevant editor is opened in the document view when the object is selected.|
|Error log||The program’s error log displays all warnings and error messages that have occurred since the program started up. When the Designer restarts, the error log is reinstalled.|
|Change log||Changes made by the user are recorded in the change log.|
|Change label||In this view, change labels are created and edited.|
To change the program settings
NOTE: General configuration setting are preset in the configuration file Designer.exe.config. In addition, globally valid configuration settings are defined using a configuration file in One Identity’s own format. The configuration files are stored in the program directory.
Enter the program settings for the user on the User tab. These settings are stored in the One Identity Manager database user configuration.
|Clear local cache||Click this button to empty the local cache directory %LocalAppData%\One Identity\One Identity Manager\Cache.|
|Show balloon help||Specifies whether speech bubbles, which provide information about program functionality, are shown in the program.|
|Show large images in the navigation||Specifies whether large or small icons are shown next to the categories in navigation.|
|Show additional icons||Specifies whether icons are shown in the task list in addition to the descriptions.|
|Use single clicks||Specifies whether objects are selected from the result list with a double click or a single click.|
|Visible root nodes||Number of categories shown in the navigation at start up. Changes become effective after a restart.|
|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"||Depending on the setting, the category Getting Started is shown or hidden.|
|Show system data||By setting this option you display comprehensive system information such as system tables, script occurrences, preprocessor dependencies.|
|Enable list limit||Specifies whether the number of elements shown in the result list and list items in controls should be limited.|
|Use system settings||If the option Enable list limit is set, the number of elements has to be entered. There is a choice between the global system setting or the users own setting.|
|Objects||Number of object for your personal list limit. If the number of results is greater than the defined number a filter dialog is opened.|
|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.|
|Search history||Number of entries available in the search history.|
Enter general program settings on the Application tab. These settings are saved in the registry database on the workstation.
Language selection. 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 that the language setting does not have to be configured for each program individually.
|Show additional navigation information||
If this option is set, additional navigation information for separate interface components is shown.
|Load all system data at program startup||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 at program start||If this option is not enabled, the contents of the binary fields is not loaded until needed. 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 database locally||If this option is enable 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 system data (no crash recovery)||If this option is not enable, 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 option Save database locally is set, the database is stored in the directory %LocalAppData%\One Identity\One Identity Manager\Designer\Cache. You save the database somewhere else by selecting another database directory.|