Editing all translations
NOTE:
-
You can edit translations in different places. When you change a translation, all those places are shown. Before changing a translation, check in the Designer about how it is used.
-
Users can only edit objects and columns for which they have permissions.
-
To edit all translation, users require the Common_Translate program function.
-
Customized default translations are highlighted in yellow in the translation table.
To display and edit all translations in the Language Editor
-
In the Designer, select the Base data > Localization category.
-
Start the Language Editor using Edit translation in database.
-
Select the languages of the translations you want to edit under Select languages in the toolbar.
-
To identify entries for which no translation is currently available, click 
.
-
Use filters to limit how much data is displayed, if necessary.
-
Click in a column header to sort by the selected column.
-
To limit column entries, click the arrow in the column header. This opens a field into which you can enter filter text. If a filter is defined, the column header displays an 
icon. To delete the filter, click the arrow in the column header and select Remove filter.
-
You can also enter add a filter to the toolbar using Filter. The icon applies the filter to the key and the translations. To reset the filter, click the 
. The icon 
can also be used to create and save additional filter queries with wildcards, full-text search or SQL queries.
When you double-click an entry in a translation field to unlock and highlight it, the selected text is automatically copied to Filter in the display.
-
Edit the translations.
-
Double-click the input field to unlock it and enter the translation.
-
Once you have checked a translation, set the translation to Checked.
TIP:
-
Use Ctrl + K to transfer the key value to the translation.
-
Use 
to run a grammar check.
-
Use the Edit context menu to:
After the changes have been committed to the main database, the system data must be recalculated by the DBQueue Processor in order make the new multi-language data available to all system users.
Related topics
Changing translation keys
Use this task to change the key of a translation (Entrykey) in the DialogMultiLanguage table and the source text of all objects that use this key, such as a column name or description.
IMPORTANT: Before changing a key, check in the Designer about how it is used.
To change a key
-
In the Designer, select the Base data > Localization category.
-
Start the Language Editor using Edit translation in database.
-
In the Key column for the required entry, select the Edit key context menu item.
Related topics
Importing translations from the language pack
The default One Identity Manager installation is supplied in English - United States [en-US] and German - Germany [de-DE]. To translate the Web Portal there are other languages available. These are provided in the form of One Identity Manager Language Pack CSV files.
The import:
-
Creates the translations in the DialogMultiLanguage table.
-
Updates currently existing entries based on the key, the table, and the column.
-
Deletes the entries.
To import the language files
-
In the Designer, select the Base data > Localization category.
-
Start the Language Editor using the Edit translation in database task.
-
In the editor toolbar, click 
.
-
Select *.CSV files with the required language and click Open.
This starts the import. The process may take some time.
-
Commit the changes to the main database. Use the Database > Commit to database menu item.
After the changes have been committed to the main database, the system data must be recalculated by the DBQueue Processor in order make the new multi-language data available to all system users.
Process orchestration in One Identity Manager
One Identity Manager uses so called 'processes' for mapping business processes. A process consists of process steps, which represent processing tasks and are joined by predecessor/successor relations. This functionality allows flexibility when linking actions and sequences to object events. Processes are modeled using process templates. A process generator (Jobgenerator) is responsible for converting script templates in processes and process steps into a concrete process in the ’Job queue’.
The One Identity Manager Service handles defined processes. The service has to be installed on the One Identity Manager network server to run the processes. The server must be declared as a Job server in the One Identity Manager database.
The One Identity Manager Service is the only One Identity Manager component authorized to make changes in the target system.
To monitor the process handling, use the Job Queue Info program. For more information, see the One Identity Manager Process Monitoring and Troubleshooting Guide.
Detailed information about this topic
