Difference between revisions of "Localization"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 27: Line 27:
''Exception:''
''Exception:''
:* In a '''Pre-import''' Rule, numeric data is not coming from the database. In that context, the raw data can be accessed, exactly as it is in the data set. If the numeric data is in localized form, the [[Java Localization Functions]] can be used to convert the numeric fields to Database Format. (To access them, click the '''[Functions]''' button that appears when defining a value or formula.)
:* In a '''Pre-import''' Rule, numeric data is not coming from the database. In that context, the raw data can be accessed, exactly as it is in the data set. If the numeric data is in localized form, the [[Java Localization Functions]] can be used to convert the numeric fields to Database Format. (To access them, click the '''[Functions]''' button that appears when defining a value or formula.)
===REST Programming===
When using the REST API, all data is specified in ''Database Format'':
{{:Database Format}}


===Java Programming===
===Java Programming===


===JavaScript Programming===
===JavaScript Programming===
===REST Programming===
When using the REST API, all data is specified in ''Database Format'':
{{:Database Format}}

Revision as of 01:45, 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 determine a variety of data formats:

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.
In those cases, the Database Format must be used:

Notepad.png

Note:
Dates and Times are always specified in the User's preferred format, regardless of context.

Rules and Imports

The Database Format for numeric values must also be used when:

  • Specifying numeric values for a Rule

Ideally, that format will also be used when:

  • Supplying numeric data for an Import operation

Exception:

  • In a Pre-import Rule, numeric data is not coming from the database. In that context, the raw data can be accessed, exactly as it is in the data set. If the numeric data is in localized form, the Java Localization Functions can be used to convert the numeric fields to Database Format. (To access them, click the [Functions] button that appears when defining a value or formula.)

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

Java Programming

JavaScript Programming