Skip to main content

Dynamic Approval Process on Salesforce

Ever come across the need of a large approval process where you do not know who the approver of the next stage will be? We all do don't we?

In a recent project requirement, I had to work on a big approval process. My basic requirement was:

1. One approval process for child object
2. Once child is approved, it should trigger the master object approval process

Both the approval process had around 5 steps and the approvers where determined by the role hierarchy and the region of the submitter.

Yikes is it?

Pre-requisites:
For this recipe, you need
1. Basic knowledge of APEX and trigger
2. Basic knowledge of Approval process
3. Aspirin (just in case you miss a step and have to debug it!!!)

So lets begin with the Child Object Dynamic Approval process.

Steps for Child Object Dynamic Process
1. Create two fields on the child object. These fields will not be shown on Page Layout.
       i) Approval_step__c: Text field to determine which step the approval is.
       ii) Next_approval__c: A user field to store the approver.

2. Create the approval process.
    i) Initial submission action will be field update: Approval_step__c='Submitted for approval'
    ii) In approver step, select related user and add the Next_approval__c
    iii) In the approval Step Action, field update for Approval_step__c with the next step of Approval. Keep a            note of these keywords.
   iv) Repeat the ii) and iii) till you finish all the approval steps.

3. Write a before update trigger on child object
   i) Check if Trigger.old.Approval_step__c != Trigger.new.Approval_step__c (this is a pseudo code, you will have to iterate through trigger.new and old and compare all values, if you do not know how to do this, add a comment below)
   ii) Now based on the value in Approval_step__c fetch the respective user from Role Hierarchy or anywhere else. Better option would be to use custom settings for this. Add this user in Next_approval__c
   iii) Repeat step ii) till you finish all the approval steps. The final approval step would be to either empty the  Next_approval__c field or set it back to manager of the user.


4. Optional step If you need to trigger another approval process after this.
   i) In the approval process, set the final approval action to 'Approved'
   ii) In the trigger if the field value is 'Approved' then submit the Master in Approval process using Apex Code. (There are many links which give you direct code, the code on my blog will come in next post. )

That's it. It is easily understood that you need to repeat the whole process for master if he needs dynamic approval.
After you done everything, take a deep breath and test your code. If it doesn't the way it should, take an aspirin and debug. Since this uses hand-shake between trigger and approval steps make sure you don't miss out on any step.

It works and I did not need Aspirin, thank God for that.

Note: As this approval process updates back-end, the visual process manager won't be able to visualize it.

Hope it helps,

Comments

  1. Hi Sid..Nice Blog on Approval Process.. Could you please provide the actual code for approval process ( The pseudo of step 3 ).. Thanks in advance

    Regards
    Maddy

    ReplyDelete

Post a Comment

Popular posts from this blog

Video: Top ten tips on how not to ruin Salesforce implementation

Another presentation for the London Salesforce Developer Group using mobile app. 
When it comes to Salesforce development, we all know what it takes to deliver stuff. Having a certified professional helps you gain a knowledgeable partner but what about the things such as common sense?  We all know how to deliver things on client requirements but what about things that are not mentioned by the client. We will be discussing in details things that will enhance the user experience, focus on tips to read your customers mind and have a bit of perspective on the user experience.

Cache me if you can: What you should know before daring to set URL parameter on visualforce

If someone gave me a pence for every time there was an SOQL query in an APEX Class without using Limit or a condition during a code review, I could afford a Lamborgini this month. Sigh. If only. We make it a habit of going digging for data, at the very moment we need it. The crux of this problem happens when you have chain classes which are independent of each other. Each class needs the reference from a single record and we have to query for that record every single time.

While we don't see it, every SOQL query has a cost to it, and it does not go in my Lamborghini fund, however, it should. In a recent project, we had to construct an Account 360 page that could fetch information from different integration points. The page was also called using a live telephony integration, which could pass the phone number for the account. This required an ability to keep in context the Account that was on call.

Passing the Account id in URL parameter was a valid option, however, any manipulatio…

Four secrets to improve the usability of your visualforce/Lightning pages on Salesforce

In the immortal words of a certain machine returning back in time, I am back. For now. After procrastinating for over a year and drafting a lot of rants- I am back with a very important coding lesson for you. For now.

When we are designing a Visualforce page or an app or a lightning component (added that only to trick google) or any web page for that matter, we often tend to wrap up things quickly. Ask anyone on the team, how to design a good User Experience? and the person will immediately throw buzz words like Bootstrap, angular and other useless libraries (did someone squint?)

Ok, Bootstrap, Angular-Js, and all the libraries are really cool and are useful in designing a fabulous UI. They are helpful in creating responsive pages that will work on all the devices but this post is not about those. Nope. For the purpose of this post, all the external libraries and buzzwords you use to decorate your resume are useless. (Adding Angular JS in your resume for a Salesforce consultant posit…