I know how to hide the Next navigation button until a certain logic is satisfied. For example if a number of buttons are selected (all or any). But I need to hide the Next button until all layers of a slide are viewed. Anybody know of a way to do this?
Hi Alyssa, thanks for the answer. The thing is that i cant use buttons or shapes, because its an animated gif with many graphics where you need to click some áreas to show layers.
Hi Marco. Thanks for clarifying. If you can't use transparent shapes, could you adjust one or more variables when clicking the hotspot? You can have the Next button change to the Normal state when the variable changes with a condition about the variable value. Number variables work well here, increasing with each hotspot being clicked.
Yes im almost there, i add a variable for each layer in the main slide "equal to true when user clicks each hotspot" but i dont know how to apply the action of the variable to turn next button normal.
You're almost there! You just need a few more triggers. Check out the changes I made in your file, and let me know if you have any questions about it. I'm here to help!
I'm wondering if someone could help me with a similar issue. I was able to get the Next button to appear in some instances, but it shows on the layer, rather than the base slide. And when the user comes back to the base slide, the Next button is set back to disable, even though the buttons are marked as Visited.
Hello, I have the same problem as Marco above. I have one slide that has 16 hotspots that reveal 16 layers. I would like the user to not be able to progress until all 16 layers have been visited. I do not want to change these to buttons because it is for a left navigation panel screenshot and do not want to show a button. How can I make this happen? I reviewed the variables link above but I am lost lol
I’m not at a place where I can look at your story, but it seems to me that Karen’s option above should work. I’m not sure why it didn’t work for her, but she has the concept and the logic solid. Probably a typo-type error somewhere.
The one problem might be that the learner can advance as soon as they click the last hotspot, without reading the last layer. To avoid that, change the “when” part of the triggers that set the variable. Make it when they take the action that closes the layer.
There are many ways to design conditional navigation in Storyline 360, but one of my preferred ways is by making use of True/False variables to control the navigation. Some notes on my approach:
There will be one master variable which is responsible for controlling the visibility of the Next button
Sub-variables will be responsible for monitoring if layers in the slide have already been viewed
Trigger conditions will check if the learner has viewed all layers to proceed
Each layer will have its own variable responsible for tracking if the learner has viewed the layer
Attached is a sample project file (Slide 1.2) for your reference so you can see the above in action.
I'm sorry this is just over my head.. I don't understand how to add variables correctly and make them reflect what I need. How do I add the variable you made to each layer? Does the number need to be 16 instead of 3?
44 Replies
Hey, Marco!
Instead of hotspots, try using shapes or buttons. That way you can add a Visited state to those objects.
The sample file I shared here is a good place to start. Check out that file and let me know if you have questions about it!
Hi Alyssa, thanks for the answer. The thing is that i cant use buttons or shapes, because its an animated gif with many graphics where you need to click some áreas to show layers.
Hi Marco. Thanks for clarifying. If you can't use transparent shapes, could you adjust one or more variables when clicking the hotspot? You can have the Next button change to the Normal state when the variable changes with a condition about the variable value. Number variables work well here, increasing with each hotspot being clicked.
Hi Crystal, Thanks for take the time to answer.
Yes im almost there, i add a variable for each layer in the main slide "equal to true when user clicks each hotspot" but i dont know how to apply the action of the variable to turn next button normal.
Thanks in advance for your support.
Hi Marco!
You're almost there! You just need a few more triggers. Check out the changes I made in your file, and let me know if you have any questions about it. I'm here to help!
Thanks a lot for your help Alyssa. Now its working fine, thanks for taking the time!
That's wonderful, Marco! Thanks for the update. 😊
This is four years old - but this has helped me immensley! Thank you...
Wow - that's great to hear Sarah...all the best with your project :-)
Hi,
I'm wondering if someone could help me with a similar issue. I was able to get the Next button to appear in some instances, but it shows on the layer, rather than the base slide. And when the user comes back to the base slide, the Next button is set back to disable, even though the buttons are marked as Visited.
Would anyone happen to have any suggestions?
Attach your .story file here, and someone will take a look at it.
Alyssa, I was just looking for the same thing since I'm working with hotspots - I used your file and was able to mimic and fix mine. Thank you!!!
Hi Alyssa Gomez,
thanks for the story file however I am still having issue on the "Next" button not appearing when all the hotspots for each layers have clicked.
I have based what i have done from your file.
VARIABLES:
o1 default value = False
... so on until o6 default value = False
TRIGGERS:
Change state of Next button to Hidden when Timeline Starts on this slide
Hotspot 1
set o1 to value True when user clicks hotspot1
show layer Apple when user clicks hotspot1
Hotspot 2
set o2 to value True when user clicks hotspot2
show later Ball when user clicks hotspot2
... so on until Hotspot 6 (o6)
o1
change state of Next button to Normal when o1 changes
if o1 = value True and o2 = True and ..... so on until o6 = True
... so on until o6
Hello Karen,
Would you mind sharing your project file here or to our support engineers so we can take a look at how your triggers are setup?
Hello, I have the same problem as Marco above. I have one slide that has 16 hotspots that reveal 16 layers. I would like the user to not be able to progress until all 16 layers have been visited. I do not want to change these to buttons because it is for a left navigation panel screenshot and do not want to show a button. How can I make this happen? I reviewed the variables link above but I am lost lol
I’m not at a place where I can look at your story, but it seems to me that Karen’s option above should work. I’m not sure why it didn’t work for her, but she has the concept and the logic solid. Probably a typo-type error somewhere.
The one problem might be that the learner can advance as soon as they click the last hotspot, without reading the last layer. To avoid that, change the “when” part of the triggers that set the variable. Make it when they take the action that closes the layer.
I have no idea how to do what Karen did. The article on variables is confusing as heck to me.
Hello Ashlyn,
There are many ways to design conditional navigation in Storyline 360, but one of my preferred ways is by making use of True/False variables to control the navigation. Some notes on my approach:
Attached is a sample project file (Slide 1.2) for your reference so you can see the above in action.
Let me know if you have any questions!
I'm sorry this is just over my head.. I don't understand how to add variables correctly and make them reflect what I need. How do I add the variable you made to each layer? Does the number need to be 16 instead of 3?
This sample will do what you have asked, but there are a couple of caveats.
This will not work if the actual project navigates to different slides, rather than just different layers on the same slide.
It's unknown if it will work if the learner is allowed to navigate to another slide before finishing this slide.
This would be so much easier if you use transparent shapes, rather than hotspots. For one thing, there are fewer triggers. See slide 1.2.
It allows topics to visited in any order. Requiring a specific order makes it more complicated.