IBM TRIRIGA Application Platform Version 3.5.3

Runtime usage of globalized data in workflow mappings

If a data language pack is imported, globalized data is supported in workflow mappings.

The following mappings are supported:

Localizable text field to localizable text field
Localizable text field to localizable locator field
Localizable text field to a localizable note field
Record to localizable locator field
Literal string to localizable text field
Localizable classification field to a localizable text field
System form label translation to a localizable text field

If the value of the localizable field is mapped to a record, its internal value, base value, and language values are also copied to the target record.

At run time, workflows map all available globalized data from the source field to the target field. If globalized data is available in the source record but not the target record, a new globalized record is created in the target record. If no equivalent localizable value exists in the source record, an empty value is set in the target record. An example is displayed in the following graphic.

Figure 1. Mapping in workflow run time

Mapping in workflow run time. The source record is L_VIBOLOCALIZATIONB, containing data for the TRINAMETX and VIFLDANOTHERLOCALIZABLETX fields in Italian and French. The target record is L_VIBOLOCALIZATION, and before mapping it contains data for the TRINAMETX and VIFLDLOCALIZABLETX fields in Italian and Russian. The VIFLDANOTHERLOCALIZABLETX field is mapped to the VIFLDLOCALIZABLETX field. The target record, L_VIBOLOCALIZATION, clears the Russian value for VIFLDLOCALIZABLETX and adds another row to contain the French value of VIFLDLOCALIZABLETX.

At run time, workflows can use literal string values, dynamic values, and extended formulas. The internal value of a localizable field from the main tables is always used in the workflow engine.

Feedback