One issue that can arise with the use of this pattern occurs where it cannot be ensured that the incoming place to the merge (p1) is safe. BPMN and XPDL allow it to be represented in both ways. Staffware, SAP Workflow and UML 2.0 ADs provide specific join constructs for this purpose where as it is represented implicitly in WebSphere MQ, FLOWer, COSA and BPEL. Similar to patterns WCP2-WCP4, this pattern can either be represented explicitly or implicitly. place p1 fin Figure 5) is safe and can never contain more than one token. There is one context condition associated with the pattern: the place at which the merge occurs (i.e. There is no consideration of synchronization. Immediately after either task A or B is completed, task C will be enabled. Overviewįigure 5 illustrates the behaviour of this pattern. Instead, these branches can be joined with a simple merge construct and the common set of tasks need only to be depicted once in the process model. As such, this presents the opportunity to simplify a process model by removing the need to explicitly replicate a sequence of tasks that is common to two or more branches. The Simple Merge pattern provides a means of merging two or more distinct branches without synchronizing them. ExamplesĪt the conclusion of either the bobcat-excavation or the D9-excavation tasks, an estimate of the amount of earth moved is made for billing purposes.Īfter the case-payment or provide-credit tasks, initiate the product-receipt task.
XOR-join, exclusive OR-join, asynchronous join, merge. The convergence of two or more branches into a single subsequent branch such that each enablement of an incoming branch results in the thread of control being passed to the subsequent branch. FLASH animation of Simple Merge pattern Description
0 kommentar(er)
