localization user guide - ibm - united states filechapter 3. localizing lists .....7 types of lists...

IBM TRIRIGA Application PlatformVersion 3 Release 4.0

Localization User Guide

��

NoteBefore using this information and the product it supports, read the information in “Notices” on page 37.

This edition applies to version 3, release 4, modification 0 of IBM TRIRIGA Application Platform and to allsubsequent releases and modifications until otherwise indicated in new editions.

© Copyright IBM Corporation 2011, 2014.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Chapter 1. Localizing applications . . . 1

Chapter 2. Multicultural Support . . . . 3US English . . . . . . . . . . . . . . . 3One Language (Not US English) . . . . . . . . 4Official Language with Multilingual Workforce . . . 4Multilingual with No Official Language . . . . . 5

Chapter 3. Localizing lists . . . . . . . 7Types of lists . . . . . . . . . . . . . . 7Specifying List Items in Alternate Languages . . . 7Defining Date or Date and Time Format . . . . . 8

Custom Date Formats . . . . . . . . . . 8

Chapter 4. Application Data . . . . . . 13Base Language Setup . . . . . . . . . . . 13Data Modeler. . . . . . . . . . . . . . 14

Business object fields . . . . . . . . . . 14Business Object Publish . . . . . . . . . 15Internal Value . . . . . . . . . . . . 15Modification of Internal Values . . . . . . . 15Object Migration . . . . . . . . . . . 16

Application Data Import . . . . . . . . . . 16Language Packs . . . . . . . . . . . . 16Language Manager . . . . . . . . . . . 17

Record Runtime . . . . . . . . . . . . . 17Workflow Runtime . . . . . . . . . . . . 18Query Runtime . . . . . . . . . . . . . 18

Base Language Users . . . . . . . . . . 18Secondary Language Users . . . . . . . 18

Runtime Filters . . . . . . . . . . . . 19Static or System Filters . . . . . . . . . 19My Reports . . . . . . . . . . . . . 19

Community Reports . . . . . . . . . . 19

Chapter 5. Label Manager . . . . . . 21Importing a File of Translated Values . . . . . . 21Translate Specific Items . . . . . . . . . . 22

Applying Translation to Fields . . . . . . . 22Applying Translation to Page Messages . . . . 23Applying Translation to Tab Messages . . . . 23Applying Translation to Label Tooltips . . . . 23Applying Translation to Icon Tooltips. . . . . 24Adding New Application Fields, Messages, andLabel Tooltips . . . . . . . . . . . . 24

Using Translated Values . . . . . . . . . . 24

Chapter 6. Export of Labels andApplication Data . . . . . . . . . . 27Exporting Labels and Application Data forTranslation . . . . . . . . . . . . . . 28

Chapter 7. Currency . . . . . . . . . 31Creating currency rates . . . . . . . . . . 31Modifying currency rates . . . . . . . . . . 32

Chapter 8. Managing Units of Measure 33Configuring UOM Type . . . . . . . . . . 33Configuring UOM Values. . . . . . . . . . 34Rounding Rules for UOM Values . . . . . . . 35

Notices . . . . . . . . . . . . . . 37Privacy Policy Considerations . . . . . . . . 38Trademarks . . . . . . . . . . . . . . 39

© Copyright IBM Corp. 2011, 2014 iii

iv © Copyright IBM Corp. 2011, 2014

Chapter 1. Localizing applications

You can use the IBM® TRIRIGA® Application Platform to display TRIRIGA textand data in other languages. To do this, you can customize labels and modify unitsof measure, dates, and currency.

© Copyright IBM Corp. 2011, 2014 1

2 © Copyright IBM Corp. 2011, 2014

Chapter 2. Multicultural Support

Multicultural support, also known as globalization, is the process of organizing anapplication so that it can be configured to work in different countries and indifferent languages. You can use IBM TRIRIGA Application Platform to translatemessages and any other text content that appears into the language you want.

However, with multicultural support, you can have logic issues relate to thedifferent ways that workflows must behave when working in different languagesor countries. For example, business logic for an application can vary because ofdifferent regulations in different places.

Multicultural support involves the configuration and translation efforts needed tomeet the requirements of the application. The globalization requirements forapplications vary considerably; however, they usually support one of the followingscenarios:

US EnglishAn application is developed to be used by people whose languagepreference is US English to process data that uses only US English.

One Language (Not US English)An application is developed to be used by people who all have the samelanguage preference to process data in that same language.

Official Language with Multilingual WorkforceWorkers who prefer different languages work with data that is all in thesame language.

Multilingual with No Official LanguageWorkers who prefer different languages work with data that is in multiplelanguages.

US EnglishYou can develop applications to be used by people whose language preference isUS English to process data that uses only US English.

All business objects that come with the IBM TRIRIGA Application Platform arewritten in US English and use units of measure and currency appropriate for theUnited States.

If an application was developed in a language other than US English, multiculturalsupport can be required to use the application on the IBM TRIRIGA ApplicationPlatform in US English.

You can use globalization features to adjust an application to an organization.Suppose that your organization decides that some labels or descriptions suppliedwith an application are not right for business practices. Instead of directlymodifying any forms, you can define a language and supply translations forspecific labels and descriptions to match business practices. If you customize anapplication this way, you can avoid incompatibilities between modified businessobjects and business objects.


One Language (Not US English)You can develop applications to be used by people who all have the samelanguage preference to process data in that same language.

In some cases, if your company uses a language other than US English as thepreferred language, you expect to see the formatting and units for numericquantities that are different from what is customary in the United States. Except forthe formatting of numbers, this scenario is well supported. Before using thisscenario, perform the following tasks:v Add the language to the Language list if needed.v Use the Label Manager to provide translations of all labels, tab information,

system messages, tooltips, and classifications in the Classification hierarchy.v Use the Label Manager and the List Manager to provide translations for all lists

that should be translated.v Access different pages under the Tools menu to create translations of Approvals,

CTQ Dynamic Lists, News, Notification Content, and User Message records.v If none of the date or time formats shipped with the IBM TRIRIGA Application

Platform are appropriate for your business environment, you can add theformats in the List Manager.

v Add the currency type to the List Manager if needed.v Translate Units of Measure and UOM Values in the Administration menu if

needed.v Translate all reports and help text.v Establish language, currency, time zone, date format, date time format, area unit,

and length unit values in the My Profile page.v Enable bidirectional support and specify the direction of user-generated text in

the My Profile page if needed.

Attention: Evaluate your use of currencies during implementation and add orremove currencies pertinent to your company needs before adding data records.Otherwise you can cause conversion issues or data loss on those records.

If you use a language that is not US English, you can have a few problems. Forinstance, IBM TRIRIGA Application Platform does not explicitly allow theformatting of numbers. Also, if you change the name of a classification, instead ofusing the Label Manager to translate it, the workflows can break if they rely on thename of the classification.

Official Language with Multilingual WorkforceIn some cases, a company can conduct its internal business in one officiallanguage, which can be different from the language of preference of each user. Theapplication is much easier to use if information such as field labels and help text ispresented in the language of preference of each user.

Except for the formatting of numbers, such scenario is well supported. Thefollowing activities are useful:v Identify the secondary languages to be supported.v Add the official language and the supported secondary languages to the

Language list if not already there.v Use the Label Manager to provide translations of all labels, tab information,

system messages, tooltips, and classifications in the Classification hierarchy.


v Use the Label Manager and the List Manager to provide translations for all liststhat should be translated.

v Access different pages under the Tools menu to create translations of Approvals,CTQ Dynamic Lists, News, Notification Content, and User Message records intothe official Language and other supported languages that are not US English.

v If none of the date or time formats shipped with the IBM TRIRIGA ApplicationPlatform are appropriate for the intended business environment, addappropriate formats in the List Manager.

v Add the currency types to the List Manager if needed.v Translate Units of Measure and UOM Values in the Administration menu if

needed.v Translate all reports into the official language.v Translate all help text into the official language and the other supported

languages that are not US English.v Establish language, currency, time zone, date format, date time format, area unit,

and length unit values in users My Profile page.v Enable bidirectional support and specify the direction of user-generated text in


Attention: Evaluate your use of currencies during implementation and add orremove currencies pertinent to your company needs before adding data records.Failure to do so before creating records could cause conversion issues or data losson those records.

If you work with the Official Language with Multilingual Workforce scenario, youcan have a few problems. For instance, any dates or times entered as text are notformatted according to the preference in the My Profile page; they are seen exactlyas entered. Also, you cannot explicitly format numbers with IBM TRIRIGAApplication Platform. Some workarounds may be available for some combinationsof formatting and computing environments.

Multilingual with No Official LanguageIn this scenario, workers who prefer different languages work with data that is inmultiple languages.

In an environment where there is a multilingual workforce but no officiallanguage, users conduct business in multiple languages. To support this scenario,you must:v Add languages that will be supported to the Language list if needed.v Use the Label Manager to provide translations of all labels, tab information,

system messages, tooltips, and classifications in the Classification hierarchy thatshould be translated.

v Use the Label Manager and the List Manager to provide translations for all liststhat should be translated.

v Access different pages under the Tools menu to create translations of Approvals,CTQ Dynamic Lists, News, Notification Content, and User Message records intoall languages that will be supported.

v If none of the date or time formats shipped with the IBM TRIRIGA ApplicationPlatform are appropriate for the intended business environment, addappropriate formats in the List Manager.

v Add currency types to the List Manager if needed.

Chapter 2. Multicultural Support 5

v Translate Units of Measure and UOM Values in the Administration menu ifneeded.

v If you need to have reports in multiple languages, you must create multipleversions of the reports. When you create these reports you can choose to filterthe data by the triLanguageLI field on the record so your reports do not mixdata in multiple languages.

v Translate help text into all supported languages.v Establish language, currency, time zone, date format, date time format, area unit,

and length unit values in the My Profile page.v Enable bidirectional support and specify the direction of user-generated text in


Attention: Evaluate your use of currencies during implementation and add orremove currencies pertinent to your company needs before adding data records.Failure to do so before creating records could cause conversion issues or data losson those records.

Some potential problems for supporting this scenario follow.v The values of list and classification fields are displayed in the preferred

language of the user. This can be different from the languages that the fieldsappear in, since they appear in the language in which they are entered. Theautomatic translation of list values may be good or bad.

v Any dates or times entered as text are not formatted according to the preferencein the My Profile page and are displayed exactly as entered.

v You cannot explicitly format numbers with the IBM TRIRIGA ApplicationPlatform. Some workarounds may be available for some combinations offormatting and computing environments.


Chapter 3. Localizing lists

You can localize choices that appear in List fields so users can see list choices intheir preferred language.

Types of listsIBM TRIRIGA provides lists of predefined values for many fields in the userinterface. These lists contain valid data and you can select the required value froma list. You can improve data integrity by restricting users to select approved valuesfrom a list for entry into a field. Lists ensure that information is relevant,consistent, and correctly entered.

You can use the List Manager to create and manage radio button lists, drop-downlists of static values, dynamic lists derived from values in the database, anddependent lists.

In the List Manager, you can organize lists by the menu with which they areassociated. For example, the Project menu has lists like project type, projectbusiness object type, project transaction type, severity, and work order type.

Static ListA Static list contains values that are fixed and do not change often, forexample, states, colors, countries.

Dependent ListDependent lists consist of two static lists, one parent list and one or morechild lists. For example, a business object contains two list fields namedCountry and State. If the State list is defined as a dependent list, the list ofvalues available for the State field is dependent on the Country selected.

Dynamic ListDynamic lists are directly tied to a business object. For example, a newmodel number in a business object in the Asset menu. As new models arereceived, they are entered into the Asset business object. These modelnumbers are immediately available in a Model list that is used with a PartsRequest form. You do not need to manually specify the new modelnumbers in the Parts Request form because the Model list was dynamicallycreated from the Asset business object.

Attention: Evaluate your use of currencies during implementation and add orremove currencies according to what your company needs before adding datarecords. Failure to do so before creating records could cause conversion issues ordata loss on those records.

Specifying List Items in Alternate LanguagesYou can localize choices that appear in List fields so users can see list choices intheir preferred language.

About this task

To specify list items in alternate languages, use the Label List action in the ListManager.


Note: In the List Manager, you can use the Label List in both the manual list andthe dynamic list to edit the translations directly, and save the results.

Your application may use some lists that should not be translated. For example,you should not translate a list of postal abbreviations for the states of a country orprovinces. These normally need to be in their original form so that the post officefrom that country can read the abbreviations.

Procedure1. Navigate to Tools > Administration > Lists. The system opens the List

Manager. The left panel has two sections: Manage By and Filter By.2. In the Manage By section, click the menu and select Name.3. Click the radio button to the left of the list name for which you want to

provide entries in another language. The values for that list appear in the rightpanel.

4. To filter lists by a module, select the check box to the left of the module namein the Filter By section. The lists in the Manage By section refresh to show onlylists available for that module. To further refine the lists shown in the ManageBy section, select more than one module in the Filter By section.

5. Click Label List. The system opens the List Labels form containing Valuescarried from the list selected in the Manage By section.

6. Select the appropriate language from the Select Language menu.7. Enter the labels in the selected language.8. Save your changes.

Defining Date or Date and Time FormatIf the format you want to use does not exist, you can define a different date formator date and time format.

About this task

Use the List Manager to complete this task.

Procedure1. Select Tools > Administration > Lists.2. In the Manage By section, expand the menu and select Name.3. Select DateFormat or DateTimeFormat.4. In the right panel, specify the new format in the Value field.5. Save your entries.

Custom Date FormatsYou can define different date formats or date time formats from those shippedwith the IBM TRIRIGA Application Platform. In the List Manager, you can use theDateFormat list to control the formatting of Date fields.

The standard date-only formats are:

Format Example

dd/MM/yyyy 06/03/2007

dd-MMM-yyyy 06-Mar-2007


MM/dd/yyyy 03/06/2007

MMM dd, yyyy Mar 06, 2007

MMMMM dd, yyyy March 06, 2007

yyyy.MM.dd 2007.06.03

yyyy/MM/dd 2007/06/03

yyyy-MM-dd 2007-06-03

You can use the DateTimeFormat list to control the formatting of Date and Timefields. Not all of the formats in the DateTimeFormat list can be translated. Thestandard date and time formats that can be translated are as follows:

Format Example

dd-MM-yyyy HH'h'mm 06-03-2007 13h44

dd-MM-yyyy HH'h'MM'min' 06-03-2007 13h44min

dd-MMM-yyyy HH:mm 06-Mar-2007 13:44

dd/MM/yyyy HH'h'mm 06/03/2007 13h44

dd/MM/yyyy HH:mm 06/03/2007 13:44

dd/MM/yyyy hh:mm a zzz 06/03/2007 01:44 PM PST

dd/MM/yyyy HH:mm zzz 06/03/2007 13:44 PST

dd/MM/yyyy HH:mm:ss 06/03/2007 13:44:25

dd/MM/yyyy hh:mm:ss a zzz 06/03/2007 01:44:25 PM PST

dd.MM.yyyy HH:mm:ss 06.03.2007 13:44:25

MM/dd/yyyy HH:mm 03/06/2007 13:44

MM/dd/yyyy hh:mm a zzz 03/06/2007 01:44 PM PST

MM/dd/yyyy HH:mm zzz 03/06/2007 13:44 PST

MM/dd/yyyy HH:mm:ss 03/06/2007 13:44:25

MM/dd/yyyy hh:mm:ss a zzz 03/06/2007 01:44:25 PM PST

MMMMM dd, yyyy hh:mm a zzz March 06, 2007 01:44 PM PST

yyyy-MM-dd HH.mm 2007-03-06 13.44

yyyy-MM-dd hh:mm a zzz 2007-03-06 01:44 PM PST

yyyy.MM.dd hh:mm a zzz 2007.03.06 01:44 PM PST

yyyy/MM/dd hh:mm a zzz 2007/03/06 01:44 PM PST

yyyy/MM/dd HH:mm zzz 2007/03/06 13:44 PST

The IBM TRIRIGA Application Platform does not directly control the language inwhich these names and abbreviations appear. They appear in the same language,independent of the language specified by the user in their My Profile. Thelanguage in which the names and abbreviations appear is controlled by a layer ofsoftware that runs on top of the IBM TRIRIGA Application Platform. The specificsvary with the computing environment in which the platform runs.

You can use the List Manager to add or modify formats in the DateFormat orDateTimeFormat lists. The IBM TRIRIGA Application Platform treats the text inDateFormat and DateTimeFormat as a sequence of characters that specify how to

Chapter 3. Localizing lists 9

format dates and times. For formatting dates and times, the characters in theseformats are considered to be one of two kinds:v Copied characters, which are copied from the format when creating a formatted

date or time. For example: / - : are copied characters.v Interpreted characters, which are interpreted with whatever meaning is assigned

to them. The interpretation of the interpreted character is copied into theformatted date or time. For example, a is interpreted to mean AM or PM,depending on the time portion of the value being formatted.

The letters from A to Z and from a to z are interpreted characters. All othercharacters are copied characters. Although all letters from A to Z and from a to zare interpreted characters, an interpretation has not been assigned to all letters. Thefollowing paragraphs describe the interpretation of letters in formats.

The following chart shows the interpretation for letters used to format parts ofdates. The number of times a letter is repeated affects the way it formats a part ofa date. Also, upper and lowercase letters have different interpretations.

Letter Sequence Description Examples

d One or two digit day inmonth

1 - 31

dd Two digit day in month 01 - 31

DDD Three digit day in year 001 - 366

EEE Abbreviated day of week Mon - Sun

EEEE Full day of week Monday - Sunday

M One or two digit month 1 - 12

MM Two digit month 01 - 12

MMM Three letter monthabbreviation

Jan - Dec

MMMMM Full month name January - December

y One or two digit year 0 - 99

yy Two digit year 00 - 99

yyyy Four digit year 1999, 2000, 2010

The following chart shows the interpretation for letters used to format parts oftimes. The number of repetitions of a letter affects the way it formats a part of atime and that upper and lowercase letters have different interpretations. If youinclude letters to format time in a format for date-only values, it will look like thetime part of the value is midnight.

Letter Sequence Description Examples

a AM or PM indication AM or PM

h One or two digit hour inam/pm (1-12)

1 - 12

hh Two digit hour in am/pm(01-12)

01 - 12

H One or two digit hour in day(0-23)

0 - 23

HH Two digit hour in day (00-23) 00 - 23


m One or two digit minute inhour

0 - 59

mm Two digit minute in hour 00 - 59

s One or two digit second inminute

0 - 59

S One, two, or three digitmillisecond

0 - 999

ss Two digit second in minute 00 - 59

SSS Three digit millisecond 000 - 999

z or zzz Three letter time zoneabbreviation

EST, CST, and so on.

Z Time zone with respect toGMT

-0500, -0600, and so on.

Chapter 3. Localizing lists 11

Chapter 4. Application Data

You can mark or flag a business object field as localizable and export the data fortranslation. The data language packs for the data shipped are included. However,if you want to enter your own data in the languages you support, you must do sothrough the normal medium like forms.v Base Language is the language that the platform uses when processing

localizable data. Base values refer to the localizable data stored in the languagestorage and assumed to be written in the base language. The base languagedetermines what values are displayed in forms if there is no value in thelanguage preference of the user’s My Profile record. For example, if anenvironment is set to have Brazilian Portuguese as the base language, and aFrench user is interacting with a geography record where the description fielddoes not have a French translation, the application tries to display the BrazilianPortuguese value of the field.

If the base language remains US English, which is the default base language fornew and upgraded installations, data from US English users is stored in the mainstorage (T_ tables) and not in the language storage. On the other hand, if the baselanguage has been swapped to non-US English, then data from US English users isstored as localized values in the language tables and is treated the same as anysecondary language in the system.v Secondary Languages are the languages other than the base language of the

system. Secondary or Language values refer to the different translations of thelocalizable data written in the supported secondary languages and stored in thelanguage tables.

If the base language has been swapped to non-US English, then data from USEnglish users is stored as localized values in the language tables and is treated thesame as any other secondary language in the system.v Internal Value is the value of a localizable data that is stored in the main

storage (T_ tables) and may be specifically used in application logic forworkflow conditions, formulas, system report filters, and so on.

If the base language remains US English, US English users can update the internalvalues as their localized values are persisted in the main storage.

Base Language SetupYou must set up a base language for the system so that the system knows how tomanage the application records and system data, especially if there aremulti-language users in the system.

You can use the Language Manager in the Administrator Console to change thebase language of the system. In the Language Manager, you select the languagedata pack you want as the new base language. By default, the base language is USEnglish upon new installation or upgrade.

If an environment uses a language other than US English and you have swappedthe base language, you can swap the base language back to US English withoutimporting the US English data pack.


When an admin swaps the base language, the base language value is inserted intothe language table with a base language value, a language id similar to the baselanguage specified. The platform retrieves and stores updates of the record to thislanguage storage but only updates the entries of the same language as the user.

Note: If the language pack was successfully uploaded to the server, the baselanguage is swapped while the import of each XLIFF file is ongoing, even if one ofthe XLIFF files inside the pack has encountered import errors.

Data ModelerThe Data Modeler is a tool used to define and maintain the structures of data inIBM TRIRIGA, using a object-oriented approach.

Business object fieldsIn the Data Modeler, you can select the Localizable check box in a business objectfield to distinguish between localizable and non-localizable data. If you are anapplication developer, you select this property if a field can have a secondarylanguage other than US English.

Note: By default, this property is cleared for new and existing business objectfields. You must manually update the property after platform upgrade.

Note fields

Any note field can be marked as localizable. Note field values are stored in thedatabase in binary format to retain the HTML format.

Text fields

Not all text fields can be marked as localizable from the Data Modeler. A locatortext field, for example, cannot be marked. This is primarily because locator textfield values are referenced from other fields of a record. To prevent redundantlanguage values, platform enforces these fields to be non-localizable fields. TheLocalizable property of a locator field should be based from the referenced orsource fields. For example, if a locator text field references a regular text field inanother business object, the localizable flag should be set on that regular text fieldin the other business object and not on the locator text field itself. If a text fieldcannot be localized, the Localizable property is set as read-only.

Locator fields

All locator fields cannot be marked as localizable from the Data Modeler as theycontain values from another record. The localizable property value of a locatorfield is managed by its referenced field. The language values stored in thereferenced business object field are used and mapped to the locator field languagestorage. If you want to localize the locator field, you must set the localizableproperty on the referenced business object field.

If you do not select the Locator field property, the Localizable property is enabled.If you select the Locator field property, the Localizable property is cleared anddisabled.


Attention: When you clear the Localizable property of a business object fieldafter it has been localized with existing language values, the data is automaticallycleared after you publish the business object. Data loss might occur.

Business Object PublishWhen you mark one of the fields in a business object as localizable, a languagestorage is created to hold the language values of that business object.

If more fields are marked localizable afterwards, the same language storage of thatbusiness object is updated to accommodate the additional localizable fields.Whether the system is a single-language or a multi-language environment, thelanguage tables are created and the as-delivered data.zip file includes them,although they are empty.

Internal ValueSome applications depend on the value stored in the main storage, such as a literalstring used in a workflow condition, a static filter in a system report, or a formula.Therefore, if you change the base language of the environment to a language otherthan US English, you must keep the value of the main storage as the internal valueof the localizable field and refer to it when processing the localizable field value inapplication logic.

This internal value cannot be changed by a regular user interaction with the recordform, unless the base language of the data in the system remains US English.When the base language of the system is US English, US English users can modifythe internal values.

Any localizable fields have internal values stored in the main storage. The firstvalue that is set to the localizable field is the internal value. If you are buildingyour application and you use literal strings in a particular language, you mustcreate the records initially in that language so that the first value is persisted to theinternal storage as well. For example, if you create your own application in Frenchand you use a specific French string in your workflow logic as a condition againsta localizable field, the records containing this localizable field must be created firstin French so that the French value is stored as the internal value of this localizablefield.

There are several entry points in the platform where the internal value of alocalizable field is stored and kept in the main storage. One is during the objectmigration import where values in the object migration package are treated asinternal values that were pulled from the main storage. Regardless of whatlanguage is exported in the object migration package, the values are retrieved fromthe main storage.

Another entry point where the internal value is set is during the initial creation ofa record. The first non-null value to be set to the field is the internal valueregardless of what language the user is using. Succeeding modifications do notupdate the internal values.

Modification of Internal ValuesAdmin users have the option to update the internal value of a localizable fieldthrough the object migration export package. The value of the records in the objectmigration package is set to the records as the internal value to the target system.This essentially overwrites the internal values of these records in the target system

Chapter 4. Application Data 15

with the ones in the package if these records exist. Otherwise, platform sets theinternal values for newly exported records.

If the base language remains US English, any US English user can directly modifythe internal value through the form. DataConnect can modify the internal valuewhen DC JOB is run as US English user.

Object MigrationThe Localizable property of a business object field is supported in object migration.

Attention: You might lose data if you import an object migration package thatwas created before IBM TRIRIGA Application Platform 3.3 into an environmentthat has been upgraded to IBM TRIRIGA Application Platform 3.3 or later and IBMTRIRIGA 10.3 or later. In this scenario, data loss occurs because language tables aredeleted.

When an object migration package created before IBM TRIRIGA ApplicationPlatform 3.3 is imported into an environment that has been upgraded to IBMTRIRIGA Application Platform 3.3 or later and IBM TRIRIGA 10.3 or later, thelanguage table is deleted. This is because the localizable property does not exist inan object migration package created prior to IBM TRIRIGA Application Platform3.3. As a result, the localizable property value that is already in the target system isreset. By design, the business object publish deletes the column for a field that isno longer marked as localizable. Since an old object migration package does nothave this property, all the columns will be dropped, which eventually will drop thewhole language table.

Application Data ImportLanguage packs for labels are delivered separately from language packs for data.You import label language packs with the Label Manager and data language packswith the Language Manager.

Language PacksThe directory structure of the language packs separates the label packs from thedata packs.

The following sample shows the structure:tririga_332_language_packs.zip

- LanguagePacks- data

- ru.zip (Russian)- fr.zip (French)- ...

- label- ru.zip (Russian)- fr.zip (French)- ...

- tooltips- en_tooltips.zip (English)

With this separation, the label language packs are imported in the Label Managerof the IBM TRIRIGA application, and the data language packs are imported in theLanguage Manager of the Administrator Console.

Note: You must unpack the main language pack (for example:tririga_332_language_packs.zip) before selecting the individual language pack to


import (for example: ru.zip).Attention: Make sure that you import the correct type of language pack in thespecific interface. For example, if you are in the Label Manager, you must import alabel pack. If you are in the Language Manager, you must import a data pack.

Language ManagerYou use the Language Manager in the Administrator Console to import datalanguage packs. You can import data language packs during the swap of the baselanguage or during the import of secondary languages.

To import application data, click the Browse button in the Language Manager,select the compressed file that contains the shipping data pack, select the targetlanguage of the import pack, and click the Import button.

All language values imported from the data language pack are stored into thelanguage table with the corresponding language id of the language code specifiedin the pack. If the record ID of a translation data does not match the record ID ofthe target environment, the translation data is skipped during the import process.

If you delete or add as-delivered records in the target environment, the translationsfrom the pack are not imported if the row number of these smart section recordshave changed or are not the same as the one in the pack.

Attention:

v Your system must be running IBM TRIRIGA Application Platform 3.3 or later;otherwise nothing is imported into the system.

v Refrain from importing a data pack while an existing import in the samelanguage is ongoing.

v If an insufficient column size error is encountered, fix the metadata of the field,republish the business object, and reimport the pack or the problematic XLIFFfile in a pack.

For more information, see the IBM TRIRIGA Application Platform 3 AdministratorConsole User Guide.

Record RuntimeIBM TRIRIGA renders and processes localizable field values in the record formdepending on your language.

Base Language Usersv Platform renders the base values that come from the language tables in the

user's language.v Updates made by a user are persisted in the language tables. This does not

overwrite the internal value from the main storage. If the internal value is nullor empty at this point, the value is stored in both main storage and languagetable.

v If the base language of the system remains the default US English, then all baselanguage users or US English users persist their values to the main storage andnot to the language table.

Secondary Language Usersv Platform renders the language values that come from the language tables.


v If no language values are available in the user's language, platform displays theinternal value (T_).

v If a user edits the field in a form with the internal value in it, this internal valueis persisted to the language table (L_).

v Updates made by the user are persisted in the language tables.v Validation of required fields is applied on secondary values to the internal value

validation.v Internal, base, and other language values are not affected by the secondary

language value changed.If the base language is not US English, US English users are consideredsecondary users and their values are persisted in the language tables.

Workflow RuntimeThe internal value of a localizable field from the main storage is always used inthe workflow engine.

Usage may include:v Literal string value used in the conditionv Dynamic value used in the conditionv Extended Formula

If the value of the localizable field is mapped to a record (regardless if new orexisting record), its internal value, base value, and language values are also copiedto the target record.

Query RuntimeSimilar to record runtime, the query engine queries and displays values oflocalizable fields depending on the user's language. Non-localizable fields arequeried from the main storage. Areas in the platform where a query can be runsuch as in the Report Manager, query section in the form, and portal sectionshould have the localizable data displayed in the language of the user.

Base Language UsersFor base language users, the query engine queries, filters, and sorts localizablevalues from the language tables in the base language. Updates made by the user tothe editable query follow the same rules applied to the runtime form changes.

Secondary Language UsersFor secondary language users, the query engine queries, filters, and sortslocalizable values from the language tables. An empty value is used if there is novalue for the secondary language. The internal value is used if there is no value forthe secondary language.v If for some reason there is a discrepancy in the internal, base, and language

values, for example if there is no base and secondary language value but aresome values in another secondary language, the query engine uses the emptyvalue. It does not attempt to use other language values nor its internal value.

v Updates made by the user to the editable query follow the same rules applied tothe runtime form changes.

v Validation of required fields is also applied on secondary values.


Runtime FiltersThe query engine always treats the runtime filter value input by the user to be inthe user’s preferred language. The query engine uses that value to filter fromlanguage tables for base or secondary language users.

Static or System FiltersStatic filters are treated differently from runtime filters. Query engine considers thelanguage of the user at runtime.

My ReportsSimilar to a runtime filter, a static filter input by the owner of the report is treatedin the language of the owner if the Localize flag is checked. By default, when astatic filter is added, the Localize flag value is checked. If the flag value is cleared,the static filter does not filter against the language table even if the filter is in MyReports.

Community ReportsDepending on how you copy or share community reports, you might be requiredto update the static filter string.

From My Reports

When a report is copied as a community report, the platform creates a separatetemplate of this report that includes the static filter string in the community pageand the report is marked as read-only. This copy becomes a community report.

The static filter is now in the language of the user who is running the report if theLocalize flag is checked. This may not yield the desired results if the language ofthe user who is running the report is not the same as the language of the ownerwho originally created the report. In this case, the community user needs to copythe community report to his My Reports page and update the static filter string tobe in his language.

From System Reports

When a system report is shared to the community, the platform does not create anew instance of the report. It is the same system report when run from thecommunity page. The query engine treats the static filter of a system reportdepending on the value of the Localize property in the System Filter section.

The System Filter section of a system report includes a Localize property flag foreach static filter. An application builder can use the internal value of the localizablefield or the runtime value. By default, this is cleared for new and existing systemreports. If an application builder checks this property, the query engine at runtimetreats the string literal in the language of the user who is running the report. If it iscleared, the query engine filters the results based on the internal values from thebase tables.

Language

The Language column in the community page shows the language in which thereport was created.


Chapter 5. Label Manager

You can use the Label Manager to view labels, text messages, and tooltips in yourown language.

For example, to show the labels and text messages on forms in Spanish, use theLabel Manager to enter the values in Spanish. You can provide information in anylanguage defined in the List Manager. The Label Manager does not contain acomplete list of all fields that are in the application. You must export/import thefiles to obtain the entire listing.

Note: If the language you need is not already in the list, you must add it.

The Label Manager has two different methods to provide the system withtranslated values.v Many translations are performed by third parties who do not have access to the

IBM TRIRIGA system. For this scenario, use the Label Manager to export a filethat contains the values that need to be translated. After the translator enters thetranslated data into the file, use the Label Manager to import the file and updatethe system.

v Use the Label Manager to directly enter translated values for specific fields, pagemessages, tab messages, and label and icon tooltips.

To access the Label Manager, navigate to Tools > Administration > LabelManager. The information in the left panel is organized by module.

Importing a File of Translated ValuesYou can import XLIFF and ZIP of XLIFF files. The exported XLIFF files can bezipped and imported as a queued batch process which runs in the background.Otherwise, each of the exported files must be imported one at a time; they cannotbe imported as a batch process.

About this task

Attention:

v If you are importing a translation data pack, do not import another pack in thesame language.

v If you customized labels in your application, importing a language packoverwrites your customized labels. Language packs are intended to work fullyon 10.3 or later applications and require the 3.3 or later platform. Customized orpre-10.3 applications may have some missing translations.

Procedure1. From the Label Manager, click Import. The import process uses batches. When

the import finds an issue with a row in a batch, it logs the issue in the feedbackwindow and removes the row from the batch so the batch can importsuccessfully.

2. From the list next to File Type select the format of the file you want to import.3. Select the target language. You can change the values in the Target Language

list in the List Manager.


4. Select whether you want to update the existing labels5. Specify the path of the file to be imported or click Browse to select the path.6. Click Import. If you select the Allow Special Character option, you can import

files that contain special characters, such as *, <, >, <=, >=. The languageelements are created or updated based on the information contained in the fileyou import.

7. When the import process finishes, if you imported a single XLIFF file, a list ofthe values found is displayed. Review any warnings or errors that occurred. Ifyou imported a ZIP file, no list is displayed, but you can view warnings anderrors in the labelManager.log file.Attention: If an insufficient column-size error occurs when you import yourfile, you must fix the metadata field, republish the business object and reimportthe pack.

What to do next

When the import process is complete, you can create a translated offline record.Ensure that you have selected the correct target language and click Run PostImport Process. You can view new records by selecting Home > Tools > SystemSetup > Integration > Offline Content.

Restriction: Macros are not supported and will not be translated.

Translate Specific ItemsIn the IBM TRIRIGA Application Platform, in the Label Manager, you can createlabels in secondary languages.

You can create labels in secondary languages for the following values:v Field: Field name and label by Module/Business Object.v Page Message: Alert message displayed in an information window.v Tab Message: Message associated with tab within the application.v Label Tooltip: Tooltip displayed when user hovers over a label.v Icon Tooltip: Tooltip displayed when user hovers over an icon.

Applying Translation to FieldsIf you are more comfortable reading another language, your company can translatespecific business objects and fields to that language. Translation can be applied tobusiness object fields using specific module or business object names or fields.

Procedure1. From the Label Manager, select Field from the Managed By menu.2. Select the secondary language from the list. You can change the values for

Secondary Language in the List Manager.3. If needed, select the Module/Business Object radio button in the Scope field.4. Select the object from the list in the left panel.5. In the right panel, specify the translated version of each Field Label in the

New Label field. The type of fields displayed for the Module/Business Objectscope are the action, tab, section, field, and state action labels.

6. Click Save.


Attention: Be sure to click Save before advancing to the next page. If you donot save a page, the translation values entered are removed.

7. Repeat for any additional pages of label values.

Tip: Use the arrows pointing left and right on the Action bar to scroll throughthe pages of label values.Attention: Be sure to click Save before advancing to the next page. If you donot save a page, the translation values entered are removed.

8. Set the Scope to Fields by selecting the radio button to the left of Fields.9. For each Field Label, enter the translated version in the New Label column.

10. Click Save.11. Repeat for any additional pages of label values.

Applying Translation to Page MessagesYou can use the Label Manager to apply language translation values to PageMessages.

Procedure1. From the Label Manager, select Page Message from the Managed By menu.2. Select the language.

Note: You can change the values in the Language menu in the List Manager.3. In the left panel, select the radio button related to option to which the page

messages belong.4. For each message name, enter the translated version in the Message Text field.5. Click Save.


Applying Translation to Tab MessagesYou can use the Label Manager to apply language translation values to TabMessages.

Procedure1. From the Label Manager, select Tab Message from the Managed By menu.2. Select the target language.

Note: You can change the values for Language in the List Manager.3. In the left panel, select the object you want.4. For each Tab Name, enter the translated version in the Tab Description field.5. Click Save.


Applying Translation to Label TooltipsUse the Label Manager to apply language translation values to label tooltips.

Procedure1. From the Label Manager, select Label Tooltip from the Managed By list.2. Select the target language.

Chapter 5. Label Manager 23

Note: You can change the values for Language in the List Manager.3. In the left panel, select the object you want.4. For each Field and Section, enter the translated version in the Tooltip Text

field.5. Click Save.


Applying Translation to Icon TooltipsUse the Label Manager to apply language translation values to icon tooltips.

Procedure1. From the Label Manager, select Icon Tooltip from the Managed By list.2. Select the radio button for Application Forms or Platform Forms.3. Select the language and click Change Language.

Note: You can change the values for Language in the List Manager.

Note: If you do not specify an icon tooltip for a language, the system displaysthe US English icon tooltip.

4. Enter the translated version of the tooltip in the Tooltip Message column.5. Click Save.


Adding New Application Fields, Messages, and Label TooltipsIn some modules and business objects, you can use the Label Manager to addfields, tab messages, and label tooltips to system objects, for example the WorkflowBuilder and the Association Manager, and provide translated values for the newfields in secondary languages. Page Messages and Icon Tooltips cannot be added.

Procedure1. From the Label Manager, select Field from the Managed By menu.2. Click Add.3. Select an Application from the list.4. Specify the field names.5. Click Save. The new fields display in the Label Manager for the Application.

You can then translate as needed.

Using Translated ValuesWhen a user signs in to the IBM TRIRIGA Application Platform, the platformattempts to present all text and messages in the preferred language. The defaultlanguage is US English. After text is available in a secondary language, a user canchange their language in their user profile.

Procedure1. Select Portfolio > People > My Profile.2. Select the My Profile tab.3. In the Preferences section, select the language from the Language list.


4. Optional: Select the time zone, date format, and area unit default.5. Optional: Enable bidirectional support and select the direction of

user-generated text. If you select Contextual, the direction of text is set asdescribed by Unicode. For more information, see http://www.unicode.org/reports/tr9/#The_Paragraph_Level. If you select Default, the direction of text isset to the default of the web browser.

6. Click Save & Close.

Note: To view the language update, you must clear the object metadata cacheby using the Administrator Console, log out, and log back in.

Chapter 5. Label Manager 25

http://www.unicode.org/reports/tr9/#The_Paragraph_Level

http://www.unicode.org/reports/tr9/#The_Paragraph_Level

Chapter 6. Export of Labels and Application Data

You can export labels and application data for translation by using the LanguageManager. You can then translate the exported data and reimport it. You can exportall labels and application data or just the labels and data that has changed sincethe last export. You can also export data for specific business objects.

Note:

v XLIFF, which stands for XML Localization Interchange File Format, is alocalization industry standard format for passing localizable data between tools.Various computer aided translation tools support the XLIFF format.

v Multi-Byte Characters and Excel: Languages with multi-byte characters, forexample Japanese and Russian, need special attention if Excel is used by thetranslator to provide the text in the target language. If the file is saved asUnicode text, you must open the file with a text editor and save it as UTF-8. Thestandard encoding format is UTF-8, which handles all character sets.

v Multi-Byte Characters and Oracle: If you are using a language with multi-bytecharacters, the database needs to be configured for UTF-8 at the instance level(not the schema). If you installed Oracle using the automated installation option,the resulting database instance cannot accept multi-byte characters. Read aboutglobalization on the Oracle website www.oracle.com.

v Multi-Byte Characters and Microsoft SQL Server: If you use Microsoft SQLServer, you can use multi-byte character sets. Read the material on Microsoftwebsite www.microsoft.com regarding globalization issues with SQL Server.

Application data

Exported application data is stored in the userfiles\Translations\tririgaData\export\updates directory in XLIFF format. The \updates folder is also backed upbefore each export. The XLIFF files are organized by business object. The files arenamed Module_triBusinessObject.xliff. For example, the calendar period businessobject, which is in the classifications module, is exported toClassification_triCalendarPeriod.xliff.

When you perform an export, the userfiles\Translations\tririgaData\export\reference folder is updated. The \reference folder is used as the base forreference files when a delta export is performed. If there are files in the referencedirectory, they are backed up to a folder called reference_date_time. You canmanually update the reference directory if required.

Each XLIFF file for data contains a maximum of 100 records. If more than 100records exist for a business object, extra files for that business object are createdand numbers are appended to the file name, for exampleClassification_triCalendarPeriod_01.xliff, Classification_triCalendarPeriod_02.xliff.

The userfiles\Translations\tririgaData\export\forDeletion folder contains filesfrom the reference directory that are going to be deleted.

Labels

Exported labels are stored in the userfiles\Translations\tririgaLabel\export\updates directory in XLIFF format. The \updates folder is also backed up before


http://www.oracle.com

http://www.microsoft.com

each export. The XLIFF files are organized by label type. The files are namedModule_LabelType.xliff. For example, the GUI labels, which are in the documentsmodule, are exported to Document_GUILabel.xliff. The exported file is also savedwith UTF-8 encoding in the userfiles\Translations folder of the installationsdirectory, for example, c:\Tririga\userfiles\Translations.

When you perform an export, the userfiles\Translations\tririgaLabel\export\reference folder is updated. If there are files in the reference directory, they arebacked up to a folder called reference_date_time. You can manually update thereference directory if required.

Each XLIFF file for labels contains a maximum of 1000 labels. If more than 1000labels exist for a label type, extra files for that label type are created and numbersare appended to the file name, for example Document_GUILabel_01.xliff,Document_GUILabel_02.xliff.

The userfiles\Translations\tririgaLabel\export\config directory contains theinclusion and exclusion files for the labels. The userfiles\Translations\tririgaLabel\export\forDeletion folder contains files from the reference directorythat are going to be deleted.

Exporting Labels and Application Data for TranslationYou can export labels and application data for translation by using the LanguageManager. The labels and data are exported as XLIFF files to theuserfiles\Translations directory. You can translate the data in the XLIFF files andthen reimport it.

Procedure1. Log in to the Administrator Console.2. In the left pane, select Language Manager and go to the Export Label and

Data For Translation section.3. Optional: In the Product version info field, enter information about the version

of IBM TRIRIGA. This information appears in the product-version attribute inthe exported XLIFF files.

4. If you want to import labels, ensure that the Label check box is selected,expand the options next to the Label Type list and select what you want toexport.

Option Description

Label Type Description

All All elements that are listed in the LabelType drop-down list.

GUI Labels Labels in the forms and static string fromData Modeler.

BO Labels BO field labels that do not havecorresponding labels in forms, BO sectionlabels, and BO name labels.

GUI Tooltips Tooltips for application icons and forms.

GUI Tab Information Instructions in form tabs.

System Messages User messages, notification records, labelsfrom offline Excel files, and static messages.


Option Description

System Labels Static labels in platform, scorecard managerlabels, UOM values, and metric thresholdlabels.

System Tooltips System tooltips, including icon tooltips.

System Tab Information Static tab instructions in the platform.

List Values Dynamic and static list values.

5. Select whether you want to perform a full export or a delta export. If you selecta delta export, you must also select the location of the reference file to whichyou want to compare the differences.

6. Select the target language for the export. Select Internal Value to export labelsand data from the main tables that are shipped with the product. You canchange the language values in the Target Language list in the List Manager.

7. Click Export.

Results

Application data is exported to the userfiles\Translations\tririgaData\export\updates directory. Labels are exported to the userfiles\Translations\tririgaLabel\export\updates directory.

Chapter 6. Export of Labels and Application Data 29

Chapter 7. Currency

The IBM TRIRIGA application enables users to establish a base currency (and date)and automatically calculate other currencies accordingly.

Currencies play a vital role in financial transactions. For example, for anorganization managing projects in multiple countries, effectively managingcurrency exchange rates can mean the difference between making or breaking thebudget. You set the base currency in the TRIRIGAWEB.properties file.

Currency types, such as US Dollars and Euro, are in the UOM Values in the Tools> UOM menu. There is limited support of currency types to your preferredlanguage. When you create a record, and your My Profile record specifies apreferred currency, that currency is the default currency for all number fields thathave Currency for their Unit of Measure (UOM). If you do not specify a currencyin your My Profile record, the default currency is the default specified in theindividual field.

Attention: Evaluate your use of currencies during implementation and add orremove currencies pertinent to what your company needs before adding datarecords. Failure to do so before creating records could cause conversion issues ordata loss on those records.

The Currency Conversion component is used with financial transactions. In IBMTRIRIGA, you can find the current exchange rates and exchange rate history in theexchange rate Conversion Groups. You can use the Conversion Groups to gatherexchange rates from multiple sources. If a currency conversion rate does not existfor the posting date and time of a financial transaction, the most recent currencyconversion rate is used. To access the Currency Conversion Rate page, go to Tools> Administration > Currency Conversions.

To see the list of available conversion rates, select the Search action on theCurrency Conversion Rates section bar. You can refine your search by adjusting thefields, and then clicking Search.

Creating currency ratesIf you do not find the conversion rate you want to use, you can create aconversion rate.

Procedure1. On the Currency Conversion page, click the Add action.2. Use the menus to select the value for the Conversion Group, From Currency,

and To Currency fields. If the value you want to use for the fields is notavailable, you can use the List Manager to add them.

3. Specify the Conversion Rate. This should be how many of the “to” currencyequals 1 of the “from” currency.

Note: You can only use up to six decimal points for the conversion rate.4. In the Start Date & Time and End Date & Time fields, specify the date after

and the date before which the rate is effective. You can also click the calendaricon and select the time and date.


5. Click OK.6. Select the check box related to the rate you want to modify, and click the Edit

action.7. If the Start Date & Time value is in the past, only the End Date & Time

value can be modified.8. If the Start Date & Time value is in the future, you can modify the

Conversion Rate and the End Date & Time.9. Save your changes.

10. Click OK.

Modifying currency ratesYou can modify an existing conversion rate.

Procedure1. Select the check box related to the rate you want to modify, and then click the

Edit action.v If the Start Date & Time value is in the past, only the End Date & Time

value can be modified.v If the Start Date & Time value is in the future, you can modify the

Conversion Rate and the End Date & Time.2. Save your changes.

Note:

v To delete a Currency Conversion Rate, select the check box related to the rateyou want to modify and click the Delete action.

v If the Start Date & Time value is in the past, the record cannot be deleted.The record is retained for historical purposes. If the Start Date & Time valueis in the future, when you click Delete, the rate is delete immediately

3. Click OK.


Chapter 8. Managing Units of Measure

Every numerical data element (field) must have an associated Unit of Measure(UOM). For example, the unit of measure type “Area” can have “square-meters” asone of its UOM values. The IBM TRIRIGA application has many standard UOMs,such as inch, gallon, pound, and volt. You can use IBM TRIRIGA to convertcompatible UOMs.

Note:

v You also can modify UOM at the display properties field level using the FormBuilder tool.

v When a numeric field defined in the Data Modeler points to a source field, thesystem reads UOM values directly from that source field. A copy of the UOMinformation is not stored with the numeric field. UOM values for base currencyfields are read directly from the TRIRIGAWEB.properties file. When creating anew numeric field, the UOM parameters must be set explicitly. Unless specified,a UOM is not set for a newly created numeric field.

v Evaluate your use of currencies during implementation and add or removecurrencies pertinent to your company needs before adding data records. Failureto do so before creating records could cause conversion issues or data loss onthose records.

Configuring UOM TypeYou can add, change, or delete Unit of Measure (UOM) types,

About this task

Follow the steps below to access and use the UOM Type functionality:

Procedure1. Select Tools > Administration > Unit of Measure (UOM).2. Select Type.3. To add a UOM Type, click the Add action.4. In the General section, specify the name of the new UOM in the UOM Type

field.5. To add a base UOM, click the search icon next to the Base UOM field, select a

value, and click OK.6. Click Create.7. Click Save & Close.8. To modify a UOM Type, click the link of the name of the UOM Type you

want to modify.Attention: Modifying a UOM Type affects existing data in your system.Evaluate your existing data before proceeding.

9. In the UOM_Type form, click Update.10. After you have made your changes, click Save & Close.11. To delete a UOM Type, select the check box related to the UOM Type you

want to delete and click the Delete action.


Attention:

v When you click Delete, the UOM Type is deleted immediately.v Deleting a UOM Type affects existing data in your system. Evaluate your

existing data before proceeding.

Configuring UOM ValuesYou can configure unit of measure (UOM) values such as the conversion factor,conversion offset, storage precision, and rounding rule.

Procedure1. Go to Tools > Administration > Unit of Measure (UOM).2. Click Values.3. To add a UOM Value, click the Add action.4. In the General section, specify a value for the UOM Type field. If you type a

few characters, you can use the autocomplete feature to select the value. Youcan also click the search icon to select a value from the list.

5. Specify the values for the fields in the UOM Details section.a. Enter the name of the UOM.b. Enter the UOM ABBREVIATION that will be used for this UOM value.c. Enter the Conversion Factor from the Base UOM.d. In Conversion Offset, enter any offset required to accurately convert the

UOM.e. Display Mask controls the formatting of the display of values.f. Storage Precision defines how many digits to the right of the decimal point

decimal are used when computing and storing numbers in this field. Themaximum is 12.

g. In Rounding Rule, specify how numbers entered in this field will berounded to the number of decimal places specified in Storage Precision.

h. Enter the UOM Decimal that should be used as a decimal separator for thecurrency.

i. Enter the Currency Symbol if appropriate.j. Enter the UOM Delimiter which should be used as a delimiter for the

currency6. Click Create.7. Click Save & Close.8. To modify a UOM Value, select the link of the name of the UOM Value you

want to modify.9. In the UOM_Values form, click Update.

10. After you have made your changes, click Save & Close.11. To delete a UOM Value, click the check box related to the UOM Value you

want to delete and click the Delete action.


Rounding Rules for UOM ValuesWhen you configure unit of measure (UOM) values, the rounding rule defines hownumbers are rounded to the number of decimal places specified in StoragePrecision.

Option Description

ROUND_CEILING The fractional digit moves toward positiveinfinity. For example, if Storage Precision is2, 1.234 is rounded to 1.24.

ROUND_DOWN The fractional digit moves toward zero. Theoperation effectively truncates the value atthe number of decimal places in StoragePrecision. For example, if Storage Precisionis 2, 1.2345 is rounded to 1.23.

ROUND_FLOOR The fractional digit moves toward negativeinfinity. For example, if Storage Precision is2, 1.234 is rounded to 1.23.

ROUND_HALF_DOWN The fractional digit uses the digit to theright to determine the direction of theround. If the digit to the right is 6 or greater,the fraction digit is rounded up. If the digitto the right is 5 or less, the fractional digit isrounded down. For example, if StoragePrecision is 2, 1.234 is rounded to 1.23, and1.236 is rounded to 1.24.

ROUND_HALF_EVEN The fractional digit is rounded up or downas needed to make it even. For example, ifStorage Precision is 2, 1.234 is rounded to1.23.

ROUND_HALF_UP The fractional digit uses the digit to theright to determine the direction of theround. If the digit to the right is 5 or greater,the fractional digit is rounded up. If thedigit to the right is 4 or less, the fractionaldigit is rounded down. For example, ifStorage Precision is 2, 1.234 is rounded to1.23, and 1.236 is rounded to 1.24.

ROUND_UP The fractional digit moves away from zero.For example, if Storage Precision is 2, 1.234is rounded to 1.24.

Chapter 8. Managing Units of Measure 35

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law: INTERNATIONALBUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFNON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULARPURPOSE. Some states do not allow disclaimer of express or implied warranties incertain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of thosewebsites. The materials at those websites are not part of the materials for this IBMproduct and use of those websites is at your own risk.


IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. The sampleprograms are provided "AS IS", without warranty of any kind. IBM shall not beliable for any damages arising out of your use of the sample programs.

Privacy Policy ConsiderationsIBM Software products, including software as service solutions, (“SoftwareOfferings”) may use cookies or other technologies to collect product usageinformation, to help improve the end user experience, to tailor interactions withthe end user or for other purposes. In many cases no personally identifiableinformation is collected by the Software Offerings. Some of our Software Offeringscan help enable you to collect personally identifiable information. If this Software


Offering uses cookies to collect personally identifiable information, specificinformation about this offering’s use of cookies is set forth below.

This Software Offering does not use cookies or other technologies to collectpersonally identifiable information.

If the configurations deployed for this Software Offering provide you as customerthe ability to collect personally identifiable information from end users via cookiesand other technologies, you should seek your own legal advice about any lawsapplicable to such data collection, including any requirements for notice andconsent.

For more information about the use of various technologies, including cookies, forthese purposes, see IBM’s Privacy Policy at http://www.ibm.com/privacy andIBM's Online Privacy Statement at http://www.ibm.com/privacy/details in thesection entitled “Cookies, Web Beacons and Other Technologies” and the "IBMSoftware Products and Software-as-a-Service Privacy Statement" athttp://www.ibm.com/software/info/product-privacy/.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at “Copyright andtrademark information” at www.ibm.com/legal/copytrade.shtml.

Java™ and all Java-based trademarks and logos are trademarks or registeredtrademarks of Oracle and/or its affiliates.

Linux is a trademark of Linus Torvalds in the United States, other countries, orboth.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Other product and service names might be trademarks of IBM or other companies.

Notices 39

http://www.ibm.com/privacy

http://www.ibm.com/privacy/details

http://www.ibm.com/software/info/product-privacy/

http://www.ibm.com/legal/copytrade.shtml

http://www.ibm.com/legal/copytrade.shtml

��

Printed in USA

localization user guide - ibm - united states filechapter 3. localizing lists .....7 types of lists...

Documents