Workflow Rule in Salesforce

on



Workflow Rule in Salesforce:  

Workflow rules is an automation tool in Salesforce that offers time-saving solutions for making different internal processes of a company switch from manual work and for optimizing various procedures.

Workflow in Salesforce is basically a container or business logic engine which automates certain actions based on particular criteria. If the criteria are met, the actions get executed. When they are not met, records will get saved but no action will get executed.

Components of Workflow in Salesforce:

Workflow rules in Salesforce can be broken down into two main components:

  1. Criteria:
    Criteria are conditions you are supposed to put in order to test a record. For example, if you’re from a technical background, what the if statement does in an if/then the condition is what criteria mean in a workflow.

  2. Actions:
    Actions occur after a record meets the criteria. Again, what the then statement does in the if/then the condition is what an action means in the workflow.

Types of actions present in a workflow in Salesforce:

  • Immediate actions:
    Actions that get executed immediately when a record is created or edited

  • Time-dependent actions:
    Actions that get executed after a certain duration of time.

Types of evaluation criteria:

  • Created:
    Whenever a record is created and the criteria match with the record, the action is executed.

  • Created and edited it:
    Whenever a record is created or updated, the action will be executed.

  • Created and every time it’s edited to subsequently meet the criteria:
    Whenever a record is created and it stands true to the criteria, the action will be performed. Now, if the record is edited and it doesn’t meet the criteria, the action will not be performed.

    Suppose, the created record doesn’t meet the criteria, and then it is edited or updated to meet the criteria. It will be evaluated again and, if it meets the criteria, the action will be performed. Otherwise, it won’t be performed.

Types of Workflow actions:

  1. Task – Assign a Task.
  2. Email Alert – Send an Email.
  3. Field update – Update a Field.
  4. Outbound message – Send an Outbound message.

Workflow Limits:

PER-ORG LIMITVALUE

Total rules across objects

(Applies to any combination of workflow, assignment, auto-response, and escalation rules, active and inactive.)

2,000

Total rules per object

(Applies to any combination of workflow, assignment, auto-response, and escalation rules, active and inactive.)

500

Active rules per object

(Applies to any combination of active workflow, assignment, auto-response, and escalation rules, as well as record change processes.)

50
Time triggers per workflow rule110
Immediate actions per workflow rule140
Time-dependent actions per time trigger40
Workflow time triggers per hour1,000
Flow trigger workflow actions: flow variable assignments225 (N/A in Professional Edition)

Combined total of these automations that start or resume based on a record’s field value.

  • Resume events that are defined in active flows
  • Groups of scheduled actions that are defined in active processes
  • Time triggers that are defined in active workflow rules
  • Inactive flow interviews that are resumed
20,000

The immediate actions and each time trigger can have:

  • 10 email alerts
  • 10 tasks
  • 10 field updates
  • 10 outbound messages
  • 10 flow triggers


# How can we count the total number of workflow rules in our org.

Counting one by one manually is a time consuming process if there are more rules! Solution is using a simple SOQL query we can get the total workflow count. 

  • Go to Salesforce org
  • Click on Gear Icon (Dropdown menu)
  • Click on Developer Console
  • In the Developer Console, click the Query Editor  tab.
  • Copy and paste the following SOQL Code line into the first box under Query Editor, and then click Execute.

1. To get the overall workflow rule count in the org, use

SELECT count(Id), TableEnumOrId FROM WorkflowRule Group by TableEnumOrId

2. To get the workflow rule count for any sObject. Let's say for account object use

SELECT count(Id), TableEnumOrId FROM WorkflowRule WHERE TableEnumOrId = 'account' Group by TableEnumOrId

## Don't forget to check the 'Use Tooling API' checkbox next to Execute.

Note: 

By default, each object is limited to 50 active workflow rules. Total workflow rules per object is 500.


 Resources: 


Comments

Post a Comment

Popular Posts

Image

Asynchronous Apex in Salesforce : Future Methods

Asynchronous Apex in Salesforce : Future Methods Future Apex is used to run processes in a separate thread, at a later time when system resources become available. A future method runs in the background, asynchronously. You can call a future method for executing long-running operations, such as callouts to external Web services or any operation you’d like to run in its own thread, on its own time. You can also use future methods to isolate DML operations on different sObject types to prevent the mixed DML error. Each future method is queued and executes when system resources become available. That way, the execution of your code doesn’t have to wait for the completion of a long-running operation. A benefit of using future methods is that some governor limits are higher, such as SOQL query limits and heap size limits. You can call 50 future methods per transaction. Things to Remember: Methods are annotated with  @future  annotation. Use the future annotation to specify that th...
Image

Salesforce Admin Interview Questions and Answers

Salesforce Admin Interview Questions and Answers Q. What is the Cloud computing? - "Cloud Computing is a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources that can be rapidly provisioned and released with minimal management effort or service provider interaction." Cloud computing is the on-demand availability of computer system resources, especially data storage and computing power, without direct active management by the user. Large clouds often have functions distributed over multiple locations, each location being a data center.   More info about Cloud Computing    Q. What are the characteristics of Cloud Computing? - On-demand, Scalable, Multi-tenant, Reliability and Utility based subscription. Q. What are the different types of clouds? 1. Public Cloud 2. Private Cloud 3. Hybrid Cloud Q. What is Public cloud? - A service provider makes resources, such as applications and storage, available to ...
Image

Apex Triggers in Salesforce

  Apex Triggers in Salesforce A Trigger is a segment of Apex code which executes before or after inserting or modifying a Salesforce record based on the condition provided. There are different types of triggers based on the action going to be performed. What is Trigger in Salesforce ? Trigger in Salesforce is essentially an Apex script used by developers before or after events related to data manipulation language (DML). Here are some of the key types of operations executed by a trigger: 1. Inserting data into the system. 2. Updating data within the system. 3. Deleting data from the system. 4. Merging data across platforms. 5. Upserting data into the system. 6. Undeleting data from the system. What are different types of Triggers? Before triggers are used to perform a task before a record is inserted or updated or deleted. These are used to update or validate record values before they are saved to the database. After triggers are used if we want to use the information set by the...
Image

DML - Data Manipulation Language in Apex

What is DML in Apex ?  Data Manipulation Language (DML)    Create and modify records in Salesforce by using the Data Manipulation Language, abbreviated as DML. DML provides a straightforward way to manage records by providing simple statements to insert, update, merge, delete, and restore records. # DML Statements: The following DML statements are available. insert update upsert delete undelete merge Each DML statement accepts either a single sObject or a list (or array) of sObjects. Operating on a list of sObjects is a more efficient way for processing records. All those statements, except a couple, are familiar database operations. The upsert and merge statements are particular to Salesforce and can be quite handy. The upsert DML operation creates new records and updates sObject records within a single statement, using a specified field to determine the presence of existing objects, or the ID field if no field is specified. The merge statement merges up to three records...