Forum Discussion
Using Variables and Triggers in a knowledge check with a result slide not working
Hello everyone,
I have tried searching for answers to a problem I am having with a results slide but most of what I am finding is old stuff with images of trigger panels from old versions of Storyline.
I've built a knowledge check Jeopardy game with a main slide that has 5 categories and 5 questions in each category. When the learner selects a button (category for 100) the trigger jumps to the slide. The learner answers the question and correct or incorrect layers return to the main slide adding or subtracting 100 from their score. The state of the button changes color to a selected state.
If I have a trigger to go to the results slides when all buttons are selected the last button selected skips to the results slide without the learner having to answer the last question.
I set a true/false variable for each question to work around this. If question 100 is true, and question 200 and so on equals a value of true show layer. This layer has a trigger to jump to slide Results when the timeline starts on this layer. When I test the entire project, answering all 25 questions I don't go to the results slide.
At first I thought it was the order of triggers on a question slide. I have Set Q2 100 to value true when the user clicks submit at the top (see attached for triggers). I've added references to my slides to make sure this is working.
I feel like I'm missing something. Any suggestions? I have included 2 screenshots of the triggers from the main slide and a question slide. I would prefer to not share the entire story as it is rather large. I'll be happy to share screenshots if you need to see something specific. Thank you for your time, and any help you can provide.
Hi Annette, 👋
Thanks so much for reaching out! Sorry to hear you've run into that snag with your Results Slide.
I understand you do not want to share your project file in this thread. Would you be willing to share a copy of your project file in private by opening a support case so we can take a closer look at what's happening? We'll delete it when we're done testing!
Hope you're having a great start to 2024! 🎉
- Annette-WestCommunity Member
- JudyNolletSuper Hero
There are problems with the "when" in some of the triggers.
This post has a file that demonstrates how to use an invisible layer to ensure that the needed trigger(s) run when a user returns to a slide: https://community.articulate.com/discussions/articulate-storyline/tip-the-incredible-power-of-invisible-layers
- Annette-WestCommunity Member
Hi Judy,
Thank you for sharing the file from the community. I don't see how this helps with my project. If I remove the "when" I'm back to where I was - it jumps to the layer then results slide without having to answer the last question because will have selected states.
Maybe I'm just more confused now.
thanks,
Annette
- JudyNolletSuper Hero
The point is to use the invisible layer to have a "when" that happens every time the user returns to the main slide.
- Add a "progress" layer without any objects and with the Slide Layer Properties set to "Reset to Initial State."
- Add a trigger that shows the "progress" layer when the base timeline starts. The layer will remain open, and its timeline will restart every time the user revisits the slide.
- Add a trigger on the "progress" layer that jumps to the Results slide when the layer's timeline starts with the conditions that all of the variables are True.
When the user returns to the main slide, the trigger on the "progress" layer will check the conditions when its timeline restarts. And it will send the user to the Results slide only after they have answered all of the questions (i.e., if all of the variables are True).
- Annette-WestCommunity Member
- JudyNolletSuper Hero
It's hard to troubleshoot without seeing the file. The triggers look okay, so my best guess is that the Slide Layer Properties don't have "Reset to initial state" for "When revisiting."
Here's the User Guide info about adjusting Slide Layer Properties: Slide Layers in Storyline 360 - E-Learning Heroes (articulate.com)
If the progress layer uses "Reset to initial state," then I suggest you upload a copy of the .story file. Here are the best practices for uploading a .story file:
- Only include slides that are involved in the problem.
- Be sure all objects, layers, motion paths, and variables have meaningful names.
- If there is proprietary content, replace or delete it. For example, replace proprietary text with ipsum lorem text.
- Annette-WestCommunity Member
I removed content but you should be able to move around the same. Normally the user would pick a character and enter their name. I removed content for the other character. Only Andrew is available. Hope this helps you see what is happening or not happening with the results slide.
thanks so much,
- JudyNolletSuper Hero
The variables listed in the conditions are all True after the questions have been answered. The progress layer is replaying every time the user returns to the main slide. Yet the trigger still doesn't work. I can't figure out why. I suggest you contact the Articulate support staff directly. You can do that here: Contact Support for Help with Any Articulate E-Learning Course Development Software
FYI:
- The bad news is that those triggers to change the buttons to Selected aren't running, because you have them after the "Jump to slide __" triggers. (A trigger can't run if the program has already left the slide.)
- The good news is that you don't need them. An object with a Normal state and Selected state will automatically toggle between those states when clicked.
- For this type of slide, I'd give the buttons a Visited state instead of Selected. An object with a Normal state and Visited state will automatically switch to Visited when clicked. And it will remain in the Visited state (unless a trigger is used to change it).
- Annette-WestCommunity Member
Hi Judy,
Changing states to Visited instead of Selected is an easy fix. TIme consuming, but easily done. I created this in the Storyline 360 Beta thinking this would be the format going forward for 2024. As you suggested, I will submit this to Support. We may have discovered a bug in the software.
I appreciate your time and help with this project, Thank You!
Annette
First, I appreciate you, Judy, for all your valuable help here!
Thanks for reporting this in a support case as well, Annette! You're in good hands with Johnrey. Let's continue the conversation in your support case to keep all the information in one place.
Have a great rest of your day! 🙂