Conditional Expressions
Integration Server provides syntax and operators that you can use to create expressions for use with the BRANCH step, pipeline mapping, and in trigger conditions.
In a BRANCH step, you can use an expression to determine the child step that
webMethods Integration Server executes. At run time, the first child step whose conditional expression evaluates to “true” is the one that will be executed. For more information about the BRANCH step, see
BRANCH.
In pipeline mapping, you can place a condition on the link between variables. At run time,
webMethods Integration Server only executes the link if the assigned condition evaluates to “true.” For more information about applying conditions to links between variables, see
Linking Variables Conditionally.
For
webMethods Messaging Triggers, you can further specify the documents that a trigger receives and processes by creating filters for the publishable document types. A filter specifies criteria for the contents of a document.
Note: The conditional expressions syntax is for filters created for documents received from Broker or locally and for the local filter for a document received from Universal Messaging. For information about the syntax for creating a provider filter on Universal Messaging, see the Universal Messaging documentation.
For JMS triggers, you can create local filters to further limit the messages a JMS trigger processes. A local filter specifies criteria for the contents of the message body.
Integration Server applies a local filter to the message after the JMS trigger receives the message from the JMS provider. If the message meets the filter criteria,
Integration Server executes the trigger service specified in the routing rule.