Forum Discussion

SaraPieczarka-8's avatar
SaraPieczarka-8
Community Member
4 years ago

Next Button Disabled on Revisit

I have the prev/next buttons set to locked. When I click on previous and it takes me back one slide, the next button looks enabled and then automatically goes to disabled upon revisiting the prior slide.

My revisit condition is set to "Resume Saved State". My next button triggers on the current slide are to disable at start of timeline and change to normal when either a video complete or the timeline ends.

Why won't my next buttons state enabled upon revisit if I have the condition set to "Resume Saved State" upon revisiting?

  • Hi, Sara,

    Unfortunately, there's a known bug. When a slide is set to "Resume saved state," it won't replay the timeline animations and such. However, the program will re-execute timeline triggers.

    If you want to disable the Next button the first time the user encounters each slide, the simplest way is to set the Menu Options to Restricted navigation.

    • With Restricted navigation, Storyline will automatically disable the Next button the first time the user visits a slide. It will enable Next when the timeline finishes. After that happens, Next will remain enabled for that slide.
    • This works even if you don't show the built-in Menu. (If you do show the Menu, the user can click it to go to a previous slide, but they can't advance by clicking the Menu.)
    • You can override this for interactive slides by adding your own triggers to control the Next button.

    If you only want to control the Next button for a given slide, do this:

    • Create a T/F variable, with an initial value of False.
    • Add a trigger that disables Next when the timeline starts, with the condition that the variable is False
    • Add a trigger that enables Next when the timeline ends (or when an interaction is completed). 
    • Add a trigger that adjusts the variable to True when the  timeline ends (or when an interaction is completed). 
  • MichelleCorby's avatar
    MichelleCorby
    Community Member

    I too have this issue with this bug and was quite relieved as I was starting to doubt my logic.

    I've tried to implement the suggested fix using the variables option, but I can't get it to work.

    My next button doesn't change to "normal" and I'm not sure what I'm missing, I've attached screenshots of my triggers.

    Can anyone help please?

  • Hello Michelle,

    Thank you for chiming in with what you see as well. You mention that your next button doesn't change to normal and I'm not seeing a trigger to do so.

    Try adding a trigger that states:

    • Change state of
      Next Button
      to Normal
      When the state of all of
      Commission btn
      Maint btn
      Permit btn
      Restore btn
      is Visited
  • MichelleCorby's avatar
    MichelleCorby
    Community Member

    Thanks so much Leslie,

    I knew it was something simple (have been looking at it too long).

     

  • I appreciate everyone's reply! Using @Judy Nollets recommendations I was able to resolve the issue using the restricted format and deleting all triggers that I had connected to the next button. That was the only way to resolve it. 

  • I am new to Articulate. A project I am working on requires the timeline restricted till slide media completes. I found the menu restriction very helpful. I am using inbuilt navigation rathe than create a custm button but the only issue is that the next button is still restricted upon revisit and not as Judy Nollet explained above. I wonder if I am doing anything wrong. I also noticed that the accessibility shortcut for "next" and "back" does not obey the menu restriction. Is there a way around this?

    Thanks

    I found help through this link: How to disable and enable next buttons - Articulate Storyline Discussions - E-Learning Heroes

  • Hi Vincent!

    Welcome to Storyline and the E-Learning Heroes community!

    It would be very helpful if we could see your project file so we can see how you set up your buttons and shortcuts.

    Would you be willing to share a copy of your project file here or in private by opening a support case for testing? We'll delete it when we're finished troubleshooting!

  • Thank you so much @Steven Benassi. I was able to get permission to share a sample of my project and just submitted a case for the accessibility shortcut and toggling play/pause using built-in features.  Regarding the restricted navigation, I was able to figure that out. I initially enabled "restriction" because of the favourable wordings.

    • Restricted means learners can view the current slide and any slide they previously viewed, but they can't jump ahead or skip over slides.
    • Locked means learners can only view slides in the order you've designed. They can't jump ahead or skip over slides, nor can they go back to any previously viewed slides.

    However enabling "locking" simplified the process and all I needed to do was add triggers for viewing the next or previous buttons. I didn't have to create any trigger for revisiting the slide. 

    This is a very helpful community. Thank you all.

     

    • StevenBenassi's avatar
      StevenBenassi
      Staff

      Hi Vincent!

      My pleasure! Thanks for sharing the feedback on what worked for you! I'm sure it will be useful to other community members when coming across this thread!

      Also, great call on opening up a support case! Our support engineers have a wealth of knowledge and insight so you're in excellent hands!

      Please let me know if you need anything else!

       

  • Many thanks to Articulate Support for reviewing and finding a work around to my accessibility request. The steps are listed here below and the sample attached. 

    Thanks for contacting Articulate Support!

    I understand that you wanted to use the keyboard left and right for navigation but you wanted it to follow the navigation restrictions.

    You may want to consider using True/False variable as condition to your keyboard navigation triggers. Here's how:

    1. Create a new true/false variable. Name it "Nav" with an initial value of false.
    2. Select View > Slide Master > Slide Master # 2 3. Modify your Jump to Slide triggers and add the condition below:

    If Nav = value True.

    See the screenshot for your reference: https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsharing.articulate.team%2F5zujodp7&data=05%7C01%7Cvincent.olakanye%40ontario.ca%7Cd9d187e645c441dc7c0608db45d6eca0%7Ccddc1229ac2a4b97b78a0e5cacb5865c%7C0%7C0%7C638180563068818707%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GJpQoeV9XKrhB%2FgMJ5J%2BmclJ6eH63bJeR2Xuz0BD2hw%3D&reserved=0

    1. Select Close Master View.
    2. Add the following triggers to all your slides. Note that you can select both triggers in the triggers panel and use the copy/paste to add the triggers to all your slides.

    Action: Adjust variable

    Variable: Set Nav to value False

    When: when the timeline starts on

    Object: This slide

    Action: Adjust variable

    Variable: Set Nav to value True

    When: when the timeline ends on

    Object: This slide

    We are adding this in the slide level instead of the Slide Master layout because each slide has a different timeline duration.

    1. Save and publish your project.