Use a Result node to mark the end of your module. You can use multiple Result nodes in your module to allow for multiple different outcomes.
Note that every branch of your module must end in a Result node. You can also switch from the default Result node to a Redirect Result node to send your end user to a different page, data view, or module.
What is a Result node?
Result nodes are the nodes concluding a path through your module. Each path in your module must end with a Result node for all possible combinations of answers. Otherwise, your module will have a 'dead end' and the module will display an error message to your end user.
A Result node irrevocably concludes a session. That means end users cannot go back to a previous node after arriving at a Result node, and the resume session link can no longer be used to access the session. Additionally, the session is logged in the statistics of the module, unless this feature is disabled in the module's publishing settings.
Configuration options
- You can enter and format text, as well as insert images, files, videos, and more in the CONTENT field.
- You can display a document at the right hand side of your node, using Document View.
- You can toggle on a confirmation screen before redirecting from the last node to the result. This gives your end user an opportunity to go back and change their answer(s) before continuing to the final result.
Occasionally asked questions
I ended up with a lot of Result nodes. What can I do to simplify my module?
Often you can reduce the number of Result nodes by using conditional blocks or text variable updating. This way, you can display relevant information depending on end user answers. For example, you can have two Result nodes Approval and Rejection and equip each of them with a different explanation that depends on the end user's path through the module.