Chat now with support
Chat with Support

Identity Manager 8.1 - Configuration Guide

About this guide One Identity Manager software architecture Customizing the One Identity Manager default configuration Adjusting the One Identity Manager base configuration One Identity Manager schema basics 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
Localization in One Identity Manager Process orchestration in One Identity Manager
Setting up Job servers in Designer Configuring the One Identity Manager Service Handling processes in One Identity Manager
Tracking changes with process monitoring Conditional compilation using preprocessor conditions Scripts in One Identity Manager Reports in One Identity Manager Adding custom tables or columns to the One Identity Manager schema Web service integration SOAP Web Service One Identity Manager as SPML provisioning service provider Processing DBQueue tasks Appendix: Configuration files of the One Identity Manager Service

Public holiday properties

Table 70: Public Holiday Properties
Property Description

Date (ISO Format)

The date of the public holiday is entered in ISO format, for example, yyyy-mm-dd where:

yyyy - year, four digits

mm - month, two digits

dd - day, two digits

Public holiday name

Name of the holiday.

Public holiday name (national language)

Name of the holiday in the national language using the national script.

 

Country/State

Name of the country/state for the public holiday.

Processing status

The processing status is used for creating custom configuration packages.

Disabled

Specifies whether the public holiday is disabled or not.

Related Topics

Language-dependent data representation

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.

Detailed information about this topic
Related Topics

Basic rules for using language-dependent data

In order to use multi-language data representation in the One Identity Manager, the following prerequisites need to be fulfilled:

  • The language is set up in the database and labeled with Select in front-end.
  • A fallback language for the database is set. In default installation of the One Identity Manager, the language used is English - United States [en-US]. This language is used if there is no translation available for a language-dependent data break down in the user’s requested language.
  • The option Multilingual has to be set on the column definitions in order to use multi-language display text.
  • Source and target of the translation are known.
  • #LD notation is used for outputting language-dependent data from within VB.Net expressions. #LD text is automatically extracted for translation. To do this, a column must be labeled as #LD content.

The translations are stored in the table DialogMultiLanguage. A key, the language and the translation are entered into the table.

Example

The text Resource should be displayed in the login language English - United States [en-US] as the column name (DialogColumn.Caption) for the column QERResource.Ident_QERResource. The column name Ressource should be used for the login language German - Germany [de-DE].

The column QERResource.Ident_QERResource contains the value Car. A user with the login language English - United States [en-US] should be shown the value Car. A user with the login language German - Germany [de-DE] should be shown the value Auto.

Table 71: Example of language-dependent entries in the DialogMultiLanguage table
Column Name Key Language Value
DialogColumn.Caption Resource English - United States [en-US] Resource
Resource German - Germany [de-DE] Ressource
QERResource.Ident_QERResource Car English - United States [en-US] Car
Car German - Germany [de-DE] Auto
Related Topics

Labeling columns for translation

Columns must be marked for translation in order to enter multilingual captions.

To label a column for translation

  1. In Designer, select One Identity ManagerSchema.
  2. Select the table and start the Schema Editor with the task Show table definition.
  3. Select the column and then the Column properties view.
  4. Select the Column tab and edit the Multilingual property. Specify the following settings. You can combine the values. The combination of values determines the resulting translation.

    Table 72: Permitted values for multilingual columns
    Value Meaning
    Translation target The column content is displayed in translation.
    Translation source The column supplies the translation.
    #LD content The column has contents in #LD notation. The contents are extracted for translation.

    Without fallback translation source

    The text store is not used as fallback for the column.

  5. 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.

    • Switch to the Language dependencies tab. Under Translation source, select the column that is to be used as the translation source.

      NOTE: Ensure that the column used as a translation source has been labeled with Translation source.

Example: a column is translation target and source

The contents of the QERResource.Ident_QERResource column are to be translated. The Ident_QERResource column contains the value Car. A user with the login language English - United States [en-US] should be shown the value Car. A user with the login language German - Germany [de-DE] should be shown the value Auto. The actual translation should be maintained in the QERResource.Ident_QERResource column.

  • Label the QERResource.Ident_QERResource column in the Multilingual property with Translation target.
  • Label the QERResource.Ident_QERResource column in the Multilingual property with Translation source.
  • In Language Editor, translate the entries for the Ident_QERResource column of the QERResource table.

When the column is loaded, it is determined that QERRessource.Ident_QERResource should be translated. For translation, the relevant key for the QERRessource.Ident_QERResource column is determined from the DialogMultiLanguage table and the value saved for the user’s login language is displayed.

Example: a column is translation target and takes its translation from another translation source

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.

  • Label the JobEventGen.ProcessDisplay column in the Multilingual property with the values Translation source and #LD content.
  • Label the DialogProcess.DisplayName column in the Multilingual property with Translation target and as the Language dependecy, enter the JobEventGen.ProcessDisplay column.
  • In Language Editor, translate the entries for the ProcessDisplay column of the JobEventGen table.

When the column is loaded, it is determined that DialogProcess.DisplayName should be translated. For translation, the relevant key for the JobEventGen.ProcessDisplay column is determined from the DialogMultiLanguage table and the value saved for the user’s login language is displayed.

Related Topics
Related Documents