Next button won't reappear (return to normal) when critieria is completed
Sep 24, 2015
I read the following instructions on how to temporarily hide the "next" button in the course player.
http://www.articulate.com/support/storyline-2/how-to-temporarily-disable-or-hide-navigation-buttons
When I tried to apply it to my slides, it worked for one of them but didn't work for the other slide I tried. I am complete lost as to why it is working for one but not for the other. Has this ever happened to anyone else? Is there someone who might be able to advise?
Some more info about the two slides below:
Both slides for which I am hiding the "next" button are what I am calling "main menu" slides.
One has hotspots that take you to other slides, and for each slide that is viewed, the user is automatically taken back to the main slide. Once all of the slides are visited, the next button appears. The "visits" are tracked by markers and when their states change to a custom-made completed. There is also a trigger setup so that the next button returns to normal when the very same markers are all "completed." -- This slide works exactly as it should.
The other slide is exactly the same except that instead of hotspots, it has objects which are being tracked. My-coworker and I tried several different things, including tracking by a visited state for those objects, tracking with the custom-made completion, changing the order of the triggers -- nothing has worked yet. We do not understand why or what it is we might be doing wrong. I have screenshots of both trigger panels attached, hoping that maybe someone can identify why the 1st set are working but the 2nd set is not.
If someone could advise it would be greatly appreciated!
Thank you.
8 Replies
Hi Alicia,
In a scenario such as this, it's best if we can take a look at your .story file to see how all the elements are set up and what states, triggers, etc. that could be interfering with this. If you'd like you can attach it using the button at the bottom of the reply box to "add attachment" and we'll be able to investigate your file further.
Hi Ashely. Thank you for responding. I also submitted an articulate support case for this file earlier. In the support case I submitted, I did attach the file. Would you be part of that same support group? I was hesitant to post the file on the forum.
Hi Alicia,
Thanks for letting me know you're working with our Support team. I can see Abel is assigned to your case (# 00650959 for my reference) and is currently testing it, so I'll follow along in his work so that we're not duplicating efforts. He'll keep you posted via email and I can include any updates here as well.
Sounds good. Thank you!
The two sets of triggers are not the same. The one that doesn't work sets a variable, and the one that does work, doesn't. Therefore it seems likely that the problem lies in what is being done with that variable. That is where I would start troubleshooting.
Hi Alicia,
Looks like that is what Abel found too. He shared an updated copy of your file and the following:
You just needed to be more specific by adding conditions on the trigger that will change the next button to hidden only if any of the variables is still "False". See this for reference: http://articulate.fyi/1PySbcT
Feel free to let Abel or I know if you need anything else.
Thank you, Everyone! This solved our problem. Thank you for your help!
Thanks for that update Alicia!
This discussion is closed. You can start a new discussion or contact Articulate Support.