We have noticed that in the latest versions of SL, when adding triggers with "WHEN STATE" "IS NOT" for a state which is going to be changed doesn't work. However same trigger with "WHEN STATE" "IS" works fine.
We have a possible bug logged where the trigger to change the state of "Object2" when the state of "Object1" (or a combination of objects in a condition) changes is not working when using "Is Not Normal" condition.
As a workaround, you can specify the object's state (instead of "Not normal").
We'll come back to this discussion as soon as we have news to share!
3 Replies
Hi, Info.
Thank you for reaching out!
We have a possible bug logged where the trigger to change the state of "Object2" when the state of "Object1" (or a combination of objects in a condition) changes is not working when using "Is Not Normal" condition.
As a workaround, you can specify the object's state (instead of "Not normal").
We'll come back to this discussion as soon as we have news to share!
Thanx Maria for reply. For now we have fixed the problem by specifying the STATE. I hope SL works on the issue and we get an update soon.
Thanx,
Tazeem
I brought this up about 4 months ago.
IS vs. IS NOT Trigger Bug?