General Usage
Typical Workflows path: choose the right logic area, move into the dedicated editor, and continue with the right family guide.
Introduction
Section titled “Introduction”A typical Workflows path has three decisions: choose where the logic should run, move into the dedicated editor family, and then keep building there instead of bouncing between concepts.
Choose the Runtime
Section titled “Choose the Runtime”The first useful question is runtime, not tool name. Ask whether the logic belongs on the server for security and data access, or in the client for UI response and local interaction.
Move into the Dedicated Family
Section titled “Move into the Dedicated Family”Once the runtime is clear, stop treating Workflows as the whole lesson. Move into Server Connect Actions or App Connect Flows and stay in that family while you build the first working result.
Return Only for Orientation
Section titled “Return Only for Orientation”Come back to the Workflows family when you need to re-orient, compare the two logic areas, or hand off to another workflow type. Use it as a map, not as your only building guide.
Workflow Finish
Section titled “Workflow Finish”The practical Workflows habit is to choose the execution model early, then keep the learning path focused. That is how the docs and tours stay easy to grasp instead of collapsing into one giant concept pile.