Differences

This shows you the differences between two versions of the page.

--- en:rule:control_branch [2024-01-08 19:39] – [✘ How NOT to] Anatoly Belaychuk
+++ en:rule:control_branch [2024-11-02 13:36] (current) – [Edit diagram] Anatoly Belaychuk
@@ Line 1: / Line 1: @@
-====== Use a subprocess and a control branch as an alternative to the attached event ======
+====== A subprocess and a control branch may be used as an alternative to the attached event ======
-{{tag>subprocess gateway event "attached event"}}
+{{tag>subprocess event attached_event terminate_event}}
 Use a subprocess containing the control branch to implement versatile event processing logic.
 ===== ✔ How to =====
@@ Line 12: / Line 11: @@
   - Start the subprocess with the parallel gateway followed by two branches, "working" and "control".
   - Put the "Obtain payment" at the working branch.
-  - Put the timer to the control branch.
+  - Put the timer at the control branch.
-  - End both the working and control branch with terminate events.
+  - End both the working and control branch with the terminate event.
 <bpmnio type="bpmn">
@@ Line 166: / Line 165: @@
 ===== ✘ How NOT to =====
-Interrupting attached timer won't do the job if need to discuss the issue with client while still trying to obtain the payment:
+Interrupting attached timer won't let discussing the issue with client while still trying to obtain the payment:
 <bpmnio type="bpmn">
@@ Line 237: / Line 236: @@
 </bpmnio>
-Non-interrupting looks better but it won't be possible to reset the timer to the new due date:
+Non-interrupting looks better but it won't let resetting the timer to the new due date:
 <bpmnio type="bpmn">
@@ Line 252: / Line 251: @@
     <sequenceFlow id="Flow_1mqvexf" sourceRef="Event_0jid81n" targetRef="Activity_1mnvjuz" />
     <sequenceFlow id="Flow_1fkn8r9" sourceRef="Event_0r0tew3" targetRef="Activity_1skmlnn" />
-    <endEvent id="Event_1k1tn88" name="Paid">
-      <incoming>Flow_0b5yo8b</incoming>
-    </endEvent>
     <sequenceFlow id="Flow_0b5yo8b" sourceRef="Activity_1mnvjuz" targetRef="Event_1k1tn88" />
     <boundaryEvent id="Event_0r0tew3" name="Payment due date" cancelActivity="false" attachedToRef="Activity_1mnvjuz">
@@ Line 279: / Line 275: @@
     </endEvent>
     <sequenceFlow id="Flow_16a0qq5" name="yes" sourceRef="Gateway_1sygjo0" targetRef="Event_1ltc3ao" />
+    <endEvent id="Event_1k1tn88" name="Paid">
+      <incoming>Flow_0b5yo8b</incoming>
+      <terminateEventDefinition id="TerminateEventDefinition_1srmvcb" />
+    </endEvent>
   </process>
   <bpmndi:BPMNDiagram id="BpmnDiagram_1">
@@ Line 288: / Line 288: @@
       <bpmndi:BPMNShape id="Event_0jid81n_di" bpmnElement="Event_0jid81n">
         <omgdc:Bounds x="112" y="-138" width="36" height="36" />
-      </bpmndi:BPMNShape>
-      <bpmndi:BPMNShape id="Event_0ok4f4i_di" bpmnElement="Event_1k1tn88">
-        <omgdc:Bounds x="352" y="-138" width="36" height="36" />
-        <bpmndi:BPMNLabel>
-          <omgdc:Bounds x="359" y="-95" width="23" height="14" />
-        </bpmndi:BPMNLabel>
       </bpmndi:BPMNShape>
       <bpmndi:BPMNShape id="Activity_1skmlnn_di" bpmnElement="Activity_1skmlnn">
@@ Line 315: / Line 309: @@
         <bpmndi:BPMNLabel>
           <omgdc:Bounds x="349" y="155" width="43" height="14" />
+        </bpmndi:BPMNLabel>
+      </bpmndi:BPMNShape>
+      <bpmndi:BPMNShape id="Event_05jo8b9_di" bpmnElement="Event_1k1tn88">
+        <omgdc:Bounds x="352" y="-138" width="36" height="36" />
+        <bpmndi:BPMNLabel>
+          <omgdc:Bounds x="359" y="-95" width="23" height="14" />
         </bpmndi:BPMNLabel>
       </bpmndi:BPMNShape>
@@ Line 359: / Line 359: @@
 ===== Notes =====
-  - [[en:rule:event_gateway_warning | Exclusive event-based gateway ]] won't do the job.
+  - Although it's usually better to use [[en:rule:collapsed_subprocess|collapsed representation of a subprocess]] to isolate its internals, it may make sence to depict the subprocess expanded in this technique to make the logic clear.
-  - Although it's usually better to use [[en:rule:collapsed_subprocess | collapsed representation of a process ]] to isolate its internals, it may make sence to depict the subprocess expanded in this technique to make the logic clear.
+  - As an exception to the [[en:rule:explicit_parallel_split|general rule]], one may initiate work and control flows directly from the start event:
-  - As an exception to the [[en:rule:one_outgoing_control_flow | general rule ]], one may initiate work and control flows directly from the start event:
 <bpmnio type="bpmn">
@@ Line 500: / Line 499: @@
 </definitions>
 </bpmnio>
-===== Exceptions =====
+===== See also =====
-Attached events are simpler and hence should be preferred in more straightforward scenarios.
+  * [[en:rule:event_gateway_warning]]
 ===== Autor(s) =====
  --- //[[user:bell|Anatoly Belaychuk]] 2023-09-10 11:21//