Languages

There are generally two kinds of languages in the iPIM system: The UI language is the language that is used to localize the user interface elements. The locale is the language that is used to localize data (attributes respectively attribute values). In the “Language” area you can create new locales, edit existing locales or delete locales that are now longer needed.

Using the column header tools you can filter table entries or adjust their sequence. In order to filter table entries you can also use the free-text search. And you can customize the selection of attributes that are shown in the table.

3. Enter a valid ISO code* in the input field “ISO code”.
4. Enter an export ISO code in the input field “Export ISO code”. The export ISO code uniquely identifies the locale when exporting data.

5. Enter the names by which the locale is referenced in the individual locale levels:
   1. Click on the button in the “Description” field. Then you will be directed to another slider that features individual input fields for the different locale levels.
   2. Enter the multiligual names in the respective input fields.
   3. Click on the  BACK button to get back to the previous slider.

6. Enter a positive truth value in the input field “Boolean value for Yes”.
7. Enter a negative truth value in the input field “Boolean value for No”.
8. Since 5.4.1: In the input field “Order”, possibly enter a sequence number for the sorting within the list of locales.
9. Possibly tick the checkbox “Language package” to activate the use of a language package. If activated, this particular language will then be available as a UI language as long as it is implemented as such**.

10. Possibly specify a view right for the locale. Then any user that has the same right assigned to them will be able see the corresponding locale:
    1. Click on the button in the “View right” field.A slider showing the user right directory is shown.
    2. Choose the right from the rights directory. Possibly use the text search to filter the list of rights by a search term.
    3. Click on the right to select it.The previous slider is shown again.

11. Possibly specify a edit right for the locale. Then any user that has the same right assigned to them will have edit rights in the corresponding locale:
    1. Click on the button in the “Edit right” field.A slider showing the user right directory is shown.
    2. Choose the right from the rights directory. Possibly use the text search to filter the list of rights by a search term.
    3. Click on the right to select it.The previous slider is shown again.

• In order to finish the process, click on the SAVE button. A success message is shown. The new locale is now created and it appears in the list of locales.
• In order to cancel the process, click on the CANCEL button.

• Even if a user has the view right that is defined for the respective locale, they also need log in with a client that is related to the locale. Otherwise the user cannot see that particular locale.
• The behavior of edit rights is depending on the respective environment. If the environment is for viewing and editing as most tables are, the view turns read-only when switching the data locale to a locale where the user has the view right but not the edit right. In an environment that is for creating, such as the dialog box for creating texts, the drop-down menu for selecting a data locale only shows locales where the user has edit rights. And if the environment is for editing only, such as in the “Content Management” app, the respective “Save” buttons are disabled.
  

If you do not assign view and edit rights for a locale, any user can see and edit data on this particular locale level.

Edit a locale

In order to edit a locale, proceed as follows:

1. Select the locale as described above.
2. Click on the MANAGE button to call up the corresponding dialog box.
3. Make the desired changes.

• In order to save your changes, click on the SAVE button. A success message is shown.
• In order to cancel the process, click on the CANCEL button.

1. Select the locale as described above.
2. Click on the button. The  CLICK TO CONFIRM button is shown.
3. Click on the  CLICK TO CONFIRM button to confirm the deletion. A success message is shown and the locale vanishes from the list of locales.

Clients

Locales can be related to clients. Users that are logged in with a related client can then see the corresponding locale levels, as long as that they have the corresponding view rights at the same time. Here you can relate additional clients to the selected locale and you can resolve relations to clients.

3. Possibly enter a search term in the search field to filter the list of clients by a search term.
4. Select a client. You can also select multiple clients:
   • In order to select a client, transfer it from the left column to the right column . To do so, click on the client .
   • In order to deselect a client, transfer it from the right column back to the left column. To do this, click on the client.

Using the button and the button you can transfer all the clients from one column to the other column at once.

Remove clients

In order to undo the relation between the selected locale and a related client you need to remove it from the table in the “Clients” card. To do so, proceed as follows:

1. Select the locale as described above.
2. In the table, tick the client you want to remove. You can also tick multiple clients.
3. Click on the REMOVE button in the footer.
   The CLICK TO CONFIRM button is shown.
4. Click on the CLICK TO CONFIRM button to confirm the removal.
   A success message is shown. The relation is now resolved.

Instead of using the REMOVE button, you can also use the "Delete" icon () icon in the respective table row to delete resp. remove individual entries.

FAQ

What kinds of languages are there in the iPIM system?

There are generally two kinds of languages in the iPIM system. The UI language is the language that is used to localize the user interface elements. The locale is the language that is used to localize data, i.e. attributes respectively attribute values.

How is the ISO code of a locale structured?

The required ISO code consists of a language code in lower case letters and a country code in upper case letters, e. g. “deDE” for German or “enGB” for English.

What is the “Order” field used for when creating a locale?

The sequence number entered in the “Order” field determines the position of the locale within the list of locales. The sequence numbers effect that in tables across the board, locales are sorted according to their sequence numbers. For example, localized attribute value names in a list of values are sorted according to the sequence number of their respective locale.

What happens if I tick the “Language package” checkbox for a locale?

If the locale is created as a UI language, it will then be available as a UI language and can be selected via the corresponding menu. Additionally, the property ipim.web.ui.locales has to be maintained accordingly.

What is the view right of a locale used for?

Any user that has the same view right assigned to them will be able to see data on the corresponding locale.

What is the edit right of a locale used for?

Any user that has the same edit right assigned to them will have edit rights in the corresponding locale.

Why can a user not see a locale despite having the assigned view right?

Even if a user has the view right that is defined for the respective locale, they also need to log in with a client that is related to the locale. Otherwise the user cannot see that particular locale.

How do the edit rights of a locale behave in different environments?

The behavior of edit rights is depending on the respective environment. If the environment is for viewing and editing as most tables are, the view turns read-only when switching the data locale to a locale where the user has the view right but not the edit right. In an environment that is for creating, such as the dialog box for creating texts, the drop-down menu for selecting a data locale only shows locales where the user has edit rights. And if the environment is for editing only, such as in the “Content Management” app, the respective “Save” buttons are disabled.

What happens if no view and edit rights are defined for a locale?

If you do not assign view and edit rights for a locale, any user can see and edit data on this particular locale level.

What can I relate a locale to a client for?

Locales can be related to clients. Users that are logged in with a related client can then see the corresponding locale levels, as long as they have the corresponding view rights at the same time.

Rights

The identifier of rights are not shown correctly here as hyphens are shown as half square dashs. In order to search for a particular right in iPIM CC, copy the key to the clipboard and search for the key.