Split Workflow Message Type Details
You can use this workflow to split messages based on a certain criteria and to create multiple messages with different message types. The split messages undergo further workflow processing as defined in the workflow configuration.
The following table describes fields requiring explanation:
Field |
Description |
|---|---|
|
Identifies the type of message to be split, such as |
|
Identifies a type of this workflow as |
|
A path to the program that handles the message. |
|
A set of one or more comma separated name-value pairs, which are passed as parameters to the workflow handler. |
|
The number of times a message is retried when the system fails. |
|
A path to the standard program used to enhance the incoming message before message transformation. |
|
A set of one or more comma separated name-value pairs, which are passed as parameters to the pre-XSLT transaction. |
|
A path to the program used to enhance the incoming message before message transformation. If entered, this program takes precedence over the standard pre-XSLT transaction. |
|
A set of one or more comma separated name-value pairs, which are passed as parameters to the partner pre-XSLT transaction. |
|
A path to the program used to enhance the incoming message before message transformation. If entered, this program takes precedence over the partner and standard pre-XSLT transactions. |
|
A set of one or more comma separated name-value pairs, which are passed as parameters to the partner pre-XSLT transaction. |
|
A path to the XSLT file that splits the incoming message based on a certain criteria. |
|
A path to the XSLT file that splits the incoming message based on a certain criteria. This file takes precedence over the standard split XSLT address. |
|
A path to the XSLT file that splits the incoming message based on a certain criteria. This file takes precedence over the standard and partner split XSLT addresses. |
|
A path to the standard program used to perform actions after the split of messages is successfully executed. |
|
A set of one or more comma separated name-value pairs, which are passed as parameters to the pass handler transaction. |
|
A path to the program used to perform actions after the split of messages is successfully executed. If entered, this program takes precedence over the standard pass handler transaction. |
|
A set of one or more comma separated name-value pairs, which are passed as parameters to the partner pass handler transaction. |
|
A path to the program used to perform actions after the split of messages is successfully executed. If entered, this program takes precedence over the standard and partner pass handler transactions. |
|
A set of one or more comma separated name-value pairs, which are passed as parameters to the customer pass handler transaction |
|
A path to the standard program used to perform actions after the split of messages fails. |
|
A set of one or more comma separated name-value pairs, which are passed as parameters to the fail handler transaction. |
|
A path to the program used to perform actions after the split of messages fails. If entered, this program takes precedence over the standard fail handler transaction. |
|
A set of one or more comma separated name-value pairs, which are passed as parameters to the partner fail handler transaction. |
|
A path to the program used to perform actions after the split of messages fails. If entered, this program takes precedence over the standard and partner fail handler transactions. |
|
A set of one or more comma separated name-value pairs, which are passed as parameters to the customer fail handler transaction. |