Skip to main content
At this point, I think it's safe to say that everyone who has done an approval process has been burned by the 'Re-evaluate Workflow Rules after Field Update' checkbox at least once. I'm getting stuck now when I finally thought I understood the box.

 

Let me set the stage: I have a custom object with several 'stages' for each record. Each stage has its own section on the layout, a corresponding picklist value in the 'Stage' field, and some tasks and/or approval processes that they go through. This is all facilitated through a process builder and 3 approval processes.

 

Use Case: For each approval process, if the record is rejected, I would like it to go back to the previous stage. No problem. However, I would like the user assigned to that stage to know that this was a record submitted and rejected, and not a new record in stage 2.

 

The Issue: My idea was to not use the 'Re-evaluate' checkbox on the Final Rejection field update, and to instead create a new action to Task the owner of that stage. This way I could add custom messaging saying it was rejected. The issue with this approach is that within the Approval Process UI, it seems there are only a small set of standard fields that can be changed on the task record and we use custom fields that I would want to set. Additionally, I cannot get the standard Stage 2 task (in the Process Builder) to not fire, even though the 're-evaluate' checkbox on the field update isn't checked. I'm wondering if my the 'Recursion' checkbox on the process builder is messing with it and causing that action to still fire.

 

Anyone have thoughts on how I could fix this? 
1 resposta
0/9000