Forum Discussion

KirstenSmith-5b's avatar
KirstenSmith-5b
Community Member
3 years ago

Assistance with Results Testing

I could use some advice on an assessment I built in Storyline.

There are three layers on the Results slide: Success, Failure, and Failure 2nd

  • Success should appear when the learner passes the assessment. From this layer, they can click a button to review any questions they answered incorrectly or exit the course.
  • Failure should appear the first and second time the learner fails the course. On this layer, they can click the Try Again button on the Results slide to attempt the assessment up to two more times.
  • Failure 2nd should appear when the two “Try Again” attempts resulted in failure. On this layer, the learner can review their incorrect answers and exit the course.

I created a variable called RetryMe (set to 0), and a trigger to the variable that increases RetryMe by 1 each time the learner clicks the Try Again button. I also added a trigger that changes the state of Try Me to Hidden when the timeline starts if RetryMe is >/= 2.

My problem is this: when I test the course and intentionally fail the assessment, I continue to land on the Failure slide and can continue to click the Try Again button. The button’s state does not change to hidden and the Failure 2nd layer does not open after clicking Try Again two times.  

Image 1 displays my timeline triggers. Image 2 displays my object triggers. I know I must be missing something, but the answer eludes me.

Any suggestions?

 

  • Your button trigger to adjust the value of the RetryMe variable will set that value to 1. That means the value will always = 1 after the user clicks the button. 

    Since you want to count all attempts, that trigger should add 1 to that value. In the Trigger Wizard, click "Set" to find the "Add" option. You should end up with something like this:

    • KirstenSmith-5b's avatar
      KirstenSmith-5b
      Community Member

      Thank you! I don't know how I missed that. It's always the obvious fixes that are the least obvious when you stare at something as long as I stared at my variables. :)

      • JudyNollet's avatar
        JudyNollet
        Super Hero

        Yeah, it's always hard to edit one's own stuff (programming or writing).  :-)

        For troubleshooting that involves variables, it's always a good idea to add a text box to the slide that shows the variable reference. Then you can see whether or not the variable is changing as expected. Because those simple mistakes in the trigger are all-too-easy to make...