How to get the Next Button to reappear
Sep 04, 2019
Hi there,
I'm working on a project and I've been reading through all the forums and watching as many videos as possible and I'm still at a loss.
Does "Remove the built-in Next button and create your own custom navigation button" steps only work when CREATING a navigation button (https://community.articulate.com/articles/make-your-e-learning-smarter-with-conditional-navigation-buttons?page=1#comment-81536)?
Because I'm trying to get it to work with the original next button, and its not functioning properly.
I've "hidden the next button when timeline starts". And then "change state of the next button to Normal when the state of x and y and z are visited".
Please help!
Stephanie
22 Replies
Can you provide the slide that has the problem? At the very least we need to see the triggers to know what problem is occurring.
Hi,
Please view the attachment of the triggers and let me know if anything else is needed.
Thanks so much.
Does the user return to the base layer or does the user finish on a layer? Can you share the .story file or just that slide makes it easier to help you troubleshoot the issue.
returns to baselayer
Here is a Peek video setup as you have explained and its working as expected
If you can share the file perhaps someone can take a look and see what's happening...the only thing I can think to check is make sure there isn't something else ticked in the trigger wizard when you are selecting the visited states of your objects.
"Visited" state is a bit tricky because if the item is still currently selected then it's not yet in the visited state.
Can you see a visual change in each of the elements to confirm that they are in the visited state?
I've attached a mock module my teammate created with the exact triggers we're working with. Please advise!
Hi Stephanie
it's working for me unless I misunderstand what you mean. The Next button is disabled on timeline start and enabled when the last object is clicked (visited).
If you mean it's displaying before you close the last layer that is because you are using the built in visited state. If you don't want that to happen you'd need to create a custom 'completed' state and use triggers or use variables.
See this Peek...I changed the visited state of each object to B & W so I could make sure its working.
Maybe I'd need to create a completed state then.
Wehn we test it, after each layer is visited, it displays the base layer, but the next button isn't clickable. It doesn't progress forward.
here it is mocked up with a 'completed' state.
If it doesn't work with this trigger can I suggest you publish the file and upload to where you intend your users to see it e.g. web or LMS and test it there.
Theyd be viewing it in LMS.
So to clarify, the way the triggers are set up in the mock module, you're able to view and click on the next button after visiting the 4 layers?
Yes - I had no issue previewing and clicking the next button using the built in visited state and then when I created a custom state - result was the same I could click next and advance.
I would recommend you publish to LMS and upload to Scormcloud (industry standard LMS) and make sure it works. See this KB article for more information.
sorry, we have tested it in LMS and we encounter the same issue :(
Thank you Wendy for all your help!
Hi Stephanie
I think you should log a support ticket with Articulate and see if they can assist you with this. I can't replicate the issue you are having so can't help you any further - sorry.
Support > Submit a Case
Alrighty, thank you for all your help!
Thanks for reaching out to our support team, Stephanie. I see that Renato is currently assisting you.
Yes, everything got worked out! thanks so much for your support!
Hi Stephanie
can I ask what the solution was - it may help someone else that experiences this issue.
Thanks, Stephanie! I saw that Renato was able to test your course in Review 360 and an LMS instance and the same issue didn't occur. It sounds like it may have been specific to your LMS setup?
I have a question for the next button. The next button is "disabled" when we didn't visit all the pictures. That's what I do in my slide, but when I come back to this slide, the next button is alway disabled. I download the mock above, this problem isn't solved. I would like to know, if there is a problem on my side? Thanks for your help.
Hi Lingling!
I've added an updated file to this reply. You'll see that I added a variable, VisitedState, which is set to true when the state of the ovals is equal to visited. The next step is to add another trigger to change the state of the next button to Normal when VisitedState is equal to true.
Take a look at the course and let me know if you have any questions!
This discussion is closed. You can start a new discussion or contact Articulate Support.