Problem with Conditions on Triggers in SL2
Sep 24, 2014
Hello,
I have recently upgraded SL1 to SL2 and noticed a bug with one of my custom templates.
The bug is localized on the Conditions you can put on a trigger.
Explanations:
My template uses a certain number of markers to describe a picture (notably a machine).
The trainee has to visit all the markers before to be able to go NEXT SLIDE.
If the trainee click on the NEXT button before visiting everything, a layer is showed with a girl saying but "you have to visit all the markers":
The Condition is based on a specific object: an ARROW.
The ARROW is initially HIDDEN when the slide is viewed and thanks to another trigger (that works perfectly) change the state of this arrow to Normal when all markers are visited.
Then I have two triggers using conditions on the state of this arrow to either:
- Show layer "INFO" if all markers have not been visited:
Then I show the layer if the ARROW is still hidden (so not all of the markers have been visited)
- Jump to next slide if all markers have been visited:
The problem is that it does not work anymore with Storyline 2... It worked perfectly with SL1.
Even more, the trigger "Show Layer" Info appears when the arrow is Normal and I cannot go to next slide.
But I can go to next slide even if the Arrow is still hidden... So the contrary. I tried to change the conditions by the contrary but the layer "INFO" is never shown.
It is strange!
Can you look at or tell me if I did something wrong? My internship has also the same problem. I think there is something not working properly with the conditions on triggers.
I have put my Storyline file in this post as support.
Thanks in advance for your clarifications
Regards
Julien
15 Replies
Hello Julien,
I can't explain why the trigger conditions aren't working for you in SL2, which is especially puzzling due to you saying that they did work in SL1. I would suggest that you file a bug report with the Articulate team.
With that being said, I usually prefer to use variables to accomplish what you're trying to do. I modified your .story file, removed the trigger conditions based on state changes and created a T/F variable called AllVisited with default value of False.
If a learner clicks next and the variable value is False, show the info layer. If the state of all markers is 'visited' the variable adjusts to True, which allows the Next button to work.
Hello Brian,
Yes thank you it also work with Variables indeed.
I used the state change because I wanted to point the Arrow out to show that now they can go next slide.
But if your team can look at this bug, it can't be great also.
Thanks in advance
Regards
Julien, I would suggest that you open a support ticket with the Articulate team and attach your .story file.
If you take a look at the modified file I shared your animation effects still work on your next button arrow, even with using variables for your trigger condition.
Hi Julien,
Thanks for sharing your file here - it's definitely behaving oddly, as prior to all the items being visited - I can use the next button, but once the down arrow appears - and then I try to use the next button, it shows me the layer reminding me to click everything.
Do you have the original SL1 back up version as well? I'd like to take a look at everything and try upgrading it myself.
Hi Ashley,
I only used SL2 now so I don't have only a module to share with you to see this problem.
You will find enclosed my .STORY file used as base to build my storyline templates. There are 2 templates using these triggers.
Look within the scene 1, I think it is the slide 5 or 6 (you will recognize).
Thanks a lot for your help!
Regards
Julien
Most definitely a bug, it is validating the states of the down arrow wrong, oddly enough if you switch the states round in the conditions (e,g switch normal to hidden and vice versa. It works as expected
Thank you for your feedback.
The problem is that I have to modify the template and share it to all my teams worldwide.
If this bug is fixed in a minor update, I can't deal by modifying Normal to Hidden, I think I will either use the Next button "Disabled" or the variable True/False.
Julien
Hi Julien,
Thanks for sharing the new template file - as it looks like this was an SL1 file so I was able to see the backup that's created and how that one worked and then recreate the behavior in a new file.
I'll be sharing this with our QA team for additional review. I'll post any additional information here when it's available.
We've encountered the same problem. Are there any updates about this bug?
Hi Matt and welcome to E-Learning Heroes!
This issue has been reported to our QA Team and there is no update to share at this time. It is attached to the issue and this thread will be updated when appropriate, so be sure to subscribe
I have the same experience.
Not only that, I noticed too that using the trigger When Content Opens for a marker to play an audio is no longer working. This was possible in SL1.
Hi,
Was there ever a solution to this problem? We've just upgraded a project form SL1 to SL2 and now the NEXT triggers that are conditional on object state seem to be inverted!
Hi Richard!
This issue is still in the hands of our QA Team and I have no update to provide at this time.
Hi all,
I wanted to provide an update here, as Storyline 2 Update 8 was just released, and included a number of fixes which you can see in the release notes available here. The item you all may be particularly interested in is how it fixed the issue where trigger conditions wouldn't work properly when upgrading a project from Storyline 1 to Storyline 2. You can download the latest update here, and after downloading and installing the latest update you’ll want to republish any existing content to ensure that the updates and fixes are applied.
Let us know if you have any questions, either here or by reaching out to our Support Engineers directly.
Thanks for the update Christie, great news!
This discussion is closed. You can start a new discussion or contact Articulate Support.