Skip to main content

Basic of WorkFlow in Salesforce with Real Scenario Example

We live in a world increasingly trying to transform every component of it into a digital one. Business of all kinds are being built on digital platforms, some of them which until a few years ago had nothing to do with technology, are also willing to take the advantage of perks and flexibilities that a digital implementation would do in their business.


With such a rapidly changing world, expectations are bound to increase and innovation through technology has become utmost important. Whether it’s a website to direct customers your way, an app to help improve their experience, or another project altogether, this naturally means that some kind of software development is needed.

Let us know about the two modes of Programming we use to accomplish our software development goals:

1.       Imperative Programming:  This generally refers to the traditional code-oriented programming where we use certain coding languages- such as C, C++, Apex and so on—to tell the computer what action to perform. This requires a skilled developer with programming knowledge and at times, combined with experience. The developer builds the application block by block using code blocks, in some development environment.

2.       Declarative programming: This approach to programming accomplishes the same goal by basically telling the computer the end result and letting the computer figure how to get there. In simpler terms, Declarative Programming would involve drag-and-drop solutions that allow someone without coding knowledge to build an application. The blocks of code are pre-written and packaged into components that you as developer just need to select as needed.


Now that you got the basics of approaches to software development, let’s cut the chase and talk about what I am specifically here for. How does the Salesforce uses these two methodologies of software development? What are it’s pros and cons? How do we know when to take what approach of programming in Salesforce? we talk of the same in terms of its use in Salesforce:

Business scenarios and uses:

Let’s say you run a small business or startup, you would need to save money wherever you can. Hiring a specialist Coder/Developer would significantly increase your expenses, while as an alternative you might want to learn the programming language yourself to accomplish your software development goals. However, you might face difficulty dedicating time to learn programming languages when you have other aspects of business to manage. Looks messy, eh?

This is where Declarative tools in Salesforce come handy. You don’t need to learn a new programming language or hire a specialist developer to accomplish your development goals. Declarative tools in Salesforce are made for you to be able to accomplish your objectives in the most convenient way possible. Declarative tools mainly involve use of Point-and-Click and Drag-and-Drop actions which are easy for you to master even without a Coding/Development experience.


Declarative tools in Salesforce can help us eliminate repetitive tasks, freeing up an admin’s time to do more profound things. These tools mainly include Workflow Rules, Process Builder, and Flow. Each tool comes with its own unique features, advantages, and disadvantages, meaning that there is probably the best-fit tool for each scenario an admin faces. In order to understand when to use which, we’ll take a look at the features each one offers.

Workflow Rules

Workflow rules is most commonly used automation tool, as it has been around the longest and is very reliable. While Workflows are somewhat limited in functionality compared to the other tools available, they rarely break, are very fast, and are extremely easy to use.


Things you can do using Workflow Rules:

·         1. Create a Task 

·         2.Update a Field 

·        3. Send an Email 

·         4.Send an Outbound Message 



Workflow rules are so easy to use which makes them an excellent starter tool for any new admin or developer. The functionality is so simple, and it’s rare to run into issues. Workflows also have hardly any limits, i.e, if you have a large org with a lot of data, Workflows should handle it without a problem.



Workflow rules only evaluate one outcome, either it’s true and it will execute, or it’s false and it won’t. The fact that they are so simple can also be their downfall; if you’re looking for advanced automation, look away from Workflow Rules!


Popular posts from this blog

What is Express & how we use it .

Express: we usually heard express as expressjs and many people think that it as a library. Lets  try to understand what is Express.