Page Opened
Use the Page Opened trigger to run a flow interactively – in your own session, at the moment a user opens one of the supported card pages, before they see it. Because it runs synchronously, the flow can greet the user with what they need to know about this record, or refuse to open the page at all.
Typical examples:
- Show the user a note about this customer the moment the card opens ("payments overdue since March").
- Warn on opening a sales order that its delivery date falls in a factory shutdown.
- Stop a blocked item's card from being opened by anyone outside purchasing.
Supported pages
Pick exactly one page. These card pages are supported:
| Sales | Purchase | Master data |
|---|---|---|
| Sales Quote | Purchase Quote | Customer Card |
| Sales Order | Purchase Order | Vendor Card |
| Sales Invoice | Purchase Invoice | Contact Card |
| Sales Credit Memo | Purchase Credit Memo | Item Card |
| Sales Return Order | Purchase Return Order | |
| Blanket Sales Order | Blanket Purchase Order |
The page picker lists every page in the system, but the trigger only works on the pages above. Pick another one and the status line at the bottom of the dialog says so straight away – "Page 22 (Customer List) is not supported by this trigger, so the flow would never run" – and the flow cannot be published until you change it.
Next to that message sits Request support. It sends the page and the trigger to the AutoFlow team, along with your organization so we can come back to you. The button only appears while the chosen page is unsupported. Your partner can also add pages themselves with a small companion extension; ask us for the details.
What happens when the flow runs
- A user opens one of the supported pages.
- AutoFlow applies your field filters. If the record does not match, the page opens normally and no flow runs.
- The flow runs to the end, synchronously, while the page is opening:
- If it just ends, the page opens as usual – with whatever notifications the flow sent along the way.
- If it ends with an Error step (or any step raises an error), the page does not open and the user sees your message.
Two situations never start a flow, whatever your filters say: a card opened on a new record that has not been saved yet, and a record that no longer exists (for example after someone deleted it in another session).
Trigger output
Rec– a reference to the record the page is showing, so SmartFields can read its fields (e.g.{{<slug>.Rec.Blocked}}) and follow-up steps can use it.PageNo– the number of the page that was opened.
Configure the trigger
Open the flow editor, pick When a page is opened (interactive), and complete the card.
Page
The page whose opening runs the flow. Type a number, a caption or a name, or pick one with the ... button.
Record
Read-only. The table the chosen page runs on – this is what filters and SmartFields work on. It follows the page you pick, so changing the page clears any filters you had set on the previous one.
Timeout (seconds)
How long the flow may run before it is aborted. The user is staring at a half-open page while it runs, so keep this short – the default is 10 seconds.
Field Filters
Optional. Limit the flow to records that match certain criteria (for example Blocked <> ''). Filters are evaluated before anything else happens, so a page whose record does not match costs nothing.
Show a message on the page
Add a Send Notification step to tell the user something without stopping them. Choose Notification for a hint in the bar at the top of the page, or Dialog message when it must be acknowledged.
Keep these flows short
Unlike most triggers, this one runs while a user waits. Every step you add delays the page for everyone who opens it. Keep the work to what has to happen right now – reading the record, deciding, telling the user – and leave anything slower (calling a web service, writing to other tables) to a background trigger such as Record Modified.
A flow that errors stops the page from opening. That is deliberate and occasionally exactly what you want, but it also means a mistake in the flow can lock a page for everybody. Test on one record with a narrow filter before you widen it, and remember that unpublishing the flow restores the page immediately.