7
Flows: Operations with multiple outputs
Source: directus/directus#22158 · opened by @flipswitchingmonkey
Summary Currently flow operations can only resolve or reject, giving two output options. It would greatly improve the decision flow if operations could have n resolve outputs instead, and one reject. A classic example for this would be a switch-like statement, which could redirect the flow based on a single input or a condition script. Basic Example _No response_ Motivation Flows usually require decision making based on user / payload information, and is very often not just true or false, but can have multiple states. Example: the content of a dropdown field decides the next step in a flow. Currently this would have to be done with multiple staggered condition operations which is rather tedious and can get hard to maintain quickly. A switch-like node or generally nodes with more than one success output could condense this in a single node / operation. Detailed Design To keep the current state of resolve just passing along the payload and without a breaking change, one idea…
No pledges yet. Be the first to back this.
Comments
Similar requests
Import and export option for flows
82 votes · 0 comments
Insufficient documentation about blocking and non-blocking flows
3 votes · 0 comments
Enhancing Directus Flows: Versioning, Archiving, and Improved Manageability
28 votes · 0 comments
Add Sorting for Manually Triggered Flows
3 votes · 0 comments
Disable flows from running on a specific directus instance
2 votes · 0 comments
No comments yet.