fix bpmn comparisons examples (#302) (#303)

Signed-off-by: Tihomir Surdilovic <[email protected]>

Author: Tihomir Surdilovic

comparisons/comparison-bpmn.md

@@ -30,6 +30,7 @@ For this reason, the event, function, retry, and data mapping defined in the ass
 - [Error Handling with Retries](#Error-Handling-With-Retries)
 - [Process Execution Timeout](#Process-Execution-Timeout)
 - [Multiple Instance Subprocess](#Multiple-Instance-Subprocess)
+- [Loop Subprocess](#Loop-Subprocess)
 - [Approve Report (User Task)](#Approve-Report)
 - [Event Based Decision](#Event-Based-Decision)
 
@@ -305,26 +306,63 @@ functions:
 </td>
 <td valign="top">
 
+```yaml
+id: foreachWorkflow
+name: ForEach State Workflow
+version: '1.0'
+start: ForEachItem
+states:
+- name: ForEachItem
+  type: foreach
+  inputCollection: "${ .inputsArray }"
+  iterationParam: "${ .inputItem }"
+  outputCollection: "${ .outputsArray }"
+  workflowId: doSomethingAndWaitForMessage
+  end: true
+```
+
+</td>
+</tr>
+</table>
+
+* Note: We did not include the `dosomethingandwaitformessage` workflow in this example, which would just include
+a starting "operation" state transitioning to an "event" state which waits for the needed event.
+
+### Loop Subprocess
+
+<table>
+<tr>
+    <th>BPMN2 Diagram</th>
+    <th>Serverless Workflow</th>
+</tr>
+<tr>
+<td valign="top">
+<p align="center">
+<img src="../media/comparisons/bpmn/loop-subprocess.png" width="500px" alt="BPMN2 Loop Subprocess Workflow"/>
+</p>
+</td>
+<td valign="top">
+
 ```yaml
 id: subflowloop
-name: SubFlow Repeat workflow
+name: SubFlow Loop Workflow
 version: '1.0'
-start: SubflowRepeat
+start: SubflowLoop
 states:
-- name: SubflowRepeat
+- name: SubflowLoop
   type: subflow
-  workflowId: dosomethingandwaitformessage
+  workflowId: checkAndReplyToEmail
   repeat:
-    max: 10
+    max: 100
   end: true
 ```
 
 </td>
 </tr>
 </table>
 
-* Note: We did not include the `dosomethingandwaitformessage` workflow in this example, which would just include
-a starting "operation" state transitioning to an "event" state that waits for the needed event.
+* Note: We did not include the `checkAndReplyToEmail` workflow in this example, which would include the 
+control-flow logic to check email and make a decision to reply to it or wait an hour.
 
 ### Approve Report