IBM BJ0NJML Integration Guide - Page 216

Processing Rule Definitions SKIP action The skip action bypasses a message that meets the specified criteria. The inbound message is not processed and the outbound message is not sent to an external system. Skip processing does not generate an error, but the system log file is updated with the rule that caused the skip action. For inbound messages, the message is cleared from the inbound queue, as it would like a successfully processed message. For outbound messages that are skipped, nothing is written to the queue. A skip action has some predefined rules. These rules look up integration control values to ensure that outbound messages have a valid status before being sent to the external system. STOP action The stop action halts the processing of a message that meets the specified criteria. The outbound message is rolled back and an error message is displayed. For inbound transactions, the message remains in the inbound JMS queue. If the error was the result of a synchronous invocation of the enterprise service, the calling program is notified about the error. Predefined rules are not provided with a stop action. This option is a utility for users to customize the behavior of a service or channel. Whenever possible, use the skip action rather than the stop action for inbound enterprise services. The latter stop action results in a processing error, and the message remains in the inbound queue or the initiator receives an error response. These results do not occur when you use the skip action. For example, if a processing rule with a stop action applies to a publish channel that is generated by the Data Export feature, the stop action is treated as a skip action. If the stop action evaluates as true, the message is skipped. SKIPCHILDREN action The skip children action is available only for outbound messages in a publish channel. Apply the processing rule on the record or object whose child level records are skipped. If the person structure has the person object and child objects of phone and email, use the skip children action on a person to strip the phone and e-mail data from the message. Use the skip children action when a status change occurs and the external system does not need the accompanying phone and e-mail information. SKIPRECORD action The skip record action is only available for outbound messages in a publish channel. The skip record action deletes a record or object that contains your applied rule. Apply the processing rule on the record or object, and all of their child records and objects, that you want the system to skip. For example, if the person structure has a person object and a child object of phone, you can use the skip record action to strip a specific phone record from the message. Use the skip record action when the external system needs a work phone number but not the home phone number. The skip record rule needs a condition to identify a home phone record to force the system to skip that record. Field Transformation Actions Apply the field transformation rule to the record or object that contains the field to be transformed. A field transformation rule can be applied to a single field or multiple fields in the selected record. 202 Integration Guide