Page-entry outcomes and routes

An outcome is the action a Guide runs in response to a trigger. Page entry runs when someone enters that page in Preview or Play. Editing the page itself does not run it.

You need Guide edit access to configure outcomes.

Set an entry outcome

1. Select the source page and choose Page > Page settings > Entry.
2. Under When this page opens, choose an outcome.
3. Complete its destination, Message, or Speech text when needed.
4. Choose Outcome timing.
5. Select Save page, reopen to confirm the saved choice, and test in Preview.

Choice	Result
None	Leaves the page open without an entry action
Next page / Previous page	Moves within the sequence; Previous can return from a routed path
Go to page	Opens the selected page in this Guide
Go to sequence start	Opens the selected sequence's first page
Popup Page	Opens a page in a flyout above the current page
Show message	Displays the supplied notice without moving pages
Read text if automatic reading is enabled	Requests speech subject to the player's opt-in and Guide/Page restrictions
Positive splash / Negative splash / Neutral splash	Requests the corresponding optional effect
Close guide	Opens the Guide's configured Close-guide screen
Finish guide with a message	Shows the supplied message, then closes the Guide

Next and Previous are unavailable in the picker when there is no corresponding adjacent page. Next page does not mean “start the next sequence” or “finish.” Go to page excludes the current page. A sequence route that resolves to the current page is unavailable during playback.

Use a nonempty Message for Show message or Finish guide with a message. At page entry, leaving Speech text blank uses normal prepared page narration; it does not force speech on or play a second copy of that narration. Timer speech requires supplied text.

Set the delay

Follow player setting uses the player's saved action delay. Override player setting replaces it with Override delay (seconds), from 0 to 3,600 whole seconds. Zero requests an immediate action.

For most outcomes, this is a wait before the action. Finish guide with a message instead shows its message immediately and uses the delay as reading time, with a minimum of three seconds, before closing. In Play it captures the session Report; Preview does not create a Reports inbox record.

The Close-guide screen uses the title, message, and actions in Guide settings. It is separate from Finish guide with a message and from the player's ordinary Finish action.

Understand Popup Page

A popup leaves the underlying page in place. Close popup returns to that page, or to the previous popup when several are open. Browser Back also closes the popup layer. Navigation inside the popup stays inside that popup; a Close guide or Finish outcome still ends the Guide.

Covered page outcome timers pause and resume when the page is uncovered. Repeated automatic popup loops are stopped with a notice, and the popup can still be closed. Avoid making a page automatically open itself as a popup.

Check every path

Routes retain their destination when it is renamed or reordered. A deleted or moved destination can become unavailable; choose it again and save.

In Play, missing required answers can block forward or cross-sequence routes and completion. Preview does not enforce those same required-answer navigation guards. Review the Fields and validate real use where needed.

Returning with Previous from an automatic transition suppresses the returned page's automatic entry and timer actions so it does not immediately send the player away again. Leave and re-enter normally when testing a new visit.

Review Warnings, test available destinations, and leave a usable way forward. A message, speech request, splash, or popup is not by itself a route out of the underlying page. See navigation locks.