IBM TRIRIGA Application Platform 3 Localization User Guide

IBM TRIRIGA Application Platform Version 3.3

Localization User Guide

Note Before using this information and the product it supports, read the information in “Notices” on page 34.

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

US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents

ABOUT THIS GUIDE ...... 1

Conventions ...... 1

Intended Audience ...... 1

Prerequisites ...... 1

Support ...... 1

1. MULTICULTURAL SUPPORT ...... 2

Scenarios ...... 2 US English ...... 2 One Language (Not US English) ...... 3 Official Language with Multilingual Workforce ...... 3 Multilingual with No Official Language ...... 4

2. LISTS ...... 6

Specify List Items in Alternate Languages ...... 7

Custom Date Formats ...... 8

3. APPLICATION INSTANCE DATA ...... 12

Base Language Setup ...... 12

Data Modeler ...... 13 Business Objects ...... 13 Business Object Publish ...... 14 Internal Value ...... 14 Modifying Internal Values...... 14 Object Migration ...... 14

Instance Data Import ...... 15 Language Packs ...... 15 Label Manager ...... 15 Language Manager ...... 16

Record Runtime ...... 16

Workflow Runtime ...... 17

Query Runtime ...... 17 Runtime Filter ...... 18 Static or System Filter ...... 18 My Reports ...... 18 Community Reports ...... 18 4. LABEL MANAGER ...... 19

Accessing the Label Manager ...... 19

File Export/Import ...... 19 To Export a File to be Translated ...... 20 To Import a File of Translated Values ...... 21

Translate Specific Items ...... 22 Applying Translation to Fields ...... 22 Applying Translation to Page Messages ...... 23 Applying Translation to Tab Messages ...... 24 Applying Translation to Label Tooltips ...... 24 Applying Translation to Icon Tooltips ...... 25 Adding New Application Fields, Messages, and Label Tooltips ...... 26

Using Translated Values ...... 26

5. MANAGING CURRENCY ...... 27

6. MANAGING UNITS OF MEASURE ...... 29

UOM Type...... 29

UOM Values ...... 30

INDEX ...... 33

NOTICES ...... 34 About This Guide

This guide describes how to use the tools in the IBM® TRIRIGA® Application Platform to customize the IBM TRIRIGA applications for your local environment. Topics include labels, units of measure, dates, and currency.

Conventions

This document uses the following conventions to ensure that it is as easy to read and understand as possible:

Note – A note provides important information that you should know in addition to the  standard details. Often, notes are used to make you aware of the results of actions.

 Tip – A tip adds insightful information that can help you use the system better.

Attention – An attention notice indicates the possibility of damage to a program, device,  system, or data.

Intended Audience

This guide is for Application Administrators and other users responsible for setting up and maintaining the IBM TRIRIGA applications.

Prerequisites

This guide assumes that the reader has a basic understanding of Web-based applications and has administrator access to the IBM TRIRIGA software.

Support

IBM Software Support provides assistance with product defects, answering FAQs, and performing rediscovery. View the IBM Software Support site at www.ibm.com/support.

1. Multicultural Support

Multicultural support, also known as globalization, is the process of organizing an application so that it can be configured to work in different countries and in different languages.

You can use IBM TRIRIGA Application Platform to translate messages and any other text content that appears into the language you want.

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

Multicultural support involves the configuration and translation efforts needed to meet the requirements of the application. The globalization requirements for applications vary considerably; however, they usually support one of the following scenarios:

Scenario Description

US English An application is developed to be used by people whose language preference is US English to process data that uses only US English.

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

Official Language with Workers who prefer different languages work with data that is all in the Multilingual Workforce same language.

Multilingual with No Workers who prefer different languages work with data that is in multiple Official Language languages.

Scenarios

US English

All business objects that come with the IBM TRIRIGA Application Platform support US English. If an application is intended to function entirely in US English, it normally requires no globalization effort. All business objects and tools shipped with the IBM TRIRIGA Application Platform are written in US English and use units of measure and currency appropriate for the United States.

If an application was developed in a language other than US English, multicultural support can be required to use the application on the IBM TRIRIGA Application Platform 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 supplied with an application are not right for business practices. Instead of directly modifying any forms, you can define a language supply translations for specific labels and descriptions to match business practices. If you customize an application this way, you can avoid incompatibilities between modified business objects and business objects.

One Language (Not US English)

In some cases, if your company uses a language other than English as the preferred language, you expect to see the formatting and units for numeric quantities that are different from what is customary in the United States. Except for the formatting of numbers, this scenario is well supported. Before using this scenario, perform the following tasks:

. Add the language to the Language list if needed. . Use the Label Manager to provide translations of all labels, tab information, system messages, tooltips, and classifications in the Classification hierarchy. . Use the Label Manager and the List Manager to provide translations for all lists that should be translated. . Access different pages under the Tools menu to create translations of Approvals, CTQ Dynamic Lists, News, Notification Content, and User Message records. . If none of the date or time formats shipped with the IBM TRIRIGA Application Platform are appropriate for your business environment, you can add the formats in the List Manager. . Add the currency type to the List Manager if needed. . Translate Units of Measure and UOM Values in the Administration menu if needed. . Translate all reports and help text. . Establish language, currency, time zone, date format, date time format, area unit, and length unit values in the My Profile page.

Attention – Evaluate your use of currencies during implementation and add or remove 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. For instance, IBM TRIRIGA Application Platform does not explicitly allow the formatting of numbers. Also, if you change the name of a classification, instead of using the Label Manager to translate it, the workflows can break if they rely on the name of the classification.

Official Language with Multilingual Workforce

In some cases, a company can conduct its internal business in one official language, which can be different from the language of preference of each user. The application is much easier to use if information such as field labels and help text is presented in the language of preference of each user.

Except for the formatting of numbers, such scenario is well supported. The following activities are useful:

. Identify the secondary languages to be supported. . Add the official language and the supported secondary languages to the Language list if not already there. . Use the Label Manager to provide translations of all labels, tab information, system messages, tooltips, and classifications in the Classification hierarchy. . Use the Label Manager and the List Manager to provide translations for all lists that should be translated.

. Access different pages under the Tools menu to create translations of Approvals, CTQ Dynamic Lists, News, Notification Content, and User Message records into the official Language and other supported languages that are not US English. . If none of the date or time formats shipped with the IBM TRIRIGA Application Platform are appropriate for the intended business environment, add appropriate formats in the List Manager. . Add the currency types to the List Manager if needed. . Translate Units of Measure and UOM Values in the Administration menu if needed. . Translate all reports into the official language. . Translate all help text into the official language and the other supported languages that are not US English. . Establish language, currency, time zone, date format, date time format, area unit, and length unit values in users My Profile page.

Attention – Evaluate your use of currencies during implementation and add or remove currencies pertinent to your company needs before adding data records. Failure to do so  before creating records could cause conversion issues or data loss on those records.

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

Multilingual with No Official Language

In an environment where there is a multi-lingual workforce but no official language, users conduct business in multiple languages. To support this scenario, you must:

. Add languages that will be supported to the Language list if needed. . Use the Label Manager to provide translations of all labels, tab information, system messages, tooltips, and classifications in the Classification hierarchy that should be translated. . Use the Label Manager and the List Manager to provide translations for all lists that should be translated. . Access different pages under the Tools menu to create translations of Approvals, CTQ Dynamic Lists, News, Notification Content, and User Message records into all languages that will be supported. . If none of the date or time formats shipped with the IBM TRIRIGA Application Platform are appropriate for the intended business environment, add appropriate formats in the List Manager. . Add currency types to the List Manager if needed. . Translate Units of Measure and UOM Values in the Administration menu if needed. . If you need to have reports in multiple languages, you must create multiple versions of the reports. When you create these reports you can choose to filter the data by the triLanguageLI field on the record so your reports do not mix data in multiple languages. . Translate help text into all supported languages. . Establish language, currency, time zone, date format, date time format, area unit, and length unit values in the My Profile page.

Some potential problems for supporting this scenario follow.

. 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 fields appear in, since they appear in the language in which they are entered. The automatic translation of list values may be good or bad. . Any dates or times entered as text are not formatted according to the preference in the My Profile page and are displayed exactly as entered. . You cannot explicitly format numbers with the IBM TRIRIGA Application Platform. Some workarounds may be available for some combinations of formatting and computing environments.

2. Lists

IBM TRIRIGA provides lists of predefined values for many fields in the user interface. These lists contain valid data and you can select the required value from a list. You can improve data integrity by restricting users to select approved values from 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-down lists of static values, dynamic lists derived from values in the database, and dependent lists.

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

List Type Description

Static List A Static list contains values that are fixed and do not change often, for example, states, colors, countries.

Dependent List Dependent lists consist of two static lists, one parent list and one or more child lists. For example, a business object contains two list fields named Country and State. If the State list is defined as a dependent list, the list of values available for the State field is dependent on the Country selected.

Dynamic List Dynamic lists are directly tied to a business object. For example, a new model number in a business object in the Asset menu. As new models are received, they are entered into the Asset business object. These model numbers are immediately available in a Model list that is used with a Parts Request form. You do not need to manually specify the new model numbers in the Parts Request form because the Model list was dynamically created from the Asset business object.

Tip – You will find more information about the List Manager in the IBM TRIRIGA 10  Application Administration User Guide.

Attention – Evaluate your use of currencies during implementation and add or remove currencies according to what your company needs before adding data records. Failure to  do so before creating records could cause conversion issues or data loss on those records.

Specify List Items in Alternate Languages

You can localize choices that appear in List fields so users can see list choices in their preferred language. To do this, use the Label List action in the List Manager.

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

To Specify List Items in Alternate Languages

1. 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 drop-down box 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 right panel.

To filter lists by a module, select the check box to the left of the module name in the Filter By section. The lists in the Manage By section refresh to show only lists available for that module.

To further refine the lists shown in the Manage By section, select more than one module in the Filter By section.

4. Click Label List.

5. The system opens the List Labels form containing Values carried from the list selected in the Manage By section.

6. Select the appropriate language from the Select Language drop-down list.

7. Enter the Labels in the selected language.

8. Click Save.

Your application may use some lists that should not be translated. Examples of lists that should not be translated are:

. A list of postal abbreviations for the states of a country or provinces should not be translated. These normally need to be in their original form so that the post office from that country can read the abbreviations. . Lists of numeric values are not specific to any language, so they do not need to be translated.

Custom Date Formats

You can define different date formats or date time formats from those shipped with the IBM TRIRIGA Application Platform. In the List Manager, you can use the DateFormat 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 Time fields. Not all of the formats in the DateTimeFormat list can be translated. The standard 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

Format Example

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 in which these names and abbreviations appear. They appear in the same language, independent of the language specified by the user in their My Profile. The language in which the names and abbreviations appear is controlled by a layer of software on top of which the IBM TRIRIGA Application Platform runs. The specifics vary with the computing environment in which the platform runs.

You can use the List Manager to add or modify formats in the DateFormat or DateTimeFormat lists. The IBM TRIRIGA Application Platform treats the text in DateFormat and DateTimeFormat as a sequence of characters that specify how to format dates and times. For formatting dates and times, the characters in these formats are considered to be one of two kinds:

. Copied characters, which are copied from the format when creating a formatted date or time. For example: / - : are copied characters. . Interpreted characters, which are interpreted with whatever meaning is assigned to them. The interpretation of the interpreted character is copied into the formatted 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 other characters are copied characters. Although all letters from A to Z and from a to z are interpreted characters, an interpretation has not been assigned to all letters. The following paragraphs describe the interpretation of letters in formats.

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

Letter Sequence Description Examples

d One or two digit day in month 1 - 31

dd Two digit day in month 01 - 31

DDD Three digit day in year 001 - 366

Letter Sequence Description Examples

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 month abbreviation 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 of times. The number of repetitions of a letter affects the way it formats a part of a time and that upper and lowercase letters have different interpretations. If you include letters to format time in a format for date-only values, it will look like the time part of the value is midnight.

Letter Sequence Description Examples

a AM or PM indication AM or PM

h One or two digit hour in am/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 in hour 0 - 59

mm Two digit minute in hour 00 - 59

s One or two digit second in minute 0 - 59

S One, two, or three digit millisecond 0 - 999

ss Two digit second in minute 00 - 59

SSS Three digit millisecond 000 - 999

z or zzz Three letter time zone abbreviation EST, CST, and so on.

Z Time zone with respect to GMT -0500, -0600, and so on.

Define Date or Date-and-Time Format

If the format you want to use does not exist, you can use the List Manager to define a different date format or date-and-time format.

To Define Date or Date-and-Time Format

1. Select Tools > Administration > Lists.

2. In the Manage By section, expand the drop-down list and select Name.

3. Select DateFormat or DateTimeFormat.

4. In the right panel, specify the new format in the Value field.

5. Click Save Entries.

3. Application Instance Data

You can mark or flag a business object field as localizable, but you cannot export the data for translation. 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 so through the normal medium like forms.

. Base Language is the language that the platform uses when processing localizable data. Base values refer to the localizable data stored in the language storage and assumed to be written in the base language. The base language determines what values are displayed in forms if there is no value in the language preference of the user’s My Profile record. For example, if an environment is set to have Brazilian Portuguese as the base language, and a French user is interacting with a geography record where the description field does not have a French translation, the application tries to display the Brazilian Portuguese value of the field.

If the base language remains US English, which is the default base language for new and upgraded installs, data from US English users is stored in the main storage (T_ tables) and not in the language storage. On the other hand, if the base language has been swapped to non-US English, then data from US English users is stored as localized values in the language tables and is treated the same as any secondary language in the system.

. Secondary Languages are the languages other than the base language of the system. Secondary or Language values refer to the different translations of the localizable data written in the supported secondary languages and stored in the language tables.

If the base language has been swapped to non-US English, then data from US English users is stored as localized values in the language tables and is treated the same as any other secondary language in the system.

. 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 for workflow conditions, formulas, system report filters, and so on.

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

Base Language Setup

You must set up a base language for the system so that the system knows how to manage the application records and system data, especially if there are multi-language users in the system. You can use the Language Manager in the Administrator Console to change the base language of the system. In the Language Manager, you select the language data pack you want as the new base language. By default, the base language is US English upon new install or upgrade.

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

When an admin swaps the base language, the base language value is inserted into the language table with a base language value, a language id similar to the base language specified. The platform retrieves and stores updates of the record to this language 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 base language is  swapped while the import of each xliff file inside the zip is on-going, even if one of the xliff files inside the pack has encountered import errors.

Data Modeler

Business Objects

In the Data Modeler, you can select the Localizable check box in a business object field to distinguish between localizable and non-localizable data. If you are an application developer, you select this property if a field can have a secondary language other than US English.

Note – By default, this property is cleared for new and existing business object fields. 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 the database in binary format to retain the HTML format.

Text Fields

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

Non-localizable Text Fields Locator Field

All locator fields cannot be marked as localizable from the Data Modeler as they contain values from another record. The localizable property value of a locator field is managed by its referenced field. The language values stored in the referenced business object field are used and mapped to the locator field language storage. If you want to localize the locator field, you must set the localizable property 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 and disabled.

Attention – When you clear the Localizable property of a business object field after it has been localized with existing language values, the data is automatically cleared after you  publish the business object. Data loss might occur.

Business Object Publish

When you mark one of the fields in a business object as localizable, a language storage is created to hold the language values of that business object. If more fields are marked localizable afterwards, the same language storage of that business object is updated to accommodate the additional localizable fields. Whether the system is a single-language or a multi-language environment, the language tables are created and the as-delivered data.zip file includes them, although they are empty.

Internal Value

Some applications depend on the value stored in the main storage, such as a literal string 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 other than US English, you must keep the value of the main storage as the internal value of the localizable field and refer to it when processing the localizable field value in application logic. This internal value cannot be changed by a regular user interaction with the record form (see Modifying Internal Values section for options), 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 modify the internal values.

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

There are several entry points in the platform where the internal value of a localizable field is stored and kept in the main storage. One is during the object migration import where values in the object migration package are treated as internal values that were pulled from the main storage. Regardless of what language is exported in the object migration package, the values are retrieved from the main storage.

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

Modifying Internal Values

Admin users have the option to update the internal value of a localizable field through the object migration export package. The value of the records in the object migration 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 with the ones in the package if these records exist. Otherwise, platform sets the internal values for newly exported records.

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

Object Migration

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

Attention – You might lose data if you import an object migration package that was created before IBM TRIRIGA Application Platform 3.3 into an environment that has been upgraded to IBM TRIRIGA Application Platform 3.3 or later and IBM TRIRIGA 10.3 or later. In this scenario, data loss occurs because language tables are deleted.

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

Instance Data Import

Language Packs

Starting with the IBM TRIRIGA Application Platform 3.3 release, the directory structure of the language packs separates the label packs from the data packs. The following sample shows the structure:

userfiles_dev_70249_20121115.zip - LanguagePacks - data - ru.zip (Russian) - fr.zip (French) - ... - label - ru.zip (Russian) - fr.zip (French) - ... With this separation, the label language packs are imported in the Label Manager of the IBM TRIRIGA application, and the data language packs are imported in the Language Manager of the Administrator Console.

Note – You must unpack the main language pack (for example:  userfiles_dev_70249_20121115.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 the specific interface. For example, if you are in the Label Manager, you must import a label pack. If  you are in the Language Manager, you must import a data pack.

Label Manager

You can use the Label Manager to view labels and text messages in your own language. For more information, see the “Label Manager” chapter.

Language Manager

You use the Language Manager in the Administrator Console to import data language packs. You can import data language packs during the swap of the base language or during the import of secondary languages. For more information, see the IBM TRIRIGA Application Platform 3 Administrator Console User Guide.

To import instance data, click the Browse button in the Administrator Console, select the compressed file that contains the shipping data pack, select the target language of the import pack, and click the Import button.

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

If you delete or add shipping smart records in the target environment, the translations from the pack are not imported if the row number of these smart section records have changed or are not the same as the one in the pack.

Attention – Your system must be running IBM TRIRIGA Application Platform 3.3 or later;  otherwise nothing is imported to the system.

Attention – Refrain from importing a data pack while an existing import in the same  language is on-going.

Attention – 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 xliff in a  pack.

Record Runtime

IBM TRIRIGA renders and processes localizable field values in the record form depending on your language.

Base Language Users . Platform renders the base values that come from the language tables in the user's language. . 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 null or empty at this point, the value is stored in both main storage and language table. . If the base language of the system remains the default US English, then all base language users or US English users persist their values to the main storage and not to the language table.

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

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

. If a user touches the field in a form with the internal value in it, this internal value is persisted to the language table (L_). . Updates made by the user are persisted in the language tables. . Validation of required fields is applied on secondary values to the internal value validation. . Internal, base, and other language values are not affected by the secondary language value changed.

Note – If the base language is not US English, US English users are considered secondary  users and their values are persisted in the language tables.

Workflow Runtime

The internal value of a localizable field from the main storage is always used in the workflow engine. Usage may include:

. Literal string value used in the condition . Dynamic value used in the condition . Extended Formula

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

Query Runtime

Similar to record runtime, query engine queries and displays values of localizable fields depending on the user's language. Non-localizable fields are queried from the main storage. Areas in the platform where a query can be run like in report manager, query section in the form, and portal section should have the localizable data displayed in the language of the user.

Base Language Users . Query engine queries, filters (see Runtime Filter and Static or System Filter for considerations), and sorts localizable values from the language tables in the base language. . Updates made by the user to the editable query follows the same rules applied to the runtime form changes.

Secondary Language Users . Query engine queries, filters, and sorts localizable values from the language tables. . Empty value is used if there is no value for the secondary language. . 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 are some values in another secondary language, the query engine uses the empty value. It does not attempt to use other language values nor its internal value. . Updates made by the user to the editable query follow the same rules applied to the runtime form changes. . Validation of required fields is also applied on secondary values.

Runtime Filter

Query engine always treats the runtime filter value input by the user to be in the user’s preferred language. The query engine uses that value to filter from language tables for base or secondary language users.

Static or System Filter

Static filters are treated differently from runtime filters. Query engine considers the language of the user at runtime.

My Reports

Similar to a runtime filter, a static filter input by the owner of the report is treated in the language of the owner if the Localize flag is checked. By default, when a static filter is added, the Localize flag value is checked. If the flag value is unchecked, the static filter does not filter against the language table even if the filter is in My Reports.

Community Reports From My Reports

When a report is copied as a community report, platform creates a separate template of this report that includes the static filter string in the community page and 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 the Localize flag is true. This may not yield the desired results if the language of the user who is running the report is not the same as the language of the owner who originally created the report. In this case, the community user needs to copy the community report to his My Reports page and update the static filter string to be in his language.

From System Reports

When a system report is shared to the community, platform does not create a new instance of the report. It is the same system report when run from the community page. Query engine treats the static filter of a system report depending 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 for each static filter. An application builder can use the internal value of the localizable field or the runtime value. By default, this is unchecked for new and existing system reports. If an application builder checks this property, query engine at runtime treats the string literal in the language of the user who is running the report. If it is unchecked, the query engine filters the results based on the internal values from the base tables.

Language

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

4. Label Manager

You can use the Label Manager to view labels and text messages in your own language. For example, to show the labels and text messages on forms in Spanish, use the Label Manager to enter the values in Spanish. You can provide information in any language defined in the List Manager. The Label Manager does not contain a complete list of all fields that are in the application. You must export/import the files to obtain the entire listing.

Note – If the language you need is not already in the list, you must add it. Refer to the  “Lists” chapter for information about how to add items to lists. The Label Manager has two different methods to provide the system with translated values.

. Many translations are performed by third parties who do not have access to the TRIRIGA system. For this scenario, use the Label Manager to export a file that contains the values that need to be translated. After the translator enters the translated data into the file, use the Label Manager to import the file and update the system. . Use the Label Manager to directly enter translated values for specific fields, page messages, tab messages, and label and icon tooltips.

Accessing the Label Manager

To access the Label Manager:

To Access the Label Manager

1. Navigate to Tools > Administration > Label Manager.

The system opens the Language Editor Manager. The information in the left panel is organized by module.

Follow the section below corresponding to the method you have chosen to tell the system what the translated values are: File Export/Import or Translate Specific Items.

File Export/Import

The Label Manager Export/Import facility can export an xliff or xml file of the values to be translated away from the IBM TRIRIGA system. When the translation is complete, import the file and the language translations are available for use.

Note – Multi-Byte Characters and Excel: Languages with multi-byte characters, for example Japanese and Russian, need special attention if Excel is used by the translator to provide the text in the target language. If the file is saved as Unicode text, you must open  the file with a text editor and save it as UTF-8. The standard encoding format is UTF-8, which handles all character sets.

Note – Multi-Byte Characters and Oracle: If you are using a language with multi-byte characters, 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 about globalization on Oracle website www.oracle.com.

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

If you work with multiple environments and you export/import a file, the translatable labels in the forms, if they have the same name but different IDs, are updated across all environments that use the same application/platform version. This does not include customizations.

To Export a File to be Translated

Follow the steps below to export a file to be translated:

To Export a File to be Translated

1. From the Label Manager, click Export.

2. Expand the next to Export Type drop-down list and select what you want to export.

If you select All, the exported file will contain all of the elements listed in the Export Type drop-down. To export UOM Values, select System Labels from the Export Type list.

3. Select the format of the file to be exported from the drop-down box next to File Type.

4. Select the target language.

Note – You can change the values in the Target Language drop-down list  in the List Manager.

Note – If there are elements that have values in the target language  already, the translated values are populated in the exported file.

5. Click Export.

Note – The format for the name of the exported file is  __.

Note – The exported file also is saved with UTF-8 encoding in the  userfiles\Translations folder of the installation directory. For example, C:\Tririga\userfiles\Translations.

The format of the file is based on which File Type was selected; however, the structure of the data elements (fields) in the file is standard. The columns to the left of the BASE column describe each data element (field) to the system. The information in the BASE column is the text in the Base Language to be translated. The same text in the Target Language must be entered into the TRANSLATION column.  Attention – Do not change anything in the file except the TRANSLATION column.

Once the translation is complete, the file is ready to be imported into the TRIRIGA system.

To Import a File of Translated Values

You can import XML, XLIFF, and ZIP of XLIFF files. The exported xliff files can be zipped and imported as a queued batch process which runs in the background. Otherwise, each of the exported files must be imported 1 at a time; they cannot be imported as a batch process.

Attention – If you are importing a translation data pack, do not import another pack in the  same language.

Attention – If you customize labels in your application, importing a language pack will override your customized labels. Language packs are intended to work fully on 10.3  applications and require the 3.3 platform. Customized or pre-10.3 applications may have some missing translations.

Follow the steps below to import a file:

To Import a File of Translated Values

1. From the Label Manager, click Import.

Note – The import process uses batches. When the import finds an issue with a row in a batch, it logs the issue in the feedback window and  removes the row from the batch so the batch will import successfully.

2. From the drop-down box next to File Type select the format of the file you want to import.

3. Select the target language.

Note – You can change the values in the Target Language drop-down list  in the List Manager.

4. Specify the path of the file to be imported or click Browse to select the path.

5. Click Import. The language elements are created or updated based on the information contained in the file you import.

Note – If you select the Allow Special Character option, you can import  files that contain special character, such as *, <, >, <=, >=, and so on.

To Import a File of Translated Values

6. When the import process finishes, a list of the values found is displayed. Review any warnings or errors that occurred.

Attention – If an insufficient column-size error occurs when you import you file, you must fix the metadata filed, republish the business object and re-  import the pack.

Translate Specific Items

In the IBM TRIRIGA Application Platform, in the Label Manager, you can create labels in secondary languages for the following values:

. Field: Field name and label by Module/Business Object. . Page Message: Alert message displayed in an information window. . Tab Message: Message associated with tab within the application. . Label Tooltip: Tooltip displayed when user hovers over a label. . Icon Tooltip: Tooltip displayed when user hovers over an icon.

Applying Translation to Fields

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

To Apply Translation to Fields

1. From the Label Manager, select Field from the Managed By drop-down list.

2. Select the secondary language from the drop-down list.

Note – 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.

Note – The type of fields displayed for the Module/Business Object scope  are the action, tab, section, field, and state action labels.

To Apply Translation to Fields

6. Click Save.

Attention – Be sure to click Save before advancing to the next page. If  you do not 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  through the pages of label values.

Attention – Be sure to click Save before advancing to the next page. If  you do not 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.

Attention – Be sure to click Save before advancing to the next page. If  you do not save a page, the translation values entered are removed.

11. Repeat for any additional pages of label values.

Tip – Use the arrows pointing left and right on the Action bar to scroll  through the pages of label values.

Attention – Be sure to click Save before advancing to the next page. If  you do not save a page, the translation values entered are removed.

Applying Translation to Page Messages

To apply language translation values to Page Messages:

To Apply Translation to Page Messages

1. From the Label Manager, select Page Message from the Managed By drop-down list.

To Apply Translation to Page Messages

2. Select the language.

Note – You can change the values in the Language drop-down list 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.

Attention – Be sure to click Save before advancing to the next page. If  you do not save a page, the translation values entered are removed.

Applying Translation to Tab Messages

To apply language translation values to Tab Messages:

To Apply Translation to Tab Messages

1. From the Label Manager, select Tab Message from Managed By drop-down list.

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.

Attention – Be sure to click Save before advancing to the next page. If  you do not save a page, the translation values entered are removed.

Applying Translation to Label Tooltips

To apply language translation values to Label Tooltips:

To Apply Translation to Label Tooltips

1. From the Label Manager, select Label Tooltip from the Managed By drop-down list.

2. Select the target language.  Note – You can change the Language values in the List Manager.

3. In the left panel, select the object you want.

4. For each Field and Section, enter the text in the language in the Tooltip Text field.

5. Click Save.

Attention – Be sure to click Save before advancing to the next page. If  you do not save a page, the translation values entered are removed.

Applying Translation to Icon Tooltips

To apply language translation values to Icon Tooltips:

To Apply Translation to Icon Tooltips

1. From the Label Manager, select Icon Tooltip from the Managed By drop-down 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 Language values in the List Manager.

Note – If you do not specify an icon tooltip for a language, the system  displays the US English icon tooltip.

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

5. Click Save.

Attention – Be sure to click Save before advancing to the next page. If  you do not save a page, the translation values entered are removed.

Adding New Application Fields, Messages, and Label Tooltips

In some modules and business objects, you can use the Label Manager to add fields, tab messages, and label tooltips to system objects, for example the Workflow Builder and the Association Manager, and provide translated values for the new fields in secondary languages. Page Messages and Icon Tooltips cannot be added.

To Add New Application Fields, Messages, and Label Tooltips

1. From the Label Manager, select Field from the Managed By drop-down list.

2. Click Add.

3. Select an Application from the drop-down 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 Values

From the time a user signs in to the IBM TRIRIGA Application Platform, the platform attempts to present all text and messages in the preferred language. The default language is US English. Once text is available in a secondary language, a user can change their language in their User Profile.

Follow the instructions below to specify a new language preference:

Using Translated Values

1. Select Portfolio > People > My Profile.

2. Select the My Profile tab.

3. In the Preferences section, select the language from the Language drop-down list.

Tip – You also can specify your choice for the other fields in the  Preferences section.

4. Click Save & Close.

 Note – You must log out and log back in for the language to be reflected.

5. Managing Currency

Currencies play a vital role in financial transactions. For example, for an organization managing projects in multiple countries, effectively managing currency exchange rates can mean the difference between making or breaking the budget. The IBM TRIRIGA application enables users to establish a base currency (and date) and automatically calculate other currencies accordingly. 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. See the “Lists” chapter for information about adding, modifying, or deleting from the Currency list. There is limited support of currency types to your preferred language. When you create a record, and your My Profile record specifies a preferred currency, that currency is the default currency for all number fields that have Currency for their Unit of Measure (UOM). If you do not specify a currency in your My Profile record, the default currency is the default specified in the individual field.

Attention – Evaluate your use of currencies during implementation and add or remove currencies pertinent to what your company needs before adding data records. Failure to  do so before creating records could cause conversion issues or data loss on those records.

The Conversion Currency component is used with financial transactions. In IBM TRIRIGA, you can find the current exchange rates and exchange rate history in the exchange rate Conversion Groups. You can use the Conversion Groups to gather exchange rates from multiple sources. If a currency conversion rate does not exist for the posting date and time of a financial transaction, the most recent currency conversion 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 the Currency Conversion Rates section bar. You can refine your search by adjusting the fields, and then clicking Search.

If you do not find the conversion rate you want to use, you can create a conversion rate.

To Create Currency Conversion Rates

1. On the Currency Conversion page, click the Add action.

2. Use the drop-down 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 not available, you can use the List Manager to add them.

3. Specify the Conversion Rate. This should be how many of the “to” currency equals 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 calendar icon and select the time and date.

5. Click Ok.

You can also modify an existing Currency Conversion Rate.

To Modify Currency Conversion Rates

1. Select the check box related to the rate you want to modify, and click the Edit action.

If the Start Date & Time value is in the past, only the End Date & Time value can be modified.

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 – To delete a Currency Conversion Rate, select the check box related the rate you want to modify and click the Delete action.

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 value is in the future, when you click Delete, the rate is deleted immediately.

3. Click OK.

6. 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” as one 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 convert compatible UOMs.

Note – You also can modify UOM at the display properties field level using the Form  Builder tool.

Note – When a numeric field defined in the Data Modeler points to a source field, the system reads UOM values directly from that source field. A copy of the UOM information is not stored with the numeric field. UOM values for base currency fields are read directly  from the TRIRIGAWEB.properties file. When creating a new numeric field, the UOM parameters must be set explicitly. Unless specified, a UOM is not set for a newly created numeric field.

Note – Evaluate your use of currencies during implementation and add or remove currencies pertinent to your company needs before adding data records. Failure to do so  before creating records could cause conversion issues or data loss on those records.

UOM Type

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

To Access and Manage UOM Types

1. 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.

To Access and Manage UOM Types

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 – When you click Delete, the UOM Type is deleted immediately.

Attention – Deleting a UOM Type affects existing data in your system.  Evaluate your existing data before proceeding.

UOM Values

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

To Access and Manage UOM Values

1. 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 auto-complete feature to select the value. You can also click the search icon to select a value from the list.

5. Specify the values for the fields in the UOM Details section.

. Enter the name of the UOM. . Enter the UOM ABBREVIATION that will be used for this UOM value. . Enter the Conversion Factor from the Base UOM. . In Conversion Offset, enter any offset required to accurately convert the UOM. . Display Mask controls the formatting of the display of values. . Storage Precision defines how many digits to the right of the decimal point decimal are used when computing and storing numbers in this field. The maximum is 12.

To Access and Manage UOM Values

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

Option Description

ROUND_CEILING The fractional digit moves toward positive infinity. For example, if Storage Precision is 2, 1.234 is rounded to 1.24.

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

ROUND_FLOOR The fractional digit moves toward negative infinity. For example, if Storage Precision is 2, 1.234 is rounded to 1.23.

ROUND_HALF_DOWN The fractional digit uses the digit to the right to determine the direction of the round.

If the digit to the right is 6 or greater, the fraction digit is rounded up. If the digit to the right is 5 or less, the fractional digit is rounded down.

For example, if Storage Precision is 2, 1.234 is rounded to 1.23, and 1.236 is rounded to 1.24.

ROUND_HALF_EVEN The fractional digit is rounded up or down as needed to make it even. For example, if Storage Precision is 2, 1.234 is rounded to 1.23.

ROUND_HALF_UP The fractional digit uses the digit to the right to determine the direction of the round.

If the digit to the right is 5 or greater, the fractional digit is rounded up. If the digit to the right is 4 or less, the fractional digit is rounded down.

For example, if Storage Precision is 2, 1.234 is rounded to 1.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.234 is rounded to 1.24.

. Enter the UOM Decimal which should be used as a decimal separator for the currency. . Enter the Currency Symbol if appropriate. . Enter the UOM Delimiter which should be used as a delimiter for the currency

6. Click Create.

To Access and Manage UOM Values

7. Click Save & Close.

8. To modify a UOM Value, select the link of the name of the UOM Value you want to modify.

Attention – Modifying a UOM Value affects existing data in your system.  Evaluate your existing data before proceeding.

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.

Attention – When you click Delete, the UOM Value is deleted immediately.  You are not offered a delete confirmation window.

Attention – Deleting a UOM Value affects existing data in your system.  Evaluate your existing data before proceeding.

INDEX

Add Icon Tooltip ...... 26 Message Text ...... 24 Add Page Message ...... 26 Microsoft SQL Server ...... 20 Alternate Language ...... 7 Multi-Byte Characters ...... 19 Application ...... 26 Multilingual with No Official Language ...... 4 Application Forms ...... 25 My Profile ...... 27 Base Column ...... 21 My Profile Tab ...... 26 Base Currency ...... 29 New Label ...... 22, 23 Base Language ...... 12, 21 Official Language with Multilingual Workforce 3, 4 Base UOM ...... 29 Oracle ...... 20 Base Value ...... 12 Page Message ...... 22, 23 Change Language ...... 25 Platform Forms ...... 25 Conversion Factor ...... 30 Rounding Rule ...... 31 Conversion Group ...... 27 Save Entries ...... 11 Conversion Offset ...... 30 Search ...... 27 Conversion Rate ...... 27 Secondary Language ...... 12, 22 Currency Conversion ...... 27 Section ...... 25 Currency Symbol ...... 31 Select Language ...... 7 DateFormat ...... 8, 11 Static List ...... 6 DateTimeFormat ...... 8, 11 Storage Precision ...... 30 Define Date or Date and Time Format ...... 11 Tab Description ...... 24 Dependent List ...... 6 Tab Message ...... 22, 24 Display Mask ...... 30 Tab Name ...... 24 Dynamic List ...... 6 Target Language ...... 20, 21 Exchange Rate ...... 27 Third-Party Translation ...... 19 Export ...... 20 To Currency ...... 27 Export Type ...... 20 Tooltip Message...... 25 Field ...... 22, 25 Tooltip Text ...... 25 Field Label ...... 22, 23 Translate ...... 19 Fields ...... 23 Translate Fields...... 22 File Type ...... 20, 21 Translate Icon Tooltips ...... 25 Filter By Section ...... 7 Translate Label Tooltips ...... 24 From Currency ...... 27 Translate Page Messages ...... 23 Generate Export File ...... 20 Translate Tab Messages ...... 24 Icon Tooltip ...... 22, 25 Translation Column ...... 21 Import ...... 21 Translations Folder ...... 20 Internal Value ...... 12, 14 TRIRIGAWEB.properties ...... 29 Label ...... 7 U.S. English ...... 2 Label List ...... 7 UOM ...... 29 Label Manager ...... 19 UOM ABBREVIATION ...... 30 Label Tooltip ...... 22, 25 UOM Details Section ...... 30 Language ...... 24, 25, 26 UOM Type ...... 29, 30 Language Editor Manager ...... 19 UOM Values ...... 30 Language Manager ...... 12 Use Letters Language Translation File Export ...... 20 Format Dates ...... 9 Language Translation File Import...... 21 Format Times ...... 10 List Labels ...... 7 User Profile ...... 26 List Manager ...... 6 UTF-8 ...... 19 Manage By Section ...... 7, 11 Value ...... 11

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 in other countries. Consult your local IBM representative for information about the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

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

IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A.

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

Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan, Ltd. 19-21, Nihonbashi-Hakozakicho, Chuo-ku Tokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain 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 be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

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

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

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

IBM Corporation 2Z4A/101 11400 Burnet Road Austin, 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 material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

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

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

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

Trademarks

IBM, the IBM logo, ibm.com, and TRIRIGA are trademarks or registered trademarks of International 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 and trademark information” at www.ibm.com/legal/copytrade.shtml.

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