Forum Discussion
Storyline- Next button to become available after visiting another slide
The logic of why this doesn't work escapes me. I have one main slides that has buttons taking it to 5 other slides. Each of these return the user to that main slide again. I don't want the user to be able to click Next on the main slide until they have visited each of the 5 other slides. I've set up two triggers on the main slide (in this order):
1. Disable the Next button when the timeline starts
2. Change the state of the Next button to normal when the states of all 5 of my buttons are "Visited".
I can see the state of the Next button change to normal on the main slide when I click the last of the 5 buttons. But when I return to the main slide from that last slide, it has reverted back to disabled again.
I have discovered that if I add a third trigger to the main slide, it works. I put this one between the above 2 so basically, this trigger is cancelling out the first one once all 5 slides have been visited.
2. Change the state of the Next button to enabled when the timeline starts with the following conditions (followed by conditions for all buttons' (AND) state being "visited".
It's almost like that original trigger that I set up as trigger 2 is only applied once... when the last button's state turns to "visited". And then after that, the trigger is ignored when you revisit the slide.
At any rate, I got it to work. I just don't understand why it took that extra trigger.
It could be that your 'revisit' slide option is set to 'reset to initial state' instead of resume saved state?
As soon as you click a button it changes state to visited so your latest trigger when timeline starts with condition of states = visited is the better way to go. I don't like using the built in visited state as the user can see it change as soon as they click the button - I normally create a new state called 'completed' and delete the visited state and use 'completed' in my triggers.