That’s exactly what I wrote 2 posts prior lmao
No you didn’t :-p you said
Status is
Status is a state used for the default ticket and order flow :-p
1 Like
uhh ok, lol whatever trevor… 
Speak to the hand cos the face aint listening…
Speak to the elbow you aint worth no extetion…
That constraint didn’t work
If you see status just always be carefull.
The switch user setup needs to intervene on it in some cases due to the nature of it but must be done with caution.
Show where you making that state…
My bad, typo
Story of my life today if u see all the posts ive made… Worst one was me changing the actions in a rule… and it just wouldn’t fire…
I was editing the wrong rule…
Then I couldn’t get the actions to work…
I was editing the wrong Action…
You couldn’t make it up
1 Like
That’s one of the reasons I make generic actions and reuse. You then only need to go to rule and set the action values all in the rule.
No issues of updating full action or lots of different actions.
One generic action to use for all instances of that action. Easier to see what the rule is doing to if its values are all set in the rule.
1 Like
assigning tags to rules helps as well. You can search with tags.
I need to clean up my till, its full of old rules and actions I don’t use or failed with when I was learning.
I was thinking of creating all actions with [:Brackets] so I wouldn’t have to keep making them
1 Like