Localizing Sterling Order Management System Software

You can configure according Sterling™ Order Management System Software to the standards of your location.

Prerequisites for localization
There are some prerequisites that you must know before you localize.
Guidelines for latin-1 and UTF-8 character encoding
When implementing Sterling Order Management System Software, use the guidelines specified in this section when using Latin-1 and UTF-8 encoding.
Database overview
You must create the Application Platform database suitable to the data encoding format and character set used. The size of the database fields also depends on the data encoding format and type of character sets used.
Data storage
Besides storing your transactional data, the database also stores configuration data, such as error codes and item descriptions of various attributes. This means that the database may have to store values in a language-specific format.
Directory structure and file names
The Sterling Order Management System Software directory structure must be maintained based on the language and country or region localization.
User interface themes
The user interface theme files specify the screen colors and display fonts to be used. Display fonts are dependent on the languages that must be supported. Some fonts may not support all the languages.
Literals
All Sterling Order Management System Software components use a common resource bundle that contains literals displayed on the screens. Sterling Order Management System Software enables you to customize and localize resource bundles as required.
Validating date, time, and number
Date and number validations are performed using JavaScript. By default, Sterling Order Management System Software provides validation for the en_US locale (English for the United States). The installation locale code is by default set to en_US_EST. To match with the other timezones and avoid any timezone calculation errors, set the locale code and database to en_US_UTC timezone.
Templates
You can store templates with locale-specific information.
Displaying a translated default organization name
In the Applications Manager, some screens display the organization code instead of the organization name in the title. Because organization codes are not translated, these are displayed in English. To have translated organization names displayed instead of organization codes, override the default for the yfs.showOrganizationName.enabled property in yfs.properties.
Localizing calendar pop-up Windows in the console
In the Console, calendar pop-up windows contain literals that must be localized.
Localizing message pop-up Windows in the console
In the Console, message pop-up windows contain literals that must be localized.
Localizing images
Images and icons are stored in JAR files. A separate JAR file can be used for each locale. Both the Applications Manager and Application Console use their own mechanisms for reading images.
Localizing the greex file
A Greex file, also known as advanced XML file, contains the advanced XML condition or Greex Rule that is defined by a user. By localizing the Greex file, you can localize an advanced XML condition or Greex Rule.
Localizing synonyms for catalog search
Sterling Order Management System Software does not provide synonyms for search terms. However, you can configure synonyms for each of the locales your catalog search supports.

Parent topic: Localizing Sterling Order Management System Software