Forum Discussion
Urgent Storyline help!
Hi everyone,
I'm hoping someone might be able to help me troubleshoot an issue I'm encountering in my Storyline project.
In the file I'm attaching, within Part 3 – Decision Point, there's a multiple choice slide titled 2.3 Pick_all. From this slide, the user can choose between three options. For example, selecting Option 3 correctly navigates to the Part 3 Options scene and plays the Option 3 video.
The intended behavior is as follows:
- After the video plays, the user is returned to the 2.3 Pick_all slide, with Option 3 disabled.
- Then, selecting Option 2 plays the Option 2 video, after which the user returns again to the same multiple choice slide, now with both Option 2 and 3 disabled.
- Finally, selecting Option 1 should take the user to the Conclusion scene after the option 1 video is finished, titled Behind the Scenes.
However, when Option 3 is selected, it plays the video and then jumps straight to the conclusion, skipping the rest of the branching logic despite there being no trigger set to do that.
Has anyone experienced this behavior before or know how to fix it? I'd like all options to function as intended and lead to the conclusion only after all choices are completed.
Thanks in advance for any guidance you can offer!
Personally, I wouldn't disable the Option buttons after the user has seen the related video. Instead, I'd give the buttons a Visited state. And I'd put them into a Button Set, so that only 1 could be Selected at a time. That would show which was currently selected, remind the user which buttons had already been clicked, but allow them to revisit any option.
For more info about the how the built-in states and button sets work, see https://community.articulate.com/discussions/discuss/primer-take-advantage-of-built-in-states/777134
2 Replies
That file is way more complicated than it needs to be. Slides 2.3 through 2.9 have the exact same content, except for which buttons are clickable. And that requires multiple triggers to "return" to the appropriate slide. (It would also require you to revise all of those slides if that content needed editing.)
You only need 1 slide with that Options 1-3 content. Triggers can change the already-selected option to Disabled based on simple T/F variables that track which button has already been clicked.
Then the "Next" button on the video slides can be programmed to return to the PickAll slide if any of the T/F variables = False. Otherwise, it can jump to the Conclusion (or wherever else you want it to go).
This has been set up in the attached version. Note that I hid most of the content on the video slides, and made the Next buttons available right away. (I don't waste time watching videos when troubleshooting.)
I didn't take the time to figure out what the Xavier variables were doing, nor when the SME VIDEO was supposed to be shown. But the edited version will allow you to delete slides 2.4 through 2.9.
Personally, I wouldn't disable the Option buttons after the user has seen the related video. Instead, I'd give the buttons a Visited state. And I'd put them into a Button Set, so that only 1 could be Selected at a time. That would show which was currently selected, remind the user which buttons had already been clicked, but allow them to revisit any option.
For more info about the how the built-in states and button sets work, see https://community.articulate.com/discussions/discuss/primer-take-advantage-of-built-in-states/777134
