Forum Discussion

TaraLaughlin's avatar
TaraLaughlin
Community Member
7 years ago

Next button doesn't work after Previous button used

Hello everyone,

I've published several Storyline360 courses using SCORM 1.2, and I'm noticing a similar bug in many of my courses, though I can't figure out what's causing it.  

When I go through my course straight through, everything functions properly.  But then, if I use the Previous button to return to a previous slide, the next button doesn't return.  See short screencast HERE.

Can anyone tell me what is causing this, and how to fix it?

Thanks!

  • Hi again,

    I am struggling to get the next button to work correctly on this Infection control section now. It seems to work ok for me if I go through the section exactly as intended but the moment do click slightly differently the next button will no work. This issue is mainly on the slide 1.5 (the one with the big stop sign). My testers are struggling to get past this page and I can't seem to figure out what the issue is. I am wondering if it is a revisiting issue? It seems to work fine if you go through and don't accidentally or purposely revisit any of the pages but as soon as you do the next button won't activate. I tried adding a revisit variable but that didn't seem to help. I have attached the story file here for you. 

    Also on a related note you will notice I was only able to get the previous button to work on slides not connected to a quiz. As soon as it hits a quiz a previous button will not function properly so I ended up just putting the previous buttons around the quizzes which works but it's ideal.   

    Any help is greatly appreciated!  

    Best,

    Stephanie

  • Hi, Stephanie.

    Thank you for sharing your .story file!

    On slide 1.5, you want the Next button to become active only when all the layers and sub-layers are visited. The way you set up the trigger will only work if the last layer visited does not have sub-layers:

    • Change the state of Next to normal when all the layers are visited IF all the sub-layers are visited.
      • If not all sub-layers are in that state when the last layer is visited, the trigger won't execute. 

    The alternative is to use a custom state to check, instead of Visited. You have two options:

    Option 1: Create a state (let's call it FullyVisited) for all your buttons on the base layer and the buttons on the other layers.

    Windows 10 (1) 2022-06-15 at 10.17.05 AM 

    • Add triggers on your base layer to change the state of the button to FullyVisited when the three layers that don't contain sub-layers are called.
    • On the three sub-layers, add the trigger to change the state of those related rectangles to FullyVisited when the timeline starts on the layer.

    Windows 10 (1) 2022-06-15 at 10.18.39 AM

    • On the base layer, change the state of the Next button to Normal when all the rectangles are in the FullyVisited state.

    Option 2: Create a FullyVisited state only for those three rectangles connected to layers that have sub-layers.

    • Create two triggers to change the Next button to normal: one where three rectangles are visited if the three others are FullyVisited. Another one where the three rectangles are FullyVisited if the other three are Visited.

    Windows 10 (1) 2022-06-15 at 10.17.55 AM

    • On the three sub-layers, add the trigger to change the state of those related rectangles to FullyVisited when the timeline starts on the layer.

    I'm attaching an edited version of your file with the second option above. 

    I hope this helps!

  • Thank  you so much! I definitely would not have come up with this solution on my own. It seemed to work great for me and I have asked my testers to now give it a try.  Cheers, Stephanie