Plainly decides which items to show using three directives: ---depends_on, ---outcome and filters.
An item shows in a task when either:
An item's outcome is:
So every connection needs both halves:
--#item: ---id:step_a ---action:done ---title:Step A ---outcome:step_b --#item: ---depends_on:step_a ---id:step_b ---action:done ---title:Step B
Step A names Step B as its outcome, and Step B names Step A in ---depends_on. If either half is missing, Step B never appears.
An "always" connection uses ---outcome. The next item shows as soon as the earlier one is done.
A "sometimes" connection uses a numbered filter and outcome on the earlier item:
---filter1|filter:answer GREATER_THAN £10000 ---filter1|outcome:needs_approval ---filter2|filter:answer LESS_THAN_OR_EQUALS £10000 ---filter2|outcome:auto_approve
The filter has the form {what} {MATCH_TYPE} {value}. {what} is usually answer, the item's own answer. The match types are listed on Match types. Comparisons ignore case and currency symbols.
Rules for filters:
Items without ---depends_on show as soon as the task starts, so several can run in parallel:
--#item: ---id:collect_id ---title:Upload ID ---action:attachment --#item: ---id:collect_bank ---title:Enter bank details ---action:text_input
An item can only depend on one item, and an item can only have one outcome at a time. To bring branches back together, use a Blocker (stop action). A Blocker holds back every item listed after it until the items before it are done. Items after the Blocker don't need ---depends_on.
--#item: ---id:branch_a ---title:Branch A step ---action:done --#item: ---id:branch_b ---title:Branch B step ---action:done --#item: ---id:wait_for_both ---title:Waiting for earlier steps ---action:stop ---options:done_at ---block:true --#item: ---id:final_step ---title:Final step ---action:done
See Flow control actions for Blocker options.
---block:true on any item stops later items in the list from being completed until that item is done. It's simpler than a Blocker when you just need "do this first".
Routing checklist for every workflow you write: