simple button- getting 'state' correct for LMS

Jun 15, 2020

In order for our users to progress from a lesson created as a RISE SCORM , to an LMS multichoice quiz, we track a quiz result that is a single quiz question in the RISE.

this does cause some confusion with users, as the animated graphic ending the quiz does make it look like they've answered a quiz and got 100%, rather than just said 'yes I agree with a statement'

To change this, I'm creating a simple acknowledgement button in Storyline to be utilised in our RISE authored courses.

essentially the user clicks a button to acknowledge they've completed reading the content.

When exporting the file from RISE, I select the  'track using Storyline block' and set it to the 'button' block I created. 

I tried this logic :

trigger 1

when the state of button 1 is Down

-complete course as Completed/Passed

-shown layer thanks layer

trigger 2

when the user clicks button 1 

-change state of button 1 to Down

 

this doesn't work and I expect it's my triggers and states not working.

for some reason it forces trigger 2 to occur after trigger 1, where I would have thought they need to be the other way around, and I don't seem to be able to change the order. - Any ideas on how to get this working?  

many thanks folks, Theo.

7 Replies
Leslie McKerchie

Hey Theo,

Thanks for contacting us and sharing what you are running into. Based on your description, it does seem that trigger order may be the culprit.

The Order in Which Triggers Are Executed

You mentioned that you are unable to change the order.

With your permission, I'd like to take a look at this sample .story project file to investigate what's happening. You can share it publicly here, or send it to me privately by uploading it here. I'll delete it when I'm done troubleshooting.

Lauren Connelly

Hi Theo!

Thanks for sharing the course too!

It looks like the initial state of the button is Hover. By default, a button should be set to Normal, Hidden, or Disabled. Secondly, the Down state is how an object appears while it's being clicked. If this state exists for an object, it'll automatically display when learners click it. You don't need to create a trigger to invoke it. Instead, I'd recommend using the state Visited.

You'll see that by making these changes, you can now reorder the triggers! I've attached the updated story file to this discussion. Let me know if you have any questions!

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