0

The scenario is, there is a field called 'Expected closing Date' on the opportunity object. When the opportunity owner changes the expected closing date it should go for the approval of his manager. For this, I have written a workflow rule for storing the expected closing date before changing it because when the approver rejects the proposal then it should update for its original date, I have done it in rejection action of approval process(approval process fired by process builder) but it causes the workflow run again. I have set the flag true also in rejection but the user can change the date multiple times. How I can avoid the recursiveness of the workflow rule in this scenario? Any help will be appreciated!

Workflow Rule:

Approval Process

Improve this question

1 Answer 1

Reset to default
1

There is one checkbox called "Re-evaluate Workflow Rules after Field Change" available under field update. Uncheck that checkbox so it won't fire the workflow if the date is changed via approval process rejection action.

Improve this answer
2
  • Thank you very much, Kalpana! you solved my problem.
    – jsmith
    Commented Apr 27, 2021 at 8:48
  • Any other reasons why this might happen? I'm seeing the same thing, but my process is already not recursive
    – denvergreene
    Commented Sep 1, 2021 at 4:04

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .