Conditional "Next" triggers acting up in branching?
Apr 08, 2014
I'm working on a large and fairly complicated interactive elearning. It has branching; a user clicks one part of a diagram and is directed to a slide and quizzes about that element, and then is directed either back to the diagram (if they have not viewed all parts) or to the next portion of the elearning (if they have viewed all parts).
I'm using true / false variables to track what has been viewed (default being false, trigger set to flip the variable to "true" when the timeline starts on the informational slide).
I made my own "continue" buttons for these quizzes, since I need the "continue" buttons to have fairly specific triggers (jump to slide x if variables 1, 2, 3, 4, 5, and 6 are all true, jump to slide y otherwise) and I did remove some of the stock "continue" buttons automatically generated by the slide master.
The problems I'm having are twofold:
1. I believe it's possible that removing the continue buttons automatically generated by the slide master is, for some reason, causing random "jump to next slide once timeline finishes" triggers to appear. That's the only explanation I can come up with, because these triggers are popping up all over the place and I'm not putting them there. Do I have to copy a spare stock "continue" button and place it on the slide to prevent this? What's going on here?
2. My triggers on my custom "continue" buttons still aren't working 100%. I can't tell if this is because my conditionals are too restrictive--some of them are set to "jump to slide x if variables 1, 2, 3, 4, 5, and 6 are all true, jump to slide y if variables 1 or 2 or 3 or 4 or 5 or 6 are false" and I suppose I don't need the conditional on the second one, but I'm curious if there's a better way I could be setting these up so they're more reliable.
3 Replies
Hi Melissa,
Welcome to the community.
There's some discussion and a great how-to video by Brian Batt on creating custom continue buttons in this thread. I think it may answer your questions and help straighten things out.
HI Rebecca--Yes, I did watch that video, but it doesn't really address the question of why there are random "hide layer when timeline ends" & "jump to next slide when timeline ends" triggers popping up in the feedback slides. I can't figure out if there is any pattern of where or when these triggers are created, but I know that I and no one on the team is creating them. They are definitely coming from Storyline somehow.
Again, I believe this is happening in slides where I have deleted the stock "continue" button but that tutorial doesn't really address what happens or why when you delete the stock continue button from a feedback slide, nor does it say anything about mitigating this problem. I have been going through deleting these triggers by hand over and over again, and it's infuriating and, honestly, a giant waste of time. I'm looking for a rhyme or reason to it so I can just prevent that rather than treating the symptom with this time-sink.
If there's some default I can change or something, or even if I can grab the button from the layout master and put it back on the slide outside of the visible area (as demonstrated in the video) then that would be great as a solution, but I don't want to spend time doing that unless I know that it will actually work and keep the problem under control.
If you have any thoughts on these triggers and how to prevent them in the future, I'd be much obliged.
Hi Melissa,
Sorry you're running into difficulties. It can be extremely frustrating when you have to repeatedly smack Storyline to get it to do what you want.
I see that Brian Batt's resolution won't work for you, since his button on the Feedback masters has the button trigger jumping to the next slide and you need for ""the "continue" buttons to have fairly specific triggers (jump to slide x if variables 1, 2, 3, 4, 5, and 6 are all true, jump to slide y..." I'd thought this could be implemented on specific slides, but was unsuccessful in various attempts to do that when using this Feedback Master method.
Perhaps you can upload your story, or a part of it here, for the community to take a look. I think your troubles ARE all related to your deleting the built-in continue button.You'll note in Brian's video at around 50 seconds he says that Storyline will.always generate a continue button.
I guess my question would be; why do you need to delete it? Can't you just move it offstage, create your own buttons and add the necessary triggers?
Again, perhaps if you can upload something here the community can help you out. Otherwise, perhaps you can submit a support case.
This discussion is closed. You can start a new discussion or contact Articulate Support.