There is this peculiar problem which I am facing for all my projects. I want to restrict the navigation to the next screen before the user visits all the tabs. For this, I have used 2 triggers:
1. Next button disabled when timeline starts
2. Change state of next button to enabled when state of .... is visited
This trigger works perfectly fine for the first time. But if come back to the screen, I cannot proceed, even if I visit all the tabs again. I have tried to set the properties while revisiting to resume to saved state as well as reset to initial state. The only option is to use the Menu to proceed ahead.
I have faced this on more than 60 projects till date.
Anyone else faced it? Any workaround? Or am I doing something wrong?
It could be something small with a trigger or slide property that is overlooked.
With your permission, I'd like to take a look at your project file to investigate what's happening. You can share it publicly here so staff and community members can take a look, or send it to me privately by uploading it here.
This is something that I have faced on multiple projects and I have used a few different triggers to solve the issue. I received a lot of assistance from the community and support:
I have gone away from using the "Next button disabled when timeline starts" as a stand-alone trigger since Next will be hidden every time a learner revisits the slide. I want it hidden only the first visit so I add On Condition......[if all tabs weren't visited]
1. You can use a variable for each tab visit defaulted to false. Change tabVisited to True when clicked. I created VisitedTabTotal to equal True when all the other tabsVisited = True.
Use the trigger Next button hidden when timeline starts On Condition VisitedTabTotal Equal to False. This will hide at timeline start for the first time only. Second time through this will be ignored since VisitedTabTotal will be True.
Add trigger Change State of Next to Normal when VisitedTabTotal == True. This will display Next button when all tabs are visited.
2. If you don't want to use variables, I created a Completed State (you can also use Visited) for each tab.
I Changed State of Next buton to Hidden When timeline starts If [Tab 1 is not equal to Completed and Tab 2 is not equal to Completed,......]
Add trigger Change state of Next button to Normal When State All of [tab 1, tab 2., .....} Are Completed.
Hiding the Next button at timeline start Using the If not equal to a visited/completed state has worked the best for me so far. It hides it on initial slide view but displays on subsequent visits.
I responded as a part of your case as well, that our team is investigating an issue where the Next Button returns to a disabled state when revisiting slide and the slide properties are set to Resume Saved state. We'll keep you posted on that issue here and in your case too - and I hope Mike's idea helps you workaround it in the meantime!
Good to know about the disabled state. I don't like to use the disabled state since it's hardly noticeable and I could see the user clicking on it in frustration. I use the hidden state so that there's no doubt you can't advance.
I have some of my slides set to Resume Saved state along with Next button initially hidden (with condition). I haven't run into a problem with my current setup but I did have an earlier issue where a trigger wasn't working correctly when I had a trigger set to change Next to Normal if tabs were all Visited. I'd go back to the slide and the Next would be hidden again (even though the tab states were all Visited). Sounds like it might be a part of that issue.
We've consulted with our product team on the behavior where the Next button returns to disabled when revisiting the first slide, and now I have some answers for you.
After careful review, we determined it to be by design based on the navigation features. For next steps, we recommend the settings outlined here.
We'd love to hear your thoughts around this setup, and do let us know if you need a hand!
Thanks for following up on this but I don't believe the link that you shared applies here. I do like the Restrict Navigation feature that was implemented July of 2017.
What Prita and I were experiencing was an issue where we wanted the user to have to click on all of the tabs contained in the slide before proceeding. The Restrict option will allow the user to advance once the timeline ends.
We both figured out a solution to force the user to click on all tabs before proceeding. The issue was this was a one-time fix since when the user revisited the slide they had to click on all of the tabs again prior to Next being enabled. I fixed this issue by using variables or creating multiple shapes and changing their state to Complete whenever the user clicked on a corresponding tab. The Next would only be disabled if all of those shapes were NOT complete which would only be on the first go-through.
12 Replies
Hi Prita,
It could be something small with a trigger or slide property that is overlooked.
With your permission, I'd like to take a look at your project file to investigate what's happening. You can share it publicly here so staff and community members can take a look, or send it to me privately by uploading it here.
I’ll delete it when I’m done troubleshooting.
Hi Ashley,
Thanks for your response.
Since it is a regulated course, I would be comfortable sharing it privately with you.
Regards,
Prita
I have uploaded it. Thanks.
looking forward to your support
This is something that I have faced on multiple projects and I have used a few different triggers to solve the issue. I received a lot of assistance from the community and support:
https://community.articulate.com/discussions/articulate-storyline/trigger-condition-hide-object-on-tab-click
https://community.articulate.com/discussions/articulate-storyline/show-layer-after-variables-met
https://community.articulate.com/discussions/articulate-storyline/no-skip-ahead-first-time-then-free-to-skip-ahead-after-complete
https://community.articulate.com/articles/articulate-storyline-reset-slide-when-revisiting
I have gone away from using the "Next button disabled when timeline starts" as a stand-alone trigger since Next will be hidden every time a learner revisits the slide. I want it hidden only the first visit so I add On Condition......[if all tabs weren't visited]
1. You can use a variable for each tab visit defaulted to false. Change tabVisited to True when clicked. I created VisitedTabTotal to equal True when all the other tabsVisited = True.
Use the trigger Next button hidden when timeline starts On Condition VisitedTabTotal Equal to False. This will hide at timeline start for the first time only. Second time through this will be ignored since VisitedTabTotal will be True.
Add trigger Change State of Next to Normal when VisitedTabTotal == True. This will display Next button when all tabs are visited.
2. If you don't want to use variables, I created a Completed State (you can also use Visited) for each tab.
I Changed State of Next buton to Hidden When timeline starts If [Tab 1 is not equal to Completed and Tab 2 is not equal to Completed,......]
Add trigger Change state of Next button to Normal When State All of [tab 1, tab 2., .....} Are Completed.
********************************************************************************
Hiding the Next button at timeline start Using the If not equal to a visited/completed state has worked the best for me so far. It hides it on initial slide view but displays on subsequent visits.
Mike
Hi Mike,
This is great! I am trying this out right away! Thank you so much :) If this works for me, a lot of my review comments will be resolved :D
Prita
Hi Prita,
I responded as a part of your case as well, that our team is investigating an issue where the Next Button returns to a disabled state when revisiting slide and the slide properties are set to Resume Saved state. We'll keep you posted on that issue here and in your case too - and I hope Mike's idea helps you workaround it in the meantime!
Good to know about the disabled state. I don't like to use the disabled state since it's hardly noticeable and I could see the user clicking on it in frustration. I use the hidden state so that there's no doubt you can't advance.
I have some of my slides set to Resume Saved state along with Next button initially hidden (with condition). I haven't run into a problem with my current setup but I did have an earlier issue where a trigger wasn't working correctly when I had a trigger set to change Next to Normal if tabs were all Visited. I'd go back to the slide and the Next would be hidden again (even though the tab states were all Visited). Sounds like it might be a part of that issue.
Hi Ashley,
I received your email. And I did try Mike's method - it worked perfectly :D Thanks Mike.
Thanks for all the support, dear friends!
Prita,
Great news! Glad it all worked out and that I was able to pay it forward after working through all of my issues.
Mike
Hi there, Prita and Mike!
We've consulted with our product team on the behavior where the Next button returns to disabled when revisiting the first slide, and now I have some answers for you.
After careful review, we determined it to be by design based on the navigation features. For next steps, we recommend the settings outlined here.
We'd love to hear your thoughts around this setup, and do let us know if you need a hand!
Katie,
Thanks for following up on this but I don't believe the link that you shared applies here. I do like the Restrict Navigation feature that was implemented July of 2017.
What Prita and I were experiencing was an issue where we wanted the user to have to click on all of the tabs contained in the slide before proceeding. The Restrict option will allow the user to advance once the timeline ends.
We both figured out a solution to force the user to click on all tabs before proceeding. The issue was this was a one-time fix since when the user revisited the slide they had to click on all of the tabs again prior to Next being enabled. I fixed this issue by using variables or creating multiple shapes and changing their state to Complete whenever the user clicked on a corresponding tab. The Next would only be disabled if all of those shapes were NOT complete which would only be on the first go-through.
Mike
Thanks Katie. Really appreciate your follow up on this. But yes, as Mike mentioned, this design feature is different to what we were facing.
This discussion is closed. You can start a new discussion or contact Articulate Support.