Server Connect Actions
Protected data Reusable endpoints
Workflows Reference
Compact cross-family reference for the workflow taxonomy, the server/client boundary, and the best next reference family.
Introduction
This reference exists to keep the workflow taxonomy clear. Use it to confirm whether a problem belongs on the server or in the client, then jump into the matching reference family for the detail you actually need.
App Connect Flows
UI logic State + interaction
Handoff discipline
Confirm the boundary Then move on
Server Connect Actions own secure server-side workflows and reusable JSON endpoints.
App Connect Flows own client-side interaction logic, flow control, and page or event behavior.
This tour is only the cross-family map; implementation depth lives in the dedicated families.
Next steps
Once the boundary is clear, open the reference family that owns the detail you need. Return to the Workflows hub only when you need to compare the two workflow domains again.
Use family reference tours when you need editor or action taxonomy.
Use the family hubs when you need guided entry points and practical build coverage.
Keep the umbrella workflow layer small so it stays useful.