I have a form with two rich text fields on it. The form has two record actions that trigger when one of the two fields “has changed”. I.e., the first rule triggers when the first field changes and the second rule triggers when the second field changes.
My problem is that both of these rules trigger every time the form is saved regardless of the text in either field being changed. For example, if I have made no changes at all and click “save” both rules trigger.
What might I be doing wrong? Does the “has changed” condition not work for rich text fields?
Not really helpful, but I can confirm this behavior. A record rule applied to a Rich Text field with the condition ‘has changed’, fires every form submission.
Interestingly, a Short Text field behaves as expected with just the one condition Short Text Field ‘has Changed’, but adding another condition seems to break it.
Both of these behaviors were tested in a Next Gen App as well as a Classic Builder App.
Edit:
It seems more nuanced than I thought.
I was testing if the record rule ran by changing a Y/N field. That’s where I ran into the behavior where it seemed to break by adding another condition (If Y/N = Y AND RFT has Changed, Set Y/N to N (and the opposite)). I noticed in testing that the Y/N WOULD change if the current condition was Y, but not if the current condition was N.
So, I switched my indicator to be a Date Time Stamp.
Confirming the Record Rule runs for each form submission whether the RTF has changed or not. And I found that a similar rule with a Short Text field behaved the similarly. It did not run on each submission. It respected the Conditions that needed to be met. But it did NOT update the Y/N when the Y/N value was N.
The additional testing was done only in a Classic Builder App