Forum Discussion
My state change triggers are now broken?
I have created a practice resource that I am using to teach colleagues about Articulate. My main issue is on Question 3. I have created a make shift dropdown question.
Within the question I get my users to rank Pizza chains from 1 to 3.
Once all of the brands have a rank, the submit button needs to change to 'Normal'. I have added a variable to each of the options, so once it is not normal, it should add 1 to the page total.
The 'not normal' trigger doesn't seem to work anymore, I have also had this issue with older resources I have been asked to update.
(They previously worked as expected)
Here is the resource published on review, it works exactly how I intended. Now as I am recreating the resource in the exactly the same way for a screen recording, the trigger has stopped working. And I can't work out why as I haven't done anything differently!
Is anybody else having similar issues with 'not normal' states not triggering things? It has only occurred after the latest update.
Thanks in advance.
4 Replies
Hi, Paul, and welcome to E-Learning Heroes! ✨
If you have the original .story file (the one published to Review 360), I'd be curious to see how it was set up.
My suggestion is to avoid using the Normal state to check when it's "Not Normal," as the built-in states have their own logic, which might be affecting your triggers.
I'd recommend creating another state (let's call it Empty) and using that state in your triggers instead of Normal.
Take a look at the attached file, and let me know if it works for you.
Thanks for the fix, this will make things easier for sure :)
My main concern is why it has stopped working? The last year or so that I've been doing it I've not had any issues until now.
We haven't made any changes to the triggers, so it's hard to pinpoint what affected the triggers related to states in your project. If you see this is multiple projects, I'd like our Support Engineers to continue troubleshooting with you. You can connect with their team using a support case.
The built-in states are like all of us - they think they are perfectly normal. Therefore they do not respond correctly when "is not normal" is used in a condition.
