I have created a slide with 4 pictures on it which, when clicked, send the user to four different scenarios. I have set a trigger to stop the Next button appearing until all the scenarios have been visited.
When I preview the slide the Next button appears at the correct time, but when I run the entire project the Next button does not appear even though all the pictures have been 'visited' .
Hi, Tina -- Thanks for your question! After you publish, are you viewing the published output in the intended environment (or the location where your learners would view it)? Please see this information on Publishing and Sharing Articulate Storyline Content, as when you view it locally, you will encounter security restrictions that cause various components or features to fail.
If you are still having troubles, feel free to share your file and I will gladly take a closer look for you!
Thank you Christie. I was previewing in Storyline so will try publishing to our LMS and check it there.
It's annoying as it is a long project with audio and characterisation and this bit is near the end. I couldn't get any further than this slide to preview the rest and as it branches out to other scenes I have to preview the whole project every time.
Thanks, Tina, and certainly please let us know if you still need assistance!
I also wanted to note: when you reply via email, your signature is displayed publicly here in the thread, so you are welcome to use the Edit button beneath your post to remove those details if you wish. :)
is only activated when a state changes. You can test this theory :
Erase the jump trigger on one of your Scenarios, Preview and visit the other Scenarios first. When you click on that last scenario, the NEXT button appears.
What happens when the 4th Scenario is clicked is that the NEXT button appears, the jumps occurs so fast you don't see it. When the user finishes the scenario and returns to the menu, the button is hidden when the timeline starts. Until something on the slide changes state, your trigger isn't activated.
This trigger will get around that
I have experienced some flakiness with the visited state when I jump to another location, especially one that uses several slides, or gives the user branching choices. That is why I always set variables and use them to do things like this, instead of relying on the visited state. Besides, I can set the variable when the user finishes the branch,rather than when they start it. FWIW
Hi, Tina -- I see the file you posted is no longer available, however, please let us know if Walt's suggestion will work for you, and if you need further assistance. You are always welcome to repost your course for review! :)
Thank you for looking at this. I took the post down as I found a video posted by articulatedf about how to disable the Next button. As per his instruction I have used variables and it all works fine.
8 Replies
Hi, Tina -- Thanks for your question! After you publish, are you viewing the published output in the intended environment (or the location where your learners would view it)? Please see this information on Publishing and Sharing Articulate Storyline Content, as when you view it locally, you will encounter security restrictions that cause various components or features to fail.
If you are still having troubles, feel free to share your file and I will gladly take a closer look for you!
Thank you Christie. I was previewing in Storyline so will try publishing to our LMS and check it there.
It's annoying as it is a long project with audio and characterisation and this bit is near the end. I couldn't get any further than this slide to preview the rest and as it branches out to other scenes I have to preview the whole project every time.
I'll get back to you if it is still a problem.
Thanks, Tina, and certainly please let us know if you still need assistance!
I also wanted to note: when you reply via email, your signature is displayed publicly here in the thread, so you are welcome to use the Edit button beneath your post to remove those details if you wish. :)
This post was removed by the author
This post was removed by the author
Hi, Tina -- Thanks so much for providing your file for testing, and I will follow up with you soon! :)
Tina, I think that this trigger
is only activated when a state changes. You can test this theory :
Erase the jump trigger on one of your Scenarios, Preview and visit the other Scenarios first. When you click on that last scenario, the NEXT button appears.
What happens when the 4th Scenario is clicked is that the NEXT button appears, the jumps occurs so fast you don't see it. When the user finishes the scenario and returns to the menu, the button is hidden when the timeline starts. Until something on the slide changes state, your trigger isn't activated.
This trigger will get around that
I have experienced some flakiness with the visited state when I jump to another location, especially one that uses several slides, or gives the user branching choices. That is why I always set variables and use them to do things like this, instead of relying on the visited state. Besides, I can set the variable when the user finishes the branch,rather than when they start it. FWIW
Hi, Tina -- I see the file you posted is no longer available, however, please let us know if Walt's suggestion will work for you, and if you need further assistance. You are always welcome to repost your course for review! :)
Thank you for looking at this. I took the post down as I found a video posted by articulatedf about how to disable the Next button. As per his instruction I have used variables and it all works fine.
Fantastic, Tina! So glad to hear you are all set and thanks so much for the update! Please let us know if you need anything else! :)
This discussion is closed. You can start a new discussion or contact Articulate Support.