Localization

Clients that do not use data-localized instances are unaffected by localization limitations.

The LFSO Configuration Editor feature is not data-localized. The feature displays system values and does not display names and descriptions for the user’s locale.

You can use Configuration Editor to add or delete entities within a localized instance. When an entity is added, Configuration Editor creates a placeholder for each supported locale and assigns the application value to those placeholders. Later, placeholder values must be configured for each specific locale. For example, if a job is created that has a system value of “Check Out“, you may need to configure the job’s English locale value to “Cashier”.

When an entity is deleted, Configuration Editor removes the associated system and localized values.

For clients using data-localized instances, users do not see configuration changes in their data-localized tables. The Configuration Editor cannot be used to perform updates to existing localized entities. Although the Editor can update system values, the Editor cannot reconfigure the values required for each specific locale. Changes to data-localized values must happen outside of the Configuration Editor.

For information about the risks associated with using LFSO configuration pages in conjunction with the Configuration Editor, contact Infor Consulting Services.