webMethods 10.2 | Dynamic Apps Platform | webMethods BPM Process Development Help | Process Engine Processing | About Joins
 
About Joins
 
About Dead Path Notification and Join Steps
How Incomplete Transitions Affect Join Steps and Gateways
About Join Failures in Join Steps and Gateway Steps
Migrating Process Models with Join Steps to Version 9.7 and Later
About OR Join Behavior (Synchronized vs. Unsynchronized)
About Complex Join Expressions
In a business process model, you can merge, or join, two or more inputs in a single step, and select from available Boolean logic definitions to define the behavior of the join step. In BPMN models, a join is typically accomplished with a gateway step. Software AG Designer supports both step joins and gateway steps. For more information about gateway steps, see About Gateways and About Gateway Types.
The available join types are:
*OR. The step processes the incoming data when any incoming transition is satisfied (that is, provides data). The OR join is available as:
*A standard OR join, also known as a synchronized OR. This is the default behavior for Process Engine version 8.0 and later.
*An unsynchronized OR, provided for compatibility with Process Engine version 7.x.
For more information, see About OR Join Behavior (Synchronized vs. Unsynchronized).
*AND. The step processes the incoming data only when all incoming transitions are satisfied (that is, provide data).
*COMPLEX. The step processes the incoming data according to the custom join logic you create with a join condition editor.
You can optionally specify a join timeout value. For more information about join timeout behavior, see About Process and Step Timeouts.
Copyright © 2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.