Triggers in Storyline 2 are not working
Nov 04, 2015
Hello! I am creating a branching activity in Storyline, and I'm setting up the slides to disable the Next button until a certain point. On some slides, it is until the timeline ends, and on others it is until the user interacts with all pieces. My issue is that I have gotten this to work on all slides except one. It is the landing page for the branching activities. On this slide, I have tried to set it up so that the next button is enabled when the timeline ends, when the user has interacted with all five activities (they have a state visited), and based on a text box that also appears (changes state) once they have interacted with the same activities. I'm including an image of one of these configurations. It's for the 3rd of my options that I tried (text box), and I've highlighted the trigger in question. The interesting thing is that when I had the state set to turn to normal based on the timeline ending, if I manually changed the timeline and let it complete, it worked! I'm stumped! Please help!
6 Replies
My first inclination is to say that that trigger will work better if it is attached to the next button.
My second inclination is to say that basing a trigger on a state seems to work best if it is in the condition part of the trigger, and not in the when part.
My best inclination is to suggest that you take the trigger and conditions that change the state of the text box, and attach a copy of them to the next box. As I read your triggers, you want to set the state of the text box when certain conditions are met, and then change the state of the next button if those same conditions are met. The easy way to make that work is to copy the change state trigger to the next button.
I actually already tried copying that trigger (for the text box) and applying it to the next button. Still didn't work! Any other ideas?
I would try change the state of the next button WHEN the user does something, or the timeline reaches some point IF the state of the boxes is ...
I don't trust basing actions on when state is, and judging from the posters here that have trouble with it, maybe you shouldn't either. Base it on a definite action, and use if state is as a condition.
Otherwise, post your .story file (or part of it) here, and maybe someone can suggest some ideas.
Hi, Katie and welcome to the community! I agree with Walt; it's always easier for members of the community to chime in with their advice and suggestion if you are able to share your file and show how things are currently set.
If you would like to share, please use the ADD ATTACHMENT button in the bottom left of the reply box and browse from there. I also wanted to note, if you reply via email, your attachment will not come through to be accessible here in the thread. :)
Hi Walt and Christie, I ultimately decided to remove that feature due to timelines for the project. Unfortunately, I would have had to share pretty much the entire training for testing. I think, as Walt said, it is best that I didn't base that on the state is for that particular slide. I considered making the button normal after a specific on screen action, as suggested, but that would have defeated the purpose of forcing the user to complete all tasks before moving on.
Many thanks for sharing an update, Katie, and if there is anything more we can do to be of assistance, please don't hesitate to ask! :)
This discussion is closed. You can start a new discussion or contact Articulate Support.