You have triggers that run when a checkbox is selected. That means you also need triggers to undo those actions, and those need to run when the checkbox is deselected.
Yes, that can get cumbersome. That's why a "select multiple options" interaction is most often programmed with a button to indicate the user is ready to submit their answer. Then the subsequent actions are done based on that button being clicked.
Yes, it still works with a "submit" button. Whatever you're doing when the user is clicking each checkbox can, instead, be done when the user submits their answer.
Note that those triggers would need conditions based on what checkboxes are selected. So, for example, a trigger might adjust a T/F variable called "Functional_Expertise" to True ifthe "Functional expertise" checkbox is in the Selected state.
3 Replies
You have triggers that run when a checkbox is selected. That means you also need triggers to undo those actions, and those need to run when the checkbox is deselected.
Yes, that can get cumbersome. That's why a "select multiple options" interaction is most often programmed with a button to indicate the user is ready to submit their answer. Then the subsequent actions are done based on that button being clicked.
I really appreciate your quick response!
Since this is a self-reflection e-learning, the answers need to be recorded and then shown on the final slide to the learner.
Does it still work with a "submit" button
Yes, it still works with a "submit" button. Whatever you're doing when the user is clicking each checkbox can, instead, be done when the user submits their answer.
Note that those triggers would need conditions based on what checkboxes are selected. So, for example, a trigger might adjust a T/F variable called "Functional_Expertise" to True if the "Functional expertise" checkbox is in the Selected state.
Here's more info about conditions:
https://community.articulate.com/series/articulate-storyline-360/articles/articulate-storyline-360-user-guide-how-to-work-with-triggers#conditions