Forum Discussion
Making state persistent on menu items?
Setting the menu slide to retain saved state on revisit may help you. But if you are then using those visited states to initiate another trigger, that won't work. Visited states are designed to work well to indicate visiting layers or objects on the same slide, but less useful if the learner goes to other slides.
For more ideas, check the sample at this post:
https://community.articulate.com/discussions/articulate-storyline/free-sample-restricted-and-free-random-navigation-using-variables-and-triggers
It has four buttons that take the learner to different slides, and when they are all visited, a button appears that can have any trigger on it you want. In the restricted navigation, the four buttons appear in order, only after the previous one is visited. In the Mixed mode, the four buttons all appear at the beginning, and can be clicked in any order, but all must be visited before advancing. In free navigation, all buttons and the Next button appear at the beginning, and can be visited in any order.