Using States with Check Boxes

Aug 24, 2020

I'm fairly new to Articulate and am struggling to work out what I am doing wrong with some content I am developing in Storyline 360.  I have a content page with a list of contents with check box icons next to them.  I have created triggers that state when a user clicks on the content title to take them to another scene the check box state should change to visited (a checkbox icon with a tick).  When I tested it I expected the check box to have a tick in it when I return to the content page but it isn't working.  Any help on what I am doing wrong would be appreciated. 

4 Replies
Judy Nollet

Hi, Sue,

It's hard to troubleshoot without seeing the Storyline file. Best guess: there's a problem with the trigger order. So be sure the trigger to change the state of the checkbox comes before the trigger to jump to the designated scene. 

If that's not the problem, then you'll need to upload the file for troubleshooting.

Garth Yorko

Here is something that might work for you.

First I created custom states for the Checkbox.  I also created True/False variables for each scene (Topic_1_Complete, etc.)

Think about when you want the state change.  I think you want it when the Topic is completed.  Each topic has two slides,  I adjusted the variable to True when the timeline starts on the second slide of each topic.  If the learner returns to the Main Menu without completing the topic, the checkbox is empty.  If the learner completes the topic, the checkbox is complete

I added a user prompt to show when all three variables are equal to True so that the learner knows what to do next.

Here is the sample:

https://360.articulate.com/review/content/eb5c2f1e-8504-4b27-9b77-9f1d2c2ca582/review

The source file is attached

Walt Hamilton

Garth's option is probably your best bet.

There are two potential problems with your current attempt. An object that has a Visited state will automatically turn to the Visited state when clicked. By creating a trigger to do that, you run a huge risk of creating conflict with the built-in magic. Actions that are strange, but seldom wonderful can result.

Also, when you revisit a slide, you will lose state changes unless you set the slide to Return to saved state on Revisit.

But, if you are going to a different scene (actual different scene, not just changing to a different slide), you may still lose that state. That's why Garth's approach is considered state-of-the-art.

Two things to remember about Garth's approach:

1. You must set the menu slide to Return to initial state on Revisit, otherwise the timeline won't start, and the triggers won't work.

2. You cannot name the states Visited, otherwise you will run into the conflict I mentioned earlier. That's why most of us use Complete for a state name.

This discussion is closed. You can start a new discussion or contact Articulate Support.