> For the complete documentation index, see [llms.txt](https://inistate.gitbook.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inistate.gitbook.io/home/features/flow.md). # Flow

The area within the red frame highlights the Flow panel.

### Usage * **Flow Configuration**: Each Flow defines valid transitions, ensuring entities follow an expected path. * **Conditional Transitions**: Some Flows allow conditional steps where specific criteria must be met for transitions to occur. ### Flow Configuration Flow Configuration plays an important role in guiding entities through well-defined paths. It comprises three core components, ensuring that processes progress logically and predictably: * **From State**: This is the initial phase from which an entity begins its transition. It sets the context for all subsequent activities and transitions. * **Activity**: The action or event triggered by a user, serving as the catalyst that propels the transition forward. Activities dictate the conditions required for moving between states. * **To State**: The resulting phase following the completion of an Activity. It reflects the new status or condition that an entity has achieved post-transition. By specifying these elements, Flow Configurations provide a clear structure that aids teams in executing processes effectively, enabling smooth transitions and incorporating fallback paths for unexpected scenarios. ### **Conditional Transitions** **Conditional** The **Conditional** functions as a toggle switch within the Flow Configuration, allowing users to change "To State" to "Conditional States". #### Conditional States Conditional States is an evaluative condition that is checked after an "Activity" is performed. This condition determines if the process should advance to the next stage. Below it has a formula condition and description of the condition flow. ### Best Practices * **Sequential**: Ensure Flows progress logically, allowing smooth transitions. * **Fallback Paths**: Where applicable, include fallback paths to handle unexpected scenarios. * **Documentation**: Document each Flow to ensure all team members understand the process.