Forum Discussion
Problems with copied & changed trigger with OR conditions
For a long time, I have been experiencing problems when copying and modifying triggers with OR conditions.
When I copy and modify a trigger that contains OR conditions, then delete or change some of the conditions, the trigger is always executed — even when the conditions are not met.
I know how to fix it by deleting the trigger and creating a new one from scratch. I also know some workarounds, such as temporarily changing OR conditions to AND conditions, copying the trigger, and then changing the AND conditions back to OR.
This bug was reported and could already be replicated 3 years ago, but it still has not been resolved. The attached link is from just half an hour ago.
What I would like to know is whether other people are experiencing the same problem, or if it is common practice/knowledge that triggers with OR conditions should not be copied and modified.
4 Replies
I expect they're one of the less used features of Storyline, speaking not just from my own experience but from other designers/developers I've worked with over the years, so I wouldn't be surprised if conditional triggers aren't iron-clad. Above a certain level of complexity, JavaScript definitely seems to be clearer and has fewer limitations.
Agree with AndrewBlemings- I find I use javascript more and more for even the most simple things now.
Also Articulate used to (but may no longer) prioritise bugs based on if a work around existed or not.
Thanks for your replies. I only use JavaScript when I can't solve something with triggers, and I use triggers for the most complicated calculations and decisions. So that's quite different from how you do it :-)
Nevertheless, I think that copy/pasting a very simple trigger and modifying it should not result in a corrupt trigger that does not do what it is supposed to do.
Maybe Storyline staff could react on this post? Is there any idea when this bug is going to be solved?Hi UPlearning,
Thanks for sharing the additional context and details around this behavior. I can understand why this would be frustrating, especially when a copied trigger ends up behaving differently after only minor condition changes.
I did some testing on my end and wasn’t able to reproduce the issue in a brand-new Storyline file. However, I can see the behavior you’re describing in the example you shared, so I’d like to follow up with our engineering team to take a closer look.
You mentioned this was previously reported and reproducible around 3 years ago. If you still have the link to that older discussion or report, could you share it here? That would be really helpful so I can reference the earlier findings and connect the investigations together more easily.
