Automated checklist feature within Articulate?

Dear Friends@Articulate,

Is there a way to have an automated checklist feature within Articulate?

i.e. for the ticks to appear by itself AFTER all slides within a scene has been clicked by a learner. Regardless of sequence.

Attached the storyline file where I mimic this with just a static pic. No variable /condition tied behind it. Also attached a picture of ideal End State where all scenes have been clicked upon and all green ticks showing. 

Thanks everyone! :)

14 Replies
Benedict Chia

Hi Leslie, 

I noticed that your method uses variables while Vu's simply uses the "visited" state property of buttons. While his solution suffices for now, but my original question remains... "i.e. for the ticks to appear by itself AFTER all slides within a scene has been clicked by a learner. Regardless of sequence." was that why you used variables? 

For some reason, I could not get your method to work on my file. Still a newbie .. :p

Walt Hamilton

Benedict,

I didn't look at any of the files, I just read the posts here, but I'd like to share concerning the "states" versus "variables" issue.

In my experience, variables work much more closely to the manner most people predict they will, for several reasons.

1. Many people do not create triggers correctly using states. They use "When states are .." as the action to initiate the trigger, but that method is highly dependent on timing, and is not always predictable. Using When variable = XXX makes most people stop to think "When do I want this to happen?", which gives better results.

2. "Visited" is a state that works well on the page where it resides, but if you navigate away (especially if you go through several pages and branching activities), it tends to get lost, and is not a reliable indicator. A variable never forgets.

3. The activity of the "Visited" state is hardwired, and may contain surprises you can't predict or control. Only you the developer can change variables, while there a lot of activities that can change states without your knowledge or consent.

4. Variables can be changed at other locations. You would use this at the end of the other slides you want the user to view. After they have viewed all the material, the variable would change. (Many new developers make the mistake of changing the variable at the beginning of the material, meaning that the user gets credit for viewing the material when they haven't.) A state can only be changed on the slide where the object is.

Leslie used variables because they are stable, reliable and flexible.

Some people fear variables because they are not part of our everyday life, but they are not that difficult. Think of a variable as a check-off list to help a forgetful child remember if she has done her chores today. It is always in a know location, it can be changed, and it always remembers the last thing you told it.

Benedict Chia

Hi Walt,

Thanks for taking the time to give me such a clear explanation. Indeed, when I tested my module, I found ways to "beat" the system as using the visited state method is not as stable as using variables. Alas, for a newbie, this was the best I can muster for now. Deadline to deliver a product in a week's time. So, I am still thankful to @Vu for teaching me about the "states" method.

I agree that Variables is the way to go, hence will invest time to understand it a bit more. Grateful to Heroes like you and @Leslie who are willing to share and guide us.

PS+ love this community!

Benedict Chia

Hi Leslie,

Indeed, its fantastic. So, I'm convinced on variables... and found some useful tutorials online. Would like to share them with other newbies out there.

PS+ I haven't quite figured everything out yet. But in time, I will. Look fwd to being "Walt" in near future :)

Rebecca McGee

Hi All, I'm using this strategy but for some reason my state is not changing.  If I could get some feedback I would really be grateful! It may be due to the slide type I've chosen.  I placed a button on a Pick One quiz template and gave it the following functionality:

1. submit results of freeform interaction to LMS,
2. take learner directly to next slide without making them see correct or incorrect results (and I deleted them)
3. Change the variable Video1 to True
4. Change the state of Rectangle 1 on slide 1 to “Complete” state if variable Video1 is true

Walt Hamilton

1. I'm no expert, but I think the Submit trigger only submits the quiz results to SL, not the LMS. I think submitting is a necessary step, but I think there is more to it.

2 and 3. SL will try to execute this list of triggers, starting at the top and going down the list. When it jumps to the next slide, it will forget the other triggers.  The jump should be on the bottom of the list.

4. When the variable is changed this trigger functions