IBM BJ0NJML Integration Guide - Page 217

SET action REPLACE action COMBINE action SPLIT action Processing Rule Definitions The following field transformation actions manipulate data fields within a message. The set action writes a value to a specified data field. When you define the rule, you specify the data to be set and the source of the new value. Indicate whether the rule always writes the new value to the target field or writes the new value only when the field is null (the default action). You can use this action to initialize the value in a data field. If the rule always writes the new value to the target field, any existing value in the field is overwritten. The source can be one of the following values: T A value integration control T A hard-coded value T A system control (in the MAXVARS database table) T Another field in the specified record or object T A field in a related object The replace action replaces a value in a data field with another value. When you define the rule, you specify the data field that you want to update. The control that you use must be a cross-reference control. You specify the name of a crossreference control that contains the original and replacement values for the data field. Use this action when an external system and the system have different identifiers for the same entity. For example, the plant identifier of an external system might translate to your site identifier. For example, to replace the SITEID value in a publish channel with an external PLANTID value, and to replace the external PLANTID value in an enterprise service with a SITEID value, you can use a single cross-reference control. The combine action concatenates values from multiple source fields into a single target field. When you define the rule, you identify the target field and the source fields. You also identify the sequence in which the source data is to be written to the target field. The source data can be a data field or an integration control that contains a data value. You can also specify an integration control that contains the delimiter to separate the segments in the target field. Use this action in an enterprise service processing rule when a mismatch exists between the system definition and the external system definition of an entity, for example, a two-part external system key that maps to a single part key in the system. An enterprise service processing rule can combine a vendor ID and a vendor location field from an external system into the COMPANY field. A publish channel processing rule with the split action can then separate the combined field into separate values when data is sent to the external system. The source and target fields must be in the same object. This action always overwrites the existing value in the target field. Ensure that the source and target fields are alphanumeric fields, or processing errors may occur. The split action is the reverse of the combine action. The split action separates the value in one field into multiple fields. When you define the rule, you identify one Integration Framework Customization with Processing Rules 203