Running 2.2.9.140
When I add a condition in RM (IF THEN - haven't tried simple condition) on changed, I don't get the option 'Done with this condition'.
WORK AROUND: When I change the operator to '=' (or some comparison) to a variable, then add a variable, 'Done with this Condition' appears. I can then change the operator back to changed, and "End of Condition' remains along with the former variable comparison. If I remove the comparison variable 'no selection', 'Done with this Condition' again disappears. However, if I leave the comparison variable and select 'Done with this Condition', the condition is added to the rule properly as (variable) Changed.
I haven't tested to ensure the conditional works as it should. I have a rule which triggers on several different variable changes, I then intend to use condition statements in the rule to take different action based on what variable changed. Not sure how long the 'changed' flag persists after the trigger.
Attached screen shots show the bug sequence and work around to add the conditional.
UPDATE - Tried the conditional, the variable change DOES NOT persist after the trigger in my case, therefore the conditional is never evaluated as TRUE. There may be uses where a variable is changed within a rule, or if called/triggered in another fashion where this may still be a valid conditional, not sure.
I recognize there are other easy ways to work around this, including splitting into separate rules each triggered on the individual variable change, and not critical for my implementation
I also noticed that some of the triggers were disappearing from my rule during my edits within the rule actions. I've had two separate rules this morning where the triggers just disappeared, even though I wasn't editing the triggers. I thought I mistakenly went into the wrong section, until it happened a 2nd and third time. I suspect this is when I deleted conditions within the actions (variable changed as described above) that were the same as conditions within my triggers. However, I haven't gone back to try and recreate the problem.
None of the edits / triggers seemed to break the rule, I just had to go back and add the missing trigger back in.
