Company specific localization
XML name |
core:OwnerBasedLocalizationOverrides |
Class name |
de.lobster.scm.coresystemlocalization.db.OwnerBasedLocalizationOverrides |
Rights |
Verwaltung/Konfiguration/Firmenspezifische Sprachverwaltung |
Depending on the company context of the session, company-specific localizations override both the system's standard texts (from the resource bundles) and any entries in the database that may have been added via Localization.
In this way, all content accessible via localization can be customized as required to meet company-specific needs, e.g. to take account of regional or industry-specific peculiarities without changing the standard language, or to avoid conceptual overlaps or confusion within the system landscape of a particular company.
Each individual 'Company specific localization' contains a more or less extensive list of entries, to which the company is assigned as owner, for which these localizations should apply.
Several 'Company specific localizations' can be assigned to the same company. If entries from different lists have the same content (i.e. the same combination of Resource Bundle and Resource Name), the entry from the list with the highest priority value is used.
The permissions for the company specific localization defined on the Roles level control access for the configuration. The same applies to the general permissions (Create, Delete, Read, Change) in Company authorizations, through which one company can give another access to the configuration of its own company specific localizations. In contrast, the specific permission to use company specific localizations has the effect that all company specific localizations of the authorizing company should be operationally effective in the context of other companies.
►NOTE◄ Companies whose 'language use' is influenced by Company authorizations with permission to use the company specific localizations of other companies can only trace the origin of the effective localizations to a limited extent if the authorization does not include the permission to read the company specific localizations. This also requires read access for company specific localizations (for the respective Roles).
The screenshot shows the dialog for managing company-specific localizations.
(1) New, Delete, Cancel, Copy, Save: Company specific localizations can be stored in the database.
(2) Priority: The priority determines which entry should be used for the same Resource bundle and Resource name. The value with the higher priority is used.
(3) Description: The description of the company specific localization.
(4) List of existing company specific localizations.
(5) For the selected company specific localization (4), the overloads can be defined here.
The screenshot shows the dialog for managing overloads.
(1) Add, Remove, Cancel, Copy, Apply: The overloads can be created, changed and removed.
(2) Resource bundle: The resource bundle for the entry.
(3) Resource name: The resource name for the entry.
(4) Value: The value in the respective languages.
(5) The list of defined overloads.
A click on (1) opens a selection menu with the possible entries (2). The selection list is filtered by entering text in (3).