When you are configuring the One Identity Manager tools’ user interfaces you can add icons and images for displaying in different parts of them. The default version of the One Identity Manager supplies the icons and images that you can use for configuring the user interface and to create reports. Predefined configurations are maintained by the schema installation and cannot be edited apart from a few properties.
Icons are required to be in PNG format with sizes of 16x16 pixels, 24x24 and 32x32 pixels for the graphical interface.
Icons are required for the following use cases.
|Normal||Icons showing an enabled state. These icons must exist in the One Identity Manager database.|
|Inverted||Icons that show and enabled state on a black background. These icons can be converted automatically.|
|Disabled||Icons showing a disabled state. These icons must exist in the One Identity Manager database.|
To add an icon
To add images for reports
The image is displayed with certain important image properties.
The One Identity Manager supports language dependent representation of data. You can use this feature to edit display text in different languages for the One Identity Manager tool user interfaces. You can also create multi-language text for process information output, script processing as well as processing messages.
The One Identity Manager default installation is supplied in the languages "English - United States [en-US]" and "German - Germany [de-DE]". You can use other languages if required. To do this it is advisable to translate the required text before starting to use the One Identity Manager. There is a Language Editor in the Designer to help you do this. A special control element is provided in the One Identity Manager tools which aids multi-language input.
In order to use multi-language data representation in the One Identity Manager, the following prerequisites need to be fulfilled:
The translations are stored in the table DialogMultiLanguage. A key, the language and the translation are entered into the table.
The text "Resource" should be shown as column name for the column Ident_QERResource if the login language is "English - United States [en-US]" and "Ressource if the login language is "German - Germany [de-DE]". The value "Car" is entered in the column Ident_QERResource. If the login language is "English - United States [en-US]", the word "car" should be shown. If the login language is "German - Germany [de-DE]", the word "Auto" should be shown.
|DialogColumn.Caption||Resource||English - United States [en-US]||Resource|
|Resource||German - Germany [de-DE]||Resource|
|Ressource.Ident_QERResource||Car||English - United States [en-US]||Car|
|Car||German - Germany [de-DE]||Auto|
Columns must be marked for translation in order to enter multilingual captions.
To mark a One Identity Manager database column for translation
NOTE: Select a table column in the Designer, then you can start the Schema Editor from the task Show column definition.
|Translation target||The translated column content is displayed.|
|Translation source||The column supplies translations.|
|#LD content||The column has content in #LD notation. The contents are extracted for the translation.|
A translation target is normally the same as the translation source. If the translation, however, is taken from another translation source, enter this additionally as a language dependency.
NOTE: The column that is used as translation source, must be labeled as "translation source".
You want the contents of the column QERRessource.Ident_QERResource to be translated. The value "Car" is entered in the column Ident_QERResource. If the login language is "English - United States [en-US]", the word "car" should be shown. If the login language is "German - Germany [de-DE]", the word "Auto" should be shown. The translation itself maintained in the column QERRessource.Ident_QERResource.
When the column is loaded, it is determined that QERRessource.Ident_QERResource should be translated. The corresponding key for QERRessource.Ident_QERResource is taken from the table DialogMultiLanguage as translation and displayed in the current user's login language.
The action is displayed in the Manager process view in the current user's login language. The contents of the column DialogProcess.DisplayName are taken from the column JobEventGen.ProcessDisplay. The column JobEventGen.ProcessDisplay may use #LD notation to create the display string.
When the column is loaded, it is determined that DialogProcess.DisplayName should be translated. The corresponding key for JobEventGen.ProcessDisplay is taken from the table DialogMultiLanguage as translation and displayed in the current user's login language.
Translations, which occur frequently or cannot be associated with a particular database column, can be stored in text memory (table QBMTranslationAddOnSource). The Web Portal, for example, takes its translations from the text store. In the same way, output text from database triggers is found in the text store. The text store is also used as a fallback when a fitting translation cannot be found through other translation sources. You can also reference the text store as a translation source.
To enter an item in the text store