Does the multitude of BPA Tools in SFDC puzzle you?

Salesforce is a very dynamic platform which keeps adding amazing tools and features to its kitty on a quarterly basis. The addition of new forward looking features shows that through its platforms like - "Idea-force or Ideas" , "Success-force","Feedback Channels" , "Community Platforms" its constantly listening to what its user community and customers are talking w.r.t. improvements , enhancements, small and big modulations to bring about customer delight. While that provides us multiple options to implement our solutions at times one may feel a bit lost about which tool to adopt for the problem at hand.

One of the classic examples is multiple tools available in salesforce for BPA or "Business Process Automation" tools. We all are aware that the options available are :-

• Workflow Rules
• Approval Processes
• Process Builder
• Cloud Flow Designer

Please note these are admin or configuration tools (some will need developer skills) , we also have the option of full-blown custom solution using code , which should be avoided as they pose challenges with house-keeping and maintenance in the long run.

The question which might bother a rookie is that- which tools to use and when? Well let's consider some scenarios to answer that. 

Scenario I 

Let's say your sales-rep has submitted a request for organising a "Training Activity" which goes to his/her manager for approval. In such scenarios where approvals are required by a supervisor utilise - "Approval Process"

Other set of Scenarios

Let's say our Business Process requires action based on certain values of the record in such a case we can utilise Work Flow Rule, Cloud Flow Builder and Process Builder. 

Scenario II

Simple/single  if-else condition warrants use of "Workflow Rule". Also if your use-case involves :-

1. only updating fields of the record or its parent record  
2. sending outbound message without code
3. creation of tasks
4. email alerts

Scenario III

Complex if-else condition warrants use of "Process builder". Also if your usecase involves:- 

1. update of any related record 
2. post to chatter
3. creation of records
4. email alerts
5. invoke flows or other process
6. Things cannot be done via process builder are sending outbound messages without code and getting input from end user.

Scenario IV

If your usecase requires getting information from Users or Customers , which is then followed by doing something with those inputs one needs to use Cloud Flow Designer . Also use CFD if your usecase involves the following:- 

1. requires user interaction
2. update of any  record 
3. delete records
4. post to chatter
5. creation of records
6. send email
7. launch a flow
8. Things cannot be done via CFD are sending outbound messages without code and cannot invoke process.

 The above scenarios provide an insight into which path to embark upon while automating your business processes.  More in my following blog , bye for now, have a great holiday season!