Difference between revisions of "Localization"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
Line 14: | Line 14: | ||
There are exceptions, however. When specifying numeric values that will be used in a direct comparison against database data, the [[Database Format]] must be used. This situation occurs when: | There are exceptions, however. When specifying numeric values that will be used in a direct comparison against database data, the [[Database Format]] must be used. This situation occurs when: | ||
:* Entering [[Search]] data | :* Entering [[Search]] data | ||
:* Specifying [[Filter Criteria]] for a [[View]] | :* Specifying [[HowTo:Filter a View to Restrict the Records it Displays|Filter Criteria]] for a [[View]] | ||
:* Supplying values for an [[Import]] operation | :* Supplying values for an [[Import]] operation | ||
:* Specifying values in a [[Rule]] that fires ''before'' data is committed to the database. (Rules that fire ''after'' data is committed see data in Database Format.) | :* Specifying values in a [[Rule]] that fires ''before'' data is committed to the database. (Rules that fire ''after'' data is committed see data in Database Format.) |
Revision as of 01:05, 23 August 2013
About Localization
Localization is the process whereby a user interacts with platform using their preferred language and data formats.
Working with Localized Values
Platform Settings
The Locale Settings
- My Settings > Locale Information - Formats chosen by the user for dates, times, and numbers, plus language.
- User Settings - Formats set for the user by the admin.
- Company Information Settings - Default user formats, and the Currency format, which can be changed only by an admin.
The Translation Workbench can be used to support additional languages.
Interface Interactions
When working with the platform GUI, data is typically displayed and entered in User Format, as determined by the user's Locale Settings.
There are exceptions, however. When specifying numeric values that will be used in a direct comparison against database data, the Database Format must be used. This situation occurs when:
- Entering Search data
- Specifying Filter Criteria for a View
- Supplying values for an Import operation
- Specifying values in a Rule that fires before data is committed to the database. (Rules that fire after data is committed see data in Database Format.)
Java Programming
JavaScript Programming
REST Programming
When using the REST API, all data is specified in Database Format:
Field Format Date, DateTime, Time Currency, Number,
Number with Decimal,
Percent- No currency symbol or percent sign
- No grouping characters (e.g. commas) in whole-number portion
- A decimal point (.) before fractional portion
Ex: 84954.32
Lookup - The Record ID of a record in the target object.
Ex: 123A456B78
Multi Object Lookup Ex: 849Z:123A456B78