Overview
This document will describe how to set up an advanced configuration for a Dashboard. In this setup Runtime Selection and Design Patterns are combined to create an environment where junior developers can build small Flows.
The interface leverages runtime selection and design patterns to allow for a core engine flow to be built that can identify and call a subset of these small microflows given a specified logic. It then fetches these Flows and executes their internal logic in a loop allowing users to easily add and maintain the logic without needing to touch the main engine Flow itself.
Runtime Selection fetching Flows from a folder with a Design Pattern creates a system that can be applied to any use case where limited, but flexible access to the Flow Designer is required. This could be for internal teams to easily extend or edit the existing set of microflow logic you might ship with launch.
Build the Design Patterns
Design Patterns force every Flow or Rule added to a Designer Folder to inherit a set input and output definition. Runtime Selection requires that all Flows have the same Inputs and Outputs, so using a Design Pattern here will save time in configuring new Flows.