Difference between revisions of "Localization"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 30: Line 30:
{{Note|<br>'''Dates and Times''' are always specified in the User's preferred format, regardless of context.}}
{{Note|<br>'''Dates and Times''' are always specified in the User's preferred format, regardless of context.}}


===Rules and Imports===
===Rules===
'''Date and Time''' values are always in [[User Format]] in Rules and [[Import]] operations.
:* '''Date and Time''' values are always in [[User Format]]
:* Numeric values must be specified in [[Database Format]]


For numeric values, the [[Database Format]] must be used when:
===Imports===
:* Specifying numeric values for a [[Rule]]
:* '''Date and Time''' values are always in [[User Format]]
 
:* Numeric values should ideally be specified in [[Database Format]]
That format is also the ideal format to use when:
:* Supplying numeric data for an [[Import]] operation


Otherwise:
Otherwise:
:* In a '''Pre-Import''' Rule, numeric data is not coming from the database. In that context, the raw data value is seen, exactly as it appears in the incoming data set. If the numeric data is in localized form, the [[Java Localization Functions]] must be used to convert the numeric fields to Database Format. (A method needs to be defined to use them in a Java [[Class]], The method can then be invoked by a Rule action to do convert the numeric data. Or you can save yourself the effort by ensuring that incoming numeric data is in [[Database Format]].)
:* In a '''Pre-Import''' Rule, the incoming numeric values must be converted to Database Format. (The [[Java Localization Functions]] are used. A method must be defined to invoke them in a Java [[Class]], The method can then be invoked by a Rule action to convert the numeric data. Or you can save yourself the effort by ensuring that incoming numeric data is in [[Database Format]] to start with.)


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

Revision as of 01:09, 6 September 2013

About Localization

Localization is the process whereby a user interacts with platform using their preferred language and data formats.

The AgileApps Cloud platform Locale Settings provide a choice of data formats:

Considerations
  • If a user's permissions don't allow them to change their personal settings, then the default settings chosen by the company are effectively fixed.

Working with Localized Values

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. In particular, those settings are used for:

  • Dates and times
  • Numeric data (currencies, numbers, numbers with decimals, and percentage values)
  • Formula Fields that return numeric data
  • Rollup Summary Fields that accumulate numeric data

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:
  • Entering Search data
  • Specifying Filter Criteria for a View

Notepad.png

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

Rules

Imports

Otherwise:

  • In a Pre-Import Rule, the incoming numeric values must be converted to Database Format. (The Java Localization Functions are used. A method must be defined to invoke them in a Java Class, The method can then be invoked by a Rule action to convert the numeric data. Or you can save yourself the effort by ensuring that incoming numeric data is in Database Format to start with.)

Java Programming

Most Java programming entails dealing with the database, which means that data provided in the APIs and returned from them are in Database Format -- except for dates and times, whose format are determined by the combination of the Field settings and the user's Locale Settings.

However, in a JSP Page, data entered by a user will generally be localized, as will the data displayed to the user. To convert between those user format and the database format, use the Java Localization APIs.

Notepad.png

Note:
The localization format is determined by the user who invokes the conversion method. So the same method produces appropriate results for different users.

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

JavaScript Programming

In general, when coding Field Scripts and Form Scripts, form data will be in the User Format. Coders need to be aware of that fact when doing conversions and calculations, and when entering data into the form -- as the platform expects data coming from the form to be in that format.

However, if the code uses AJAX and REST to interact with the platform, the data going to the platform must be in Database Format, as will the data coming back. That format applies to dates and times, as well as numeric data.

To convert between the formats, use the JavaScript Localization Functions.

Template Programming

For a JSP Page-based template, the Java API described above is used to access record data. In that context, Java rules apply.

In other templates, the Velocity programming language is used.

Most template variables are simply inserted into the template, for inclusion in the final document. Template variable data, therefore, is in User Format. However, sophisticated template developers may use conditions to vary the template content based on record data.

When coding a conditional comparison in Velocity, the condition needs to account for the fact that the record data is in User Format. The mechanism for doing so is the Document Template Class, which lets you preprocess the list of data values, adding to it and modifying as needed, before it is seen by the template.

Notepad.png

Note: Data preprocessing is not supported in Email Templates.

With such a class, you can add a new template variable to the record, using the Java Localization Functions to convert record data to Database Format. The template can then use the same format for the comparison value, so you wind up comparing apples to apples.

Of course, you could also convert the comparison value into User Format, and compare oranges to oranges. But then the comparison value would be embedded in the code, where it is harder to change. So the recommended approach is to convert the user data to Database Format.

Learn more: