Field after-submit actions and feedback

An after-submit action runs when the player accepts a response through an answer method. Use it to show feedback, continue to another page, or finish the Guide. You need Guide edit access to configure it.

Configure an action

1. Edit a Field and select the answer method.
2. Open Advanced settings.
3. Under After a successful submit, choose an action.
4. Supply its destination, Message, or Speech text.
5. Set Outcome timing.
6. Select Save block, reopen to confirm the saved choice, and test it.

Available actions include None, Next page, Previous page, Go to page, Go to sequence start, Popup Page, Show message, Speak, Close guide, Finish guide with a message, and the three splash choices.

Next/Previous use adjacent pages in the sequence. Next page does not mean finish or start the next sequence. A destination that is deleted or moved may need to be selected again. Popup Page opens above the current page; see page outcomes and routes.

Complete required text and destinations before saving. An incomplete local outcome selection can leave the earlier valid choice in place; reopening confirms what was saved.

Combine a splash with a follow-up

Choose Positive splash, Negative splash, or Neutral splash. Then choose one follow-up under Then. Leave Then at None for splash only.

With a follow-up, feedback begins when the answer is accepted and the action uses Outcome timing. Users can reduce or disable effects; this does not prevent the follow-up. A zero delay can continue without waiting for the animation.

Follow player setting uses the learner's saved action delay. Override player setting accepts Override delay (seconds) from 0 to 3,600 whole seconds.

Finish guide with a message shows the message immediately and gives it at least three seconds of reading time before finishing. Close guide opens the configured Close-guide screen. Merely naming a button “Submit Report” does not give it either action.

Understand when it runs

Autosaves that only preserve a draft do not run an explicit-submit action. Use the method's Submit, Confirm, Continue, or other finishing control when offered. Failed or rejected answers do not trigger the action. Accepted offline answers can be queued for later synchronization.

For a single-selection Options method, a configured outcome on the chosen final option takes priority over the method's general submit outcome. Browsing an option that has children is not a final answer.

Skip has a special rule: when it is the only method, its actions do not run. See Skip answers.

Changing an answer or navigating away can cancel a pending action. Return to response methods alone does not cancel an accepted action. Do not assume that returning to the chooser prevents navigation.

In Play, other unanswered required Fields can still block navigation or finishing. Preview permits departures that Play guards. Test the whole page, and keep a usable way forward after any message, popup, or splash.