I was wondering if it is possible to create a trigger that will appear if someone tries to click the Next button prior to all requirements being met. For example, if the learner is required to click on a button to review a policy before continuing, I would like to have a message display should they try to click Next prior to reviewing the policy.
Right now I have the slide programmed so that the Next button is disabled when the slide starts unless it was previously visited. I would like to add this trigger so we hopefully get less help tickets from learners who are not reading the instructions on the screen. Any recommendations are greatly appreciated, even if we cannot create this sort of trigger.
I create a layer with a great big colored text box that says in huge letters: "Please review policy". I set the text box to have a fade exit animation, and the layer to have a 5 second timeline and to hide when the timeline finishes.
The next button has a trigger to show the layer if the review button is not visited, and another one to jump to the next slide if it is visited. (Actually, I set a variable if the policy is visited. That way I can set revisit options however I want, and be sure that it won't advance until visited, regardless of other conditions. I use the value of the variable instead of the state.)
Of course, I should add that I have a personal animus against disabled buttons,* so I don't disable the next button. I'm not sure the trigger will work if the button is disabled.
*This problem is one reason I don't like them. The learner doesn't read the instruction, sees a perfectly good looking button, clicks it, and nothing happens. So you get a call that it isn't working. When they click my button, they get a message telling them to complete the interaction. -rant off.
1 Reply
I create a layer with a great big colored text box that says in huge letters: "Please review policy". I set the text box to have a fade exit animation, and the layer to have a 5 second timeline and to hide when the timeline finishes.
The next button has a trigger to show the layer if the review button is not visited, and another one to jump to the next slide if it is visited. (Actually, I set a variable if the policy is visited. That way I can set revisit options however I want, and be sure that it won't advance until visited, regardless of other conditions. I use the value of the variable instead of the state.)
Of course, I should add that I have a personal animus against disabled buttons,* so I don't disable the next button. I'm not sure the trigger will work if the button is disabled.
*This problem is one reason I don't like them. The learner doesn't read the instruction, sees a perfectly good looking button, clicks it, and nothing happens. So you get a call that it isn't working. When they click my button, they get a message telling them to complete the interaction. -rant off.
This discussion is closed. You can start a new discussion or contact Articulate Support.