In-page
Runs in a page Page context
Page Flow (in-page)
Page Flow executes inside a page, can interact with that page’s components/actions, and can return data.
Page Flow (in-page): what it is
Section titled “Page Flow (in-page): what it is”Page Flow is a client-side workflow that executes inside a specific page. It can interact with that page’s components/actions and can return data.
TIP: Use a Page Flow when the workflow belongs to one page and needs to interact with that page’s components/actions.
Interactive
Can call page actions Component access
Returns data
Expose results To the page
Use Page Flow when the workflow is page-specific and needs page context.
Great for multi-step UI interactions with branching (confirm, toast, navigate, refresh).
If it grows, keep it readable: name steps and handle errors explicitly.
Define a Page Flow (inline HJSON)
Section titled “Define a Page Flow (inline HJSON)”A Page Flow lives inside the page as a dmx-flow script block. It can branch and execute steps sequentially.
Define the flow inline as a `dmx-flow` script block in the page.
Keep it page-specific: it can interact with page variables/components/actions.
Use it to orchestrate multi-step UI flows (confirmations, branching, sequencing).
Run it and use results
Section titled “Run it and use results”Run the flow from an App Connect event, then read flowId.data, flowId.running, and flowId.lastError in your UI.
Use `flowId.run({ ... })` to pass parameters into the flow.
Read `flowId.running` to show progress while it runs.
Use `flowId.data` / `flowId.lastError` to update the UI based on outcomes.
Wrap-up
Section titled “Wrap-up”Review what you did and choose a next tour.
Next steps
Section titled “Next steps”Pick a related tour to continue.