Defining locales

You can set up locales and associate them with multiple organizations and users within the Hub. Locales are only established by the Hub.

A locale defines a set of standards that enable people within a geographic area to communicate and conduct business transactions in an unambiguous way. For example, the locale defines the unique time zone, language, date/time format, currency, and units of measurement for a specific geographical area.

Locale standards enable international organizations to interact globally and ensure that UOM, currency conversions, and time zones calculations are considered during a transaction. For example, the following locale definitions for organizations in San Francisco and Tokyo enable them to transact business with each other:

Figure 1. San Francisco, United States
  • Locale - California
  • Country/Region - United States
  • Language - English
  • Date/Time - DD/MM/YYYY; HH:MM:SS
  • Time Zone - GMT-8:00
  • Currency - Dollar
  • Unit of Measure - Inch/Pound
Figure 2. Tokyo, Japan
  • Locale - Tokyo
  • Country/Region - Japan
  • Language - Japanese
  • Date/Time - DD/MM/YYYY; HH:MM:SS
  • Time Zone - GMT+9:00
  • Currency - Yen
  • Unit of Measure - Meter/Kilogram
If the currency symbol is not available in a locale, you can find the locales in which it is available by searching the currency under <runtime>/repository/dojo/src/dojo/dojo/cldr/nls. You can override the isccs.dojo.profile.localeList property by adding the locales in the build.properties file that is located in the following path and then build the isccs/isccsdev application.
extensions/bin/build.properties

You can then assign the locale to a user from the Applications Manager.