Forum Discussion
Locking Advancement until all Layers are Viewed
Good afternoon,
I am working on course with an accordion style showing different layers. I need to make it so that the learner has to complete each of the layers before advancing to the next slide. I added triggers to change the state of each rectangle in the accordion to "Visited" once they've selected it, and change the trigger to "Jump to next slide if user clicks next and all slides = visited" and it won't advance.
Can anyone help?
- JudyNolletSuper Hero
The link I provided in my original reply goes to a post with a demo that explains how to control the NEXT button on interactive slides. That should help you program your slides to ensure the user views all the layers.
I noticed that you copied a Group/button to the associated layer, and hid the original on the base. Why? If you simply show the Group on the base, you'll have less objects to worry about.
I also noticed you used a trigger to change an object to Visited.
That's not needed. Visited is a built-in state, so it comes with built-in functionality. Here's more info: PRIMER: Take advantage of built-in states - Articulate Storyline Discussions - E-Learning Heroes
In addition, I strongly recommend that you give all objects (or, at least, all interactive objects) and layers meaningful names. Do that for variables, too, when you advance to using those. That will make programming and troubleshooting much easier.
Here are some more of my general tips:
- JudyNolletSuper Hero
You don't need triggers to change an object to the Visited state when clicked. Visited is a built-in state with built-in functionality, so that will happen automatically. For more info: https://community.articulate.com/discussions/articulate-storyline/primer-take-advantage-of-built-in-states
Adding an all-objects-equal-Visited condition to the Next button should work. (BTW, I think it's better to disable or hide the Next button until an interaction is done. As a user, I find it frustrating if a button seems clickable but nothing happens.)
At this point, troubleshooting is just guessing without seeing the .story file. If you upload it, someone might be able to solve the issue. Here are the best practices for uploading a .story file:
- Only include slides that are related to the problem.
- Be sure objects, layers, motion paths, and variables have meaningful names.
- If there is proprietary content, replace or delete it. For example, replace proprietary text with “ipsum lorem” text.
Also for future reference: https://community.articulate.com/discussions/articulate-storyline/tip-controlling-the-next-button-101
- AlixGrotewoldCommunity Member
Thank you, Judy! I attached the slide I'm looking to lock advancement. Could you please look to see if there are things I could do to better this? I am self-taught and always looking for the best ways to do things!
I do have my settings to "Restricted" but I would love to know how to hide or disable my next button until all interactions are done for most of my slides. I will look at the reference you attached.