From 73e32035c8bb280d5e566b64bc05d8d578bda550 Mon Sep 17 00:00:00 2001 From: Nick O'Leary Date: Thu, 23 Jul 2015 21:32:32 +0100 Subject: [PATCH] Updated Design: subflows vNext (markdown) --- Design:-subflows-vNext.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/Design:-subflows-vNext.md b/Design:-subflows-vNext.md index 97200b7..aca0ae6 100644 --- a/Design:-subflows-vNext.md +++ b/Design:-subflows-vNext.md @@ -54,8 +54,11 @@ It is fixed to 1-input and 1-output - this cannot be changed. ![](images/subflows/loop_subflow_toolbar.png) -The loop condition is configurable in the toolbar (quick ui mock-up - need to test if there’s enough room to do it in the toolbar directly, or via some other means) +The loop condition is configurable in the toolbar (quick ui mock-up - need to test if there’s enough room to do it in the toolbar directly, or via some other means). +When a message arrives on the input, the loop condition is evaluated to see if the loop should continue. If so, it passes through the flow defined in the loop. When the message reaches the output of the subflow, the loop condition is evaluated, and so on. + +(Need to determine the proper conditions - foreach/while/until/do-loop - and message semantics) ## Lifecycle model aka - how one thing can become another, and back again.