Forum Discussion
Please give us more flexibility with "Reset to initial state" when revisiting
Hi,
My team is sometimes asked to build courses where it should not possible to proceed to the next slide until a question is answered correctly. I understand the only way to achieve this is to force a page to "reset to initial state" when revisiting, and then trigger a "jump to this slide" action via a Retry button.
However, this causes the undesirable side-effect that the slide will always reset regardless of the reason the page is being revisited. We don't want the page to reset if the question was answered correctly, and the learner is revisiting simply to review the content.
Is there already a way to achieve this?
Many thanks in advance.
This sounds like the behavior that unlimited retries would give, unless I am misunderstanding the use case.
3 Replies
This sounds like the behavior that unlimited retries would give, unless I am misunderstanding the use case.
If it is a graded-question slide, I suggest setting the revisit option to "Automatically Decide." That lets Storyline's built-in functionality work.
A graded question can be set to allow multiple attempts. If you set it to unlimited attempts, it will automatically show the Try Again layer until the user answers correctly. By default, the "Try Again" button just closes that layer. The responses still show the user's previous answer. However, you could add triggers to the "Try Again" button that reset all the responses to their Normal state.Here's more info about the built-in option for multiple attempts and how to reset responses:
If it is a custom slide, you could disable the Next button when the timeline starts on the slide. Include a condition so that trigger won't run if the correct answer has already been selected. Also add a trigger that enables Next when the user answers correctly. Here's more info about ways to control the Next button:
Ah yes I see what you mean. After enabling unlimited retries, simply hiding the feedback layer is enough to allow another attempt. Thank you for such a quick response. This has solved it.
