How to Localize the Aptify Interface

The following is an overview of how an organization localizes the Aptify interface to support multiple cultures:

  1. An organization identifies the supported cultures and creates a Cultures record for each, as necessary. See Defining Cultures for details.
  2. An organization identifies the text strings that require localization and defines the applicable local string for existing Culture Strings already in the system. If a particular string is not already present, the organization creates a new Culture Strings record as needed. Each Culture Strings record contains a sub-type record that identifies the string's appearance for a particular culture. See Working with Culture Strings for details.
    • The Culture Strings service includes a set of records to localize all areas of the Aptify system that are accessible by the typical end user. An organization only needs to add the applicable Local Strings for the organization's supported cultures to these Culture Strings. Aptify's delivered culture strings covers both metadata records (such as Entity Name culture strings) and culture strings that are embedded in code (such as display names in code-based wizards).
    • The Localization Administration application includes a Localization Grid dashboard that can be utilized to simplify the data entry process for translating various culture strings into a localized language. Culture String/Language relationships can easily be modified by directly editing the string within the grid without having to open any Culture Strings records. Note that this is a global dashboard that does not appear by default. See Defining Local Strings with the Localization Dashboard for details.
  3. An organization links new system metadata to Culture Strings as needed (since all of the Aptify-delivered culture strings are already linked to the appropriate locations). See Linking Fields to Culture Strings for details.
  4. As applicable when creating configurations that need to support localization, a developer leverages a set of Aptify-supplied functions that can return the applicable local string for the currently logged-in user. See Programmatically Retrieving Culture String Data.
  5. An organization links each user to a culture. See Linking Users to Cultures for details.
  6. When a user logs into Aptify, the system displays text and captions in that user's specified culture for all data that is linked to a Culture Strings record.


If a particular culture string exceeds the size of a field's label, Aptify automatically truncates the caption and adds an ellipsis (...) to indicate that the field name is too long for the label. An administrator can use the Visual Designer to increase the Label Width on a form to accommodate longer captions, as needed. See Modifying Field Layout with the Visual Designer for information on the Visual Designer.


Note that localization not only applies to the user interface but also to address management to display addresses and phone numbers in the format familiar to the user and to prepare address mailing labels in the format suitable for the destination. See Managing International Addresses for details.


By default, Aptify includes a localization bypass for users linked to Culture ID 1 (English). With the bypass in place, Aptify uses the Culture String data's Base String only and does not load Local String information. An administrator can change the Bypass Culture, if necessary, by adding the BuiltInCultureID configuration attribute to Aptify Shell.exe.config. See About the User Login Configuration Attributes for more information on setting this attribute.


Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.