Globalizing record data
By using the language packs that are delivered with IBM® TRIRIGA®, you can globalize record data for your multicultural users. Record data includes internal and translated values.
- Internal values
Internal values are used when consistent or literal strings are required, for example, in a workflow condition, a static filter in a system report, or a formula. Internal values are stored in the main storage table, also named the T_ table. - Translated values
Translated values are stored in the language tables, also called the L_ tables. If the base language is not US English, then translated values include base language values. Secondary language values are always included in translated values. - Changing the base language
You use the Globalization Manager to change the base language. The default language is US English. If you change the base language from the default, US English users become secondary language users and cannot change the internal values. Changing the base language does not affect the translated data or the language values that are already imported. - Globalizing business objects by using the Data Modeler
As an application developer, you use the Data Modeler to globalize your business objects. The Data Modeler uses an object-oriented approach to define and maintain the structures of IBM TRIRIGA data. - Publication of business objects
When you publish a business object that contains localizable fields, language tables are created to store the translated values. If more fields are localizable, the same language table is updated to accommodate the additional localizable fields. - Importing localizable data by using the integration object
The integration object uses database tables, files, and staging tables to import localizable data into IBM TRIRIGA. In the integration object, when you execute the integration, the user language in your profile determines the language that is used to store the imported data. - Importing localizable data by using DataConnect
You can use DataConnect to create instances or translated records for your business objects. DataConnect supports the import of localizable data through the DC_JOB tables, which you can access through the integration object or externally. You must include all data in a record when you use DC_JOB to import globalized data. - Runtime usage of globalized data
When the business objects are published, globalized data is displayed in IBM TRIRIGA record forms, workflow mappings, and reports.
Parent topic: Globalizing applications