2

We are trying to create a workflow that each time one of the three events below happens it will send an email to a particular user. Now the workflow works, besides one major flaw. In order to use ISCHANGED, evaluate rule has to be set to, "created, and everytime it's edited" which is now firing the workflow even if something not included in the formula has changed. Any suggestions on correcting this?

Formula:

Account.RecordTypeId="012A0000000hEaT"&&
ISCHANGED(Email)||
ISCHANGED(RecordTypeId) ||
CONTAINS(Title,"FORMER")
0
5

It's probably continually firing because the title contains "FORMER"

Try the following:

Account.RecordTypeId="012A0000000hEaT"&& 
(
ISCHANGED(Email) || 
ISCHANGED(RecordTypeId) || 
(ISCHANGED(Title) && CONTAINS(Title,"FORMER"))
)

Edit: See the comment from @DerekF below for additional insight into why you experienced that workflow behavior.

3
  • 2
    Deduction supports your conclusion. I think it's worth noting that a significant portion of OP's issue is likely to be that of precedence of operations. Your addition of ISCHANGED(Title) is important in this context, but I'd argue that the extra parenthesis around the parts of the expression being OR'd together is at least equally as important here (if not more so).
    – Derek F
    Mar 11 '16 at 19:37
  • @DerekF Agreed on all points.
    – jonnybro
    Mar 11 '16 at 19:42
  • @DerekF thank you!
    – c.hunter90
    Mar 11 '16 at 21:28

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.