Ask Search:
Lisa SouletLisa Soulet 

Benefit of using Process Builder to invoke an Approval Process

What would be the potential benefits of using Process Builder to invoke an Approval Process?  Do you need to duplicate entry criteria in both Processes in order for it to function correctly (if not, which process should contain the entry criteria)?  I have also attempted to use the "Default Approval Process" option in Process Builder and it did not function correctly.  Not sure if I am missing something.

Any input would be appreciated.
Best Answer chosen by Lisa Soulet
Deb WellerDeb Weller

The benefit of using Process Builder is that you don't have to rely on the user to press the Submit for Approval button; you can have it automatically submitted for approval when certain conditions happen.  It's a nicer user experience.  You would define the criteria to invoke the process.  In the approval process, you would just need to make sure the the entry criteria worked for the conditions.  

All Answers

Scott JohnsonScott Johnson
The only advantage of of using process builder if is you need/want to automatically submit for approval, based on another update to the record.  I typically use "Default Approval Approval Process" to do this.  You just need to make sure the record meets the entry criteria for your approval process.

OR - the user can manually submit for approval.  

Either way, it still needs to meet the entry criteria for the approval process you want to use

 
Deb WellerDeb Weller

The benefit of using Process Builder is that you don't have to rely on the user to press the Submit for Approval button; you can have it automatically submitted for approval when certain conditions happen.  It's a nicer user experience.  You would define the criteria to invoke the process.  In the approval process, you would just need to make sure the the entry criteria worked for the conditions.  

This was selected as the best answer