Salesforce Process Builder Guide

Using Process Builder (Beta)
Salesforce.com, Winter ’15
@salesforcedocs
Last updated: September 17, 2014
© Copyright 2000–2014 salesforce.com, inc. All rights reserved. Salesforce.com is a registered trademark of salesforce.com,
inc., as are other names and marks. Other marks appearing herein may be trademarks of their respective owners.
CONTENTS
USING PROCESS BUILDER (BETA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Process Builder Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Understanding the Process Builder User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Process Limits and Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Creating Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Managing Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Troubleshooting Your Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
USING PROCESS BUILDER (BETA)
Process Builder Overview

Many of the tasks you normally assign, the emails you regularly send, and other record updates are
EDITIONS
vital parts of your organization's standard processes. Instead of doing this repetitive work manually,
you can configure processes to do it automatically. Available in:
Note: Any unreleased services or features referenced in this document, press releases, or • Enterprise
public statements are not currently available and may not be delivered on time or at all. • Performance
Customers who purchase our services should make their purchase decisions based upon • Unlimited
features that are currently available. • Developer
The Process Builder is a new workflow tool that helps you easily automate your business processes
by providing a powerful and user-friendly visual representation of your process as you build it. The Process Builder’s simple and powerful
design allows you to:
• Create your processes using a convenient visual layout with point-and-click efficiency.
• Create your whole process in one place rather than using multiple workflow rules.
• Have multiple colleagues contribute to creating your business processes.
• Stop using Apex code to automate simple tasks.
Automated processes in the Process Builder consist of criteria that determine when to execute action groups and immediate and
scheduled actions to execute when those criteria are met. Any change that causes a record to match the criteria can automatically trigger
the action group.
If you’re familiar with workflow, you can use the Process Builder to perform all of the same actions (with the exception of outbound
messages), but with more power and flexibility. Without writing a single line of Apex code, you can:
• Create a record.
• Update fields on any related record—not just the record or its parent.
• Launch a trigger-ready flow—as an immediate or a scheduled action.
• Send an email.
• Post to Chatter.
• Submit for approval.
IN THIS SECTION:
When Should I Use a Process?
Salesforce provides multiple ways to automate your organization’s repetitive business processes: workflow rules, flows, and processes.
Processes can automate every action that can be automated in a workflow rule, with the exception of outbound messages, but flows
should be used to automate more complex business processes.
Sample Process: Opportunity Management
This example automates a single business process by using the Process Builder instead of workflow rules.
1
Using Process Builder (Beta) When Should I Use a Process?
When Should I Use a Process?

Salesforce provides multiple ways to automate your organization’s repetitive business processes:
EDITIONS
workflow rules, flows, and processes. Processes can automate every action that can be automated
in a workflow rule, with the exception of outbound messages, but flows should be used to automate Available in:
more complex business processes. • Enterprise
Create a process with the Process Builder if what you need to automate is similar to a simple “if, • Performance
then” statement (i.e. you need to evaluate whether certain conditions are true and, if so, do • Unlimited
something). • Developer
Create a flow with Visual Workflow if the process is too complicated for the Process Builder or
requires more advanced functionality. For example, create a flow if you need to:
• Build a wizard for your employees, such as a script for a customer call
• Use complex branching logic (i.e. if certain conditions are true, evaluate for further conditions)
• Sort through, iterate over, and operate on several records
• Use Apex to make web service call-outs
• Use data in your process from outside of Salesforce
Sample Process: Opportunity Management

This example automates a single business process by using the Process Builder instead of workflow
EDITIONS
rules.
The example demonstrates how you can use the Process Builder to automate a single process by Available in:
adding multiple groups of criteria and then associating individual actions with those criteria. In • Enterprise
addition, some actions are available with the Process Builder that you can’t perform with workflow • Performance
rules, such as creating records. • Unlimited
• Developer
In this example, the process is defined to start when an opportunity record (1) is created or edited.
Three criteria nodes are then set up to check whether a high-value deal was won (2), a high-value
deal was lost (3), or a quote was given (4). For the first criteria node that evaluates to true, the associated action group is executed.
2
Using Process Builder (Beta) Sample Process: Opportunity Management
The High Value Deal Won criteria checks whether the opportunity’s stage is closed and won and also whether the opportunity’s amount
is greater than $1,000,000.00. If both of these conditions are met, the associated action group is executed. For this criteria node, three
immediate actions (5) and one scheduled action (6) are defined.
These actions:
• Create a draft contract record that's associated with the opportunity’s account.
• Congratulate the opportunity owner for closing and winning the opportunity by posting to the Sales Chatter group.
• Notify the VP of sales via email that the opportunity was closed and won.
• Create a high priority follow-up task for the associated account’s owner, which is scheduled to execute six days after the opportunity’s
Close Date .
If the High Value Deal Won criteria conditions aren’t met, the associated group of actions doesn’t execute and the next criteria node
(High Value Deal Lost) is evaluated.
The High Value Deal Lost criteria node checks whether the opportunity stage is closed and lost and whether the opportunity amount
is greater than or equal to $1,000,000.00. If these conditions are true, we’ve set up an action (7) to notify the VP of sales by creating a
chatter post on the opportunity record. The post identifies the opportunity and the opportunity amount that was lost.
3
Using Process Builder (Beta) Understanding the Process Builder User Interface
If neither of the previous criteria conditions are met, the next criteria node defined in this process checks whether the opportunity stage
is set to “Quote Given.” If this condition is true, a scheduled action (8) is executed three days after the record is updated. The scheduled
action creates a follow-up task for the opportunity owner to make a call to inquire about the opportunity.
Using the Process Builder, we’ve combined three criteria nodes and associated actions into a single, automated process. To automate
the same business process with workflow, you would have to create three different workflow rules and use Apex triggers to create the
contract record and post to the Sales Chatter group.
Understanding the Process Builder User Interface

The Process Builder user interface has several functional areas that you should understand before
EDITIONS
creating a process.
Available in:
• Enterprise
• Performance
• Unlimited
• Developer
Button Bar (1)

Use the buttons in the button bar to activate or edit the properties of the open process, save the process as a new one, or return to the
process management page. The status indicator on the right side of the bar shows whether your process is in read-only mode. If it isn’t,
the status indicator shows when the process was last saved.
• Back returns you to the process management page, which contains a list of all processes in your organization.
• Save As enables you to save the process as a new process.
• Edit Properties shows you the name, API name, and description of your process. You can edit the name and description of your
process at any time, but you can’t change its API name after you’ve saved it for the first time.
4
Using Process Builder (Beta) Setting Values in the Process Builder
• Activate enables Salesforce to start using this process to evaluate records. After you activate a process, it can’t be edited.
• Deactivate stops Salesforce from using this process to evaluate records. You can deactivate only active processes. Once you deactivate
a process, its status is Obsolete and it can’t be edited; however, you can click Save As to create a new draft process based on the
deactivated one.
Canvas (2)
The canvas is the main workspace for a process. On the canvas, you can define:
• The records that the process should evaluate (3)
You identify the object and specify the changes (to that object’s records) that will cause the process to run.
• One or more criteria nodes (4)

Each criteria node includes conditions that are used to evaluate the record. A criteria node evaluates based on filter criteria—such
as whether the value for the Amount field is greater than 1000—or based on a formula.
• One or more actions (5)

You can add up to 10 immediate actions and 10 scheduled actions to a given criteria node. If the criteria are met for the record that
starts the process, the criteria node’s associated action group (6) is executed immediately or based on the schedule defined for the
action.
IN THIS SECTION:
Setting Values in the Process Builder
Throughout the Process Builder, you need to set values for fields or flow variables, for example, to set filter conditions in a criteria
node or to set the fields on a new case in a Create a Record action. Set a value for a given field or flow variable by using the text entry
field to manually enter a value or the field picker to find another field value to reference—whether on the record that started the
process or a related record.
Setting Values in the Process Builder

Throughout the Process Builder, you need to set values for fields or flow variables, for example, to
EDITIONS
set filter conditions in a criteria node or to set the fields on a new case in a Create a Record action.
Set a value for a given field or flow variable by using the text entry field to manually enter a value Available in:
or the field picker to find another field value to reference—whether on the record that started the • Enterprise
process or a related record. • Performance
Click the icon under Value to switch between the text entry field and the field picker. • Unlimited
• Developer
5
Using Process Builder (Beta) Setting Values in the Process Builder
Text Entry Field

The text entry field is indicated by . When you use the text entry field, you manually enter literal values or select from provided values.
For example, for checkbox fields you can select either True or False from a drop-down list.
For text fields, you can manually enter a string or enter one of the following global constants. These global constants aren’t supported
with the “is null” and “was set” operators.
• $GlobalConstant.Null sets the value to null.
• $GlobalConstant.EmptyString sets the value to an empty string.
For fields that aren’t text fields, such as date and currency fields, the Process Builder displays the format that you should use to enter
your value. After you enter a value, press TAB to verify your entry.
Field Picker
The field picker is indicated by . When you use the field picker, you reference another field on the record or on a related record.
The field picker displays only fields that are compatible with what’s selected for Field or Flow Variable. For example, when you’re setting
a value for a currency field, with the field picker you can select only currency fields.
When you use the field picker, you must click Insert to select a field. To use fields on a related record, click . For example, you can
use the value for the case’s contact’s Account ID.
6
Using Process Builder (Beta) Process Limits and Considerations
Process Limits and Considerations

Before you start creating, managing, and activating processes, understand the limits and
EDITIONS
considerations.
Available in:
IN THIS SECTION: • Enterprise
• Performance
Process Limits
• Unlimited
When using the Process Builder, keep shared limits and Apex governor limits in mind.
• Developer
Process Builder Accessibility Considerations
Process Builder is 508-compliant, with a few exceptions.
Process Design Considerations
Before you design a process, understand the limitations and guidelines.
Process Scheduled Actions Considerations
Before you add scheduled actions to a process, understand the limitations and guidelines.
Process Administration Considerations
When managing flows, consider the administration and activation limitations.
Process Activation Considerations
Process Limits
When using the Process Builder, keep shared limits and Apex governor limits in mind.
EDITIONS
You must use the most recent stable version of Google Chrome™, and your screen resolution must
have a width of at least 1024. Available in:
• Enterprise
• Performance
Limits Shared with Other Features • Unlimited
Processes share some limits with rules and Visual Workflow. • Developer
In addition to the following limits, a process’s API Name must be unique across all processes
and flows in your organization.
7
Using Process Builder (Beta) Process Limits
Description Per-Organization Limit

Total active rules and active processes. 50 per object
Rules include workflow rules, escalation rules, assignment rules, and auto-assignment rules.
Total flows and processes 1000
Active flows and processes 500
Total number of criteria nodes that are evaluated and actions that are executed at runtime 2000
Total number of flow interviews that are resumed or groups of scheduled actions that are executed per 1000
hour
Total number of flow interviews or groups of scheduled actions that are waiting to be processed 30,000
Total number of relative time alarms defined in flow versions or schedules based on a field value in 20,000
processes
The daily limit for emails sent from email alerts is 1,000 per standard Salesforce license per organization—except for Developer Edition
organizations, where the daily workflow email limit is 15 per standard Salesforce license. The overall organization limit is 2,000,000. This
limit is shared across all features that use workflow email alerts: workflow rules, approval processes, flows, and processes.
Apex Governors and Limits for Processes

Salesforce strictly enforces limits to ensure that runaway processes don’t monopolize shared resources in the multitenant environment.
Processes are governed by the per-transaction limits that are enforced by Apex. If the process causes the transaction to exceed governor
limits, the system rolls back the entire transaction. For details about the operations that are included in the transaction, see “Triggers
and Order of Execution” in the Force.com Apex Developer’s Guide.
Description Per-Transaction Limit

Total number of SOQL queries issued 100
Total number of records retrieved by SOQL queries 50,000
Total number of DML statements issued 150
Total number of records processed as a result of DML statements 10,000
Each “Create a Record” action uses one DML statement. Each “Quick Action” action uses one DML statement. Each “Update Records”
action uses one SOQL query and one DML statement. Each “Launch a Flow” action can use multiple SOQL queries and DML statements,
depending on the elements that the flow executes. For details, see “General Flow Limits” in the Salesforce Help.
8
Using Process Builder (Beta) Process Builder Accessibility Considerations
Process Builder Accessibility Considerations

Process Builder is 508-compliant, with a few exceptions.
EDITIONS
• You can’t close side panels by using the ESC key on your keyboard.
• You can’t navigate through the field picker by using your keyboard. For details on the field Available in:
picker, see Setting Values in the Process Builder on page 5. • Enterprise
• Performance
• Unlimited
• Developer
Process Design Considerations

Before you design a process, understand the limitations and guidelines.
EDITIONS
• Process Builder and processes are supported only in English.
• Make sure that your processes aren’t set up to create recursive loops. For example, if an Update Available in:
Records action for Process1 triggers Process2 and a Create a Record action for Process2 triggers • Enterprise
Process1, the recursive triggers might cause your organization to exceed its hourly limits. • Performance
• Unlimited
• If you create processes to replace any workflow rules, make sure you delete those workflow
• Developer
rules when you activate the equivalent processes. Otherwise, both workflow rules and processes
will fire and cause unexpected results, such as overwritten records or redundant email messages.
• If you create processes to replace any Apex triggers, make sure you delete those Apex triggers when you activate the equivalent
processes. Otherwise, both workflow and processes will fire and cause unexpected results, such as overwritten records or redundant
email messages.
• Process Name must be 255 characters or fewer.
• API Name must be 79 characters or fewer.
• Each process is associated with a single object.
• If you have processes on converted leads and want to update the records that result from the conversion, you must enable the lead
setting Enable Validation and Triggers from Lead Convert .
• You can’t change the order of the criteria nodes or the order of the actions. After you add criteria nodes and actions, the only way
to reorder them is to delete them and start over.
• Picklist fields are evaluated as text fields in the Process Builder. If a formula function doesn’t support text fields, you can’t use a picklist
field in that function. For example, you receive an error if you use the ISCHANGED formula function to determine if a case’s
Status has changed.
• Actions are executed in the order in which they appear in the Process Builder.
• If any of the actions fail, the entire transaction fails and an error message displays. For example, a Post to Chatter action fails if the
Chatter group that it tries to post to is private. For details, see Troubleshooting Your Processes on page 32.
• You can add up to 10 immediate actions and 10 scheduled actions to a given criteria node.
• If a single action group includes multiple “Update Records” actions that apply different values to the same field, the last action’s
value is used.
• Processes that update owners don’t also transfer associated items. To ensure transfer, use one “Update Records” action for each type
of child record that you want to transfer. For example, if you’re using a process to transfer an account to a new owner, use one action
to update all the child contacts, one to update all the child opportunities, one to update all the child contracts, and so on.
• If your organization uses multiple currencies, currency fields are updated using the record's currency. If you choose to update a field
based on a formula, any values in your formula are interpreted in the currency of the record.
• Email alerts aren’t supported for task- or event-based processes.
9
Using Process Builder (Beta) Process Scheduled Actions Considerations
Process Scheduled Actions Considerations

Before you add scheduled actions to a process, understand the limitations and guidelines.
EDITIONS
• If the user who caused the process to start is inactive when Salesforce tries to execute scheduled
actions, those actions fail to execute. Available in:
• After you deactivate a process, any scheduled actions continue as usual. • Enterprise
• Performance
• You can’t delete a process if it has unexecuted groups of scheduled actions. For details about
• Unlimited
deleting unexecuted groups of scheduled actions, see Delete Unexecuted Scheduled Actions
• Developer
on page 32.
• An organization can process up to 1000 groups of scheduled actions per hour. Each group of
scheduled actions is associated with a schedule, such as “3 days from now.” When a schedule is processed, the associated actions
are executed. If an organization exceeds this limit, Salesforce processes the remaining schedules in the next hour. For example, if an
organization has 1,200 groups of pending actions scheduled to be processed between 4:00 PM and 5:00 PM, Salesforce processes
1000 groups between 4:00 PM and 5:00 PM and the additional 200 groups between 5:00 PM and 6:00 PM.
• An organization can have up to 30,000 pending schedules and waiting flow interviews at one time.
• For processes that are set to run when a record is created or edited, scheduled actions remain in the queue only as long as the criteria
for those actions are still valid. If a record no longer matches the criteria, Salesforce removes the scheduled actions for that record
from the queue.
• For processes that are set to run when a record is created, Salesforce never reevaluates the record with that process. Scheduled
actions remain in the queue, even if the record no longer meets the associated criteria when the scheduled actions are executed.
Transactions and Scheduled Actions

Similar to workflow rules, immediate actions in processes are executed in the same transaction as the operation that caused the process
to be triggered—when a user created or edited a record. For details about the operations that are included in that transaction, see
Triggers and Order of Execution in the Force.com Apex Developer’s Guide. Scheduled actions are included in a separate transaction.
Groups of scheduled actions aren’t performed independently. They’re grouped into a single batch that starts performing within one
hour after the first group enters the batch. The batch can also include flow interviews that are resumed after a specified time occurs.
This behavior can cause you to exceed your Apex governor limits if any actions in the group execute DML operations or SOQL queries.
A DML operation is used each time a Salesforce record is created, updated, or deleted, such as when a process executes a “Create a
Record” action. A SOQL query is used each time Salesforce looks up information about an existing record, such as when a process executes
an “Update Records” action. For details on Apex governor limits, see Process Limits on page 7.
If your process contains scheduled actions, make sure that the actions don’t perform more DML operations or SOQL queries than are
permitted by the Apex governor limits.
If a group of scheduled actions fails to be executed:
• Prior groups of scheduled actions in that batch’s transaction are successful.
• The immediate actions for that process are successful.
• All the scheduled actions in that group fail to be executed.
• The remaining groups of scheduled actions in that batch are tried.
Example: Salesforce is going to process a batch of 25 groups of scheduled actions in the same transaction. Up to 100 DML
operations can be used across this batch. The first 22 groups each use five (5) DML operations, and the last three (3) groups don’t
use any DML operations.
The 21st group violates the Apex governor limits by trying to execute the 101st through 105th DML operations for this transaction.
Only this group of scheduled actions fails to execute. This means that the first 20 groups of scheduled actions are successfully
10
Using Process Builder (Beta) Process Scheduled Actions Considerations
executed and the 21st group of scheduled actions fails. None of the actions in the 21st group is successful, no matter which action
in the group violated the limit. Salesforce then tries to execute the remaining groups of scheduled actions in the batch. Because
the 22nd group uses five (5) DML operations and the transaction has already used all of its allowed DML operations, the 22nd
group also fails. Because the last three (3) groups don’t use any DML operations, those groups are successfully executed.
Schedule Limitations
• If actions are scheduled for a time in the past, Salesforce executes that group of scheduled actions within one hour.
For example, if a process is configured to email an opportunity owner seven days before the close date and the process runs for an
opportunity with the close date set to today, Salesforce executes the scheduled actions within an hour.
• You can’t set a schedule to zero days or hours.

If actions are scheduled based on the current time (i.e. 3 days from now):
• The schedule is evaluated based on the timezone of the user who created the process.
If actions are scheduled based on a field value (i.e. 3 days before a case’s Created Date ):
• The schedule is evaluated based on the organization's timezone.
• If a deactivated process still has pending scheduled actions and the record whose field the schedule is based on is changed, Salesforce
recalculates the schedule for those actions. Once a process is deactivated, Salesforce ignores all other changes to associated records.
• Across all of your processes and flow versions, your organization can have up to 20,000 schedules based on a field and relative time
alarms.
• The referenced field can’t be a:
– DATE or DATETIME field that contains automatically derived functions, such as TODAY or NOW .
– Formula field that includes related-object merge fields.
• If you change the referenced field value and the schedule hasn’t been processed, Salesforce recalculates the schedule associated
with that field.
For example, if a process is configured to email an opportunity owner seven days before the opportunity close date and the close
date is set to 2/20/2014, Salesforce processes the schedule on 2/13/2014 and sends the email. If the close date is later updated to
2/10/2014 and the schedule hasn’t been processed yet, Salesforce recalculates the schedule and sends the email on 2/3/2014. If
Salesforce recalculates the schedule to a date in the past, Salesforce executes the associated actions shortly after you save the record.
• Salesforce ignores schedules that reference null field values.

• If the record or the object that the schedule is associated with is deleted, the schedule is never processed.
• The following limitations apply for converted leads.
– You can’t convert a lead if an unexecuted schedule is based on one of the lead’s fields.
– If Validation and Triggers from Lead Convert is enabled, scheduled actions on leads aren’t executed during
lead conversion.
– If a campaign member based on a lead is converted before scheduled actions that are associated with that record finish, Salesforce
still executes the scheduled actions.
11
Using Process Builder (Beta) Process Administration Considerations
Process Administration Considerations

EDITIONS
• Processes aren't supported in the Metadata API, change sets, or packages.
• Processes aren't supported in organizations with a registered namespace. Available in:
• Enterprise
• If a custom object is deleted, all processes that are associated with that custom object are also
• Performance
deleted.
• Unlimited
• Error or warning messages might refer to a “flow” instead of a “process.” Those messages still • Developer
apply to your process.
• Before you change a custom field’s type, make sure that it isn’t referenced in a process that
would be invalidated by the new type.
• You can’t delete a custom field that is referenced by a process.
• After you activate a process, you can no longer edit that process.
• To delete an active process, you must first deactivate it and then wait for 12 hours. If a process has any scheduled actions, it can’t be
deleted until those pending actions have been executed.
Process Activation Considerations

Before you activate a process, understand when processes start evaluating records.
EDITIONS
• Salesforce processes rules in the following order:
Available in:
1. Validation rules
• Enterprise
2. Assignment rules • Performance
3. Auto-response rules • Unlimited
• Developer
4. Workflow rules and processes (and their immediate actions)
5. Escalation rules
• Because updates to records based on processes don’t trigger validation rules, processes can invalidate previously valid fields.
• Processes start automatically and are invisible to the user.
• Saving or creating records can trigger more than one process.
When Do Processes Start Evaluating Records?
• Processes can evaluate a record anytime it’s saved or created. However, processes that are created after records are saved don’t
evaluate those records retroactively.
• Processes are triggered when a standard object in a master-detail relationship is re-parented.
• Processes only evaluate converted leads if validation and triggers for lead convert are enabled in your organization.
• Processes evaluate changes made to records while using Connect Offline when users synchronize.
• In a batch update, processes are only retriggered on the entities where there is a change.
• The following actions don’t trigger processes:
– Mass replacing picklist values
– Mass updating address fields
– Mass updating divisions
– Changing the territory assignments of accounts and opportunities
– Converting leads to person accounts
12
Using Process Builder (Beta) Creating Processes
– Deactivating Self-Service Portal, Customer Portal, or partner portal users

– Converting state and country data by using the Convert tool
– Making changes to state and country picklists using AddressSettings in the Metadata API
Creating Processes
To create a process, define its properties and which records it should evaluate, and then add criteria
EDITIONS
nodes and actions.
Tip: Consider planning your process before you start. After you add criteria nodes and actions, Available in:
the only way to reorder them is to delete them and start over. • Enterprise
• Performance
• Unlimited
IN THIS SECTION: • Developer
Define the Process Properties
Define the process properties to uniquely identify and help you manage your processes.
USER PERMISSIONS
Identify Which Records to Evaluate
Associate the process with an object, and specify when to start the process. To create, edit, or view
processes:
Add Process Criteria • “Manage Force.com
Define the criteria that must be true before the process can execute the associated actions. Flow”
Add Actions to Your Process AND
After you’ve defined a criteria node, define the actions that are executed when the criteria are “View All Data”
met. You can add up to 10 immediate actions and 10 scheduled actions to a given criteria node.
Define the Process Properties

Define the process properties to uniquely identify and help you manage your processes.
EDITIONS
1. From Setup, click Create > Workflow & Approvals > Processes, and then click either:
Available in:
• New Process.
• Enterprise
• Edit next to a process. When the process opens, click Edit Properties. • Performance
• Unlimited
2. Fill out these fields to define your process.
• Developer
Field Description
Process The name for your process. Process Name must be 255 characters or USER PERMISSIONS
Name fewer.
To create, edit, or view
This name appears in the process management page (from Setup, this page processes:
is located at Create > Workflow & Approvals > Processes), so consider • “Manage Force.com
naming your process so that you can differentiate it from other processes. Flow”
AND
API Name The name that’s used by the API and managed packages. API Name must “View All Data”
be 79 characters or fewer.
This name must be unique across all processes and flows. (In flows, this field
is Unique Name .) The name must begin with a letter and use only
13
Using Process Builder (Beta) Identify Which Records to Evaluate
Field Description
alphanumeric characters and underscores. It can’t include spaces, end with an underscore, or have two
consecutive underscores.
After it’s saved, API Name can’t be changed for the process.
Description Optional. A description for your process.

The description also appears in the process management page and is intended to help you differentiate
between processes, such as to understand what the process does and when.
3. Click Save.
Warning: Save your changes often. If you click outside of a panel before saving—such as on another action in the canvas—any
changes that you made aren’t saved.
Identify Which Records to Evaluate

Associate the process with an object, and specify when to start the process.
EDITIONS
1. Click Add object.
Available in:
2. For Object , start typing, and then select the object that you need to base this process on.
• Enterprise
The process is run only when records of this object type are created or edited, depending on • Performance
what you select for Start the process when a record is . After you save this • Unlimited
panel, you can’t change the selected object. • Developer
Note: You must select the object from the search results. If you type Case and don’t
select “Case” from the results, the value is considered invalid. USER PERMISSIONS
3. Select when you need the process to start. To create, edit, or view
processes:
If you want the process to start every time that... Select • “Manage Force.com
Flow”
A record of the specified object type is created but not updated. created
AND
A record of the specified object type is created or updated. created or
“View All Data”
edited
Note: If you’re familiar with workflow rules and you’re wondering what happened to the third option (“created, and any time
it’s edited to subsequently meet criteria”), don’t worry! You’ll get to that setting when you add criteria nodes if you select
“created or edited” here.
4. Click Save.
14
Using Process Builder (Beta) Add Process Criteria
Add Process Criteria

Define the criteria that must be true before the process can execute the associated actions.
EDITIONS
When criteria are met, the process executes the associated action group. When criteria aren’t met,
the process skips the action group and evaluates the criteria for the next action group. Remember Available in:
that the process executes only one action group. • Enterprise
• Performance
Tip: Consider planning your process before you add criteria nodes and add actions to each • Unlimited
node. After you add criteria nodes, the only way to reorder them is to delete them and start • Developer
over. If you want to delete criteria, select the criteria in the canvas to open the side panel for
that criteria. Then click Delete at the bottom of the side panel.
USER PERMISSIONS
1. Click Add criteria.
2. Enter a name for this criteria node. To create, edit, or view
processes:
The name appears on the canvas, so use a name that helps you differentiate between other
• “Manage Force.com
criteria nodes.
Flow”
3. Select the type of criteria that you need to define. This selection determines which fields appear AND
later in the dialog box. “View All Data”
If you need... Select

The record to have certain field values. Filter conditions
For example, to execute the associated actions on opportunity records are met
with an amount greater than $5,000, set the filter to:
[Opportunity].Amount greater than $5000.00
To evaluate the record by using a formula. Formula

For example, to execute the associated actions on accounts whose annual evaluates to true
revenue is over $1,000,000 when the account is changed by someone
other than the owner, use this formula.
AND ( ( [Account].LastModifiedBy.Id <>
[Account].Owner.Id ) , ( [Account].AnnualRevenue
> 1000000 ) )
To simply execute the associated actions without evaluating the record. No criteria—just
The process executes all the actions that are associated with this criteria execute the
node and doesn’t evaluate any remaining criteria nodes in the process. actions!
Therefore, we recommend selecting this type of criteria only for the last
criteria node in a process.
4. If you selected “Filter conditions are met,” define the filter criteria.
a. For Filter Logic , select whether you want the actions to be executed when all the filter criteria are true or when any of
the filter criteria is true.
b. If you need to evaluate additional field values, click Add Row.
15
c. If you need to remove unnecessary rows, click .

You can’t remove the first row.
d. Define the field values that you need to evaluate.
Field Select the field whose value you want to evaluate. You can also evaluate values for records that are related to
the one that started the process. To do so, click next to the ID field for that related record.
For example, if a contact record started the process, you can evaluate the value for the contact’s account’s
Annual Revenue field. To access that field, click next to Account Id , select Annual Revenue,
and then click Insert.
Operator The available operators depend on the field’s data type.
Note: We recommend not using the “was set” operator, because it always resolves to true.
Value Identify the value that you want to evaluate the field for. See Setting Values in the Process Builder on page 5
for details.
5. If you selected “Formula evaluates to true,” define the formula.

• To insert a field, click Insert Field, choose a field, and then click Insert.
• To insert a function, click Insert Function, choose a function, and then click Insert.
• To insert an operator, open the Insert Operator drop-down list, and then select the appropriate operator.
6. Optionally, at the bottom of the panel specify whether you need to execute the actions only if the record was created or edited to
meet criteria.
For details, see Set the Previously Met Condition on page 17.
Note: This setting is available only if the process starts when a record is created or edited and you selected “Filter conditions
are met” or “Formula evaluates to true.”
7. Click Save.
Tip: If you have one criteria node defined, and you delete it and then add a new criteria node in its place, the new node might
not appear on the canvas. If this happens, refresh your page.
IN THIS SECTION:
Set the Previously Met Condition
Specify whether you need to execute the actions only if the record was created or if the record was edited to meet criteria. If this
setting is enabled, the process checks whether the record was changed from not meeting criteria to meeting criteria.
Formula Limitations
Formulas that are used as conditions in a criteria node have some limitations. If a process contains an invalid formula, you can’t save
or activate the process.
16
Set the Previously Met Condition

Specify whether you need to execute the actions only if the record was created or if the record was
EDITIONS
edited to meet criteria. If this setting is enabled, the process checks whether the record was changed
from not meeting criteria to meeting criteria. Available in:
For example, you might not want the actions to be executed on the same record every time a user • Enterprise
makes minor updates to the Description field. • Performance
• Unlimited
Note: This setting isn’t supported if: • Developer
• Your process starts only when a record is created.
• Your process starts when a record is created or edited and the criteria node doesn’t
evaluate any criteria.
• The criteria node evaluates a formula, but the formula doesn’t include a reference to the
record that started the process.
If Yes is... Actions are executed if... Actions are not executed if...
Selected • The record was created. • The record’s current values meet the filter criteria, and
• The record was updated. Its current values meet the the record’s most recent previous values met the
filter criteria, and its most recent previous values did criteria.
not meet the filter criteria. • The record’s current values don’t meet the filter criteria.
Deselected • The record was created. The record’s current values don’t meet the filter criteria.
• The record was updated, and its current values meet

the filter criteria.
Formula Limitations
Formulas that are used as conditions in a criteria node have some limitations. If a process contains
EDITIONS
an invalid formula, you can’t save or activate the process.
All formulas that are used in a criteria node must: Available in:
• Enterprise
• Return true or false . If the formula returns true , the associated actions are executed.
• Performance
• Not contain more than 3,000 characters. • Unlimited
• Not contain an unsupported function. • Developer
Note:
• You can check whether fields have changed by using the ISCHANGED formula function.
This beta functionality doesn’t support text or picklist fields, and the way that you
implement this check might change in an upcoming release.
• Processes evaluate picklist fields as if they’re text fields, so some functions that normally
support picklists may not support those fields.
There must be a space between the function’s parentheses and the contents of the parentheses. For example, you’ll get an error for
TEXT([Account].LastModifiedDate) but not for TEXT( [Account].LastModifiedDate ) .
17
Using Process Builder (Beta) Add Actions to Your Process
Unsupported Functions
If a formula in a process uses any of the following functions, the formula will return null .
• GETRECORDIDS
• IMAGE
• INCLUDE
• INCLUDES
• ISNEW
• ISPICKVAL
• PARENTGROUPVAL
• PREVGROUPVAL
• PRIORVALUE
• REQUIRE SCRIPT
• VLOOKUP
For a complete list of operators and functions for building formulas in Salesforce, see Formula Operators and Functions Overview.
Add Actions to Your Process

After you’ve defined a criteria node, define the actions that are executed when the criteria are met.
EDITIONS
You can add up to 10 immediate actions and 10 scheduled actions to a given criteria node.
An action group can consist of a combination of immediate and scheduled actions. Immediate Available in:
actions are executed once evaluation criteria are met. Scheduled actions are executed at a specified • Enterprise
time. For example, Salesforce can automatically send an email reminder to the account team if a • Performance
high-value opportunity is still open ten days before the specified close date. • Unlimited
• Developer
Tip: Consider planning your process before you add criteria nodes and add actions to each
node. After you add actions, the only way to reorder them is to delete them and start over. If
you want to delete an action, select the action in the canvas to open the side panel for that USER PERMISSIONS
action. Then click Delete at the bottom of the side panel.
Before you begin, consider whether you want this action to be executed immediately or at a specific processes:
time. If you want to execute the action at a specific time, identify when those actions should be • “Manage Force.com
executed. Flow”
1. Click Add action. AND
2. Select the type of action to create, and then fill out the fields to define the action. “View All Data”
IN THIS SECTION:
Create a Record from a Process
Create a record by manually entering values or by using the values of related records.
Create a Chatter Post from a Process
Post to the feed of a user, a Chatter group, or the record that started the process.
Use a Quick Action from a Process
Create a record, update a record, or log a call by using an object-specific or global action that you or another administrator created
for your organization.
18
Launch a Trigger-Ready Flow from a Process

Launch a flow from your process to automate complex business processes—create flows to perform logic and have events trigger
the flows via processes—without writing code.
Send an Email from a Process
Easily send an email from a process by using an email alert. Email alerts are configured outside of the Process Builder and contain
the standard text, list of recipients, and template for an email.
Submit a Record for Approval from a Process
Submit the record that started the process for approval.
Update Records from a Process
Update one or more records—that are related to the record that started the process—by manually entering values or by using the
values from related records.
Specify When Your Actions Should Execute

If you want some actions to be executed at a specific time, first define the schedule for those actions.
EDITIONS
Note: You can add scheduled actions only if:
Available in:
• The process starts when a record is created. • Enterprise
• The process starts when a record is created or edited and the criteria for this action group • Performance
has the previously met condition set. • Unlimited
Scheduled actions are complex features with several limitations. • Developer
Each action group that supports scheduled actions can have one schedule. For example, you can’t
schedule some actions to be executed one day from now and other actions to be executed three USER PERMISSIONS
days from now.
To identify when an action group’s scheduled actions should be executed: processes:
1. In an action group that supports scheduled actions, click Define the schedule. • “Manage Force.com
Flow”
2. If you need to schedule actions to be executed based on a date/time field on the record that
started the process: AND
“View All Data”
a. Leave the first radio button selected.
b. Click the drop-down list on the right side of the panel, and then select the field that you
want to use to scheduled the action—such as the date the record was created or modified.
c. Click Insert.
d. Specify a number of days or hours before or after the field.
If the criteria for this action group are still met when this time occurs, Salesforce executes the scheduled actions.
3. If you need to schedule actions to be executed a certain number of days or hours from when the process is executed:
a. Select the second radio button.
b. Specify the number of days or hours from when the process is executed.
If the criteria for this action group are still met when this time occurs, Salesforce executes the scheduled actions.
4. Click Save.
19
Create a Record from a Process

Create a record by manually entering values or by using the values of related records.
EDITIONS
After you’ve created an action and selected “Create a Record” for the type, fill in the relevant fields
to add the action to your process. The new record’s Created By field will be set to the user Available in:
who started the process—by creating or editing a record. • Enterprise
• Performance
Warning: If you create processes to replace any workflow rules, make sure you delete those • Unlimited
workflow rules when you activate the equivalent processes. Otherwise, both workflow rules • Developer
and processes will fire and cause unexpected results, such as overwritten records or redundant
email messages. Do the same if you create processes to replace any Apex triggers.
USER PERMISSIONS
1. Enter a name for this action.
This text appears on the canvas and helps you differentiate this action from others in your To create, edit, or view
process. The name is truncated to fit on the canvas. processes:
2. For Object , start typing and then select the object that you want to create a record for. Flow”
Note: You must select the object from the search results. If you type Case and don’t AND
select “Case” from the results, the value is considered invalid. “View All Data”
When you select an object, at least one row appears to allow you to set field values for the new
record.
Warning: Rows appear automatically for fields that are required by the API. You might need to provide values for other fields.
We recommend that you refer to your organization's page layouts to determine which fields are required.
3. Click Add Row to enter values for other fields.

4. Set the record’s field values.
Field Start typing, and then select the field whose value you want to set.
Value Set a value for the field by using the text entry field to manually enter a value or the field picker to use a field value from
a related record. See Setting Values in the Process Builder on page 5 for details.
5. Click Save.
20
Create a Chatter Post from a Process

Post to the feed of a user, a Chatter group, or the record that started the process.
EDITIONS
This action is available only if your organization has Chatter enabled. For details, see “Turning On
Chatter” in the Salesforce Help. Available in:
• Enterprise
• Performance
IN THIS SECTION:
• Unlimited
Post to a User’s Chatter Feed from a Process • Developer
Post to the feed of a user by identifying a specific user in your organization or a User lookup
field on a record.
USER PERMISSIONS
Post to a Chatter Group from a Process
Post to the feed of a specific Chatter group. To create, edit, or view
processes:
Post to a Record’s Chatter Feed from a Process
Post to the feed of the record that started the process. Flow”
AND
“View All Data”
Post to a User’s Chatter Feed from a Process

Post to the feed of a user by identifying a specific user in your organization or a User lookup field
EDITIONS
on a record.
After you’ve created an action and selected “Post to Chatter” for the action type, fill in the relevant Available in:
fields to add the action to your process. The feed item will appear as if the user who started the • Enterprise
process—by creating or editing a record—created the post. • Performance
• Unlimited
Warning: If you add a Post to Chatter action to a process, and later disable Chatter, you • Developer
won't be able to open the process. If the feed that the process tries to post to isn't available
when the process is triggered (for example, because the user is now inactive), the user sees
an error and the process fails. USER PERMISSIONS
1. Enter a name for this action. To create, edit, or view
This text appears on the canvas and helps you differentiate this action from others in your processes:
process. The name is truncated to fit on the canvas. • “Manage Force.com
Flow”
2. In the Post to field, select User.
AND
3. For User , select where you want to find the user. “View All Data”
4. Based on your selection for User , search for or browse for the user whose feed you want to
post to.
You must select the user from the results. If you type John Smith and don’t select the corresponding search result, the value is
considered invalid.
When you select a user from a record, you must ultimately select a field that contains a user’s ID—for example, Owner ID or
User ID .
5. Fill out the message that you want to post. Use the fields above the text box to mention a user or group, add a topic, or insert a
merge field into the message.
The message can contain up to 5,000 characters.
21
You can only reference topics that already exist. If you reference a merge field and that field doesn’t have a value, it appears as a
blank value.
6. Click Save.
Post to a Chatter Group from a Process

Post to the feed of a specific Chatter group.
EDITIONS
After you’ve created an action and selected “Post to Chatter” for the action type, fill in the relevant
fields to add the action to your process. The feed item will appear as if the user who started the Available in:
process—by creating or editing a record—created the post. • Enterprise
• Performance
Warning: If you add a Post to Chatter action to a process, and later disable Chatter, you • Unlimited
won't be able to open the process. If the feed that the process tries to post to isn't available • Developer
when the process is triggered, the user sees an error and the process fails.
USER PERMISSIONS
This text appears on the canvas and helps you differentiate this action from others in your
process. The name is truncated to fit on the canvas. To create, edit, or view
processes:
2. In the Post to field, select Chatter Group. • “Manage Force.com
3. For Group , search for the Chatter group whose feed you want to post to. Flow”
You must select the group from the results. If you type All Universal Containers AND
and don’t select the corresponding search result, the value is considered invalid. “View All Data”
4. Fill out the message that you want to post. Use the fields above the text box to mention a user
or group, add a topic, or insert a merge field into the message.
blank value.
5. Click Save.
22
Post to a Record’s Chatter Feed from a Process

Post to the feed of the record that started the process.
EDITIONS
You can post to the record’s Chatter feed only if feed tracking is enabled for the object that the
process is associated with. The feed item will appear as if the user who started the process—by Available in:
creating or editing a record—created the post. • Enterprise
• Performance
After you’ve created an action and selected “Post to Chatter” for the action type, fill in the relevant
• Unlimited
fields to add the action to your process.
• Developer
Warning: If you add a Post to Chatter action to a process, and later disable Chatter, you
won't be able to open the process. If the feed that the process tries to post to isn't available
USER PERMISSIONS
when the process is triggered (for example, because the user is now inactive), the user sees
an error and the process fails. To create, edit, or view
1. Enter a name for this action. processes:
Flow”
process. The name is truncated to fit on the canvas.
AND
2. In the Post to field, select This Record. “View All Data”
3. Fill out the message that you want to post. Use the fields above the text box to mention a user
or group, add a topic, or insert a merge field into the message.
blank value.
4. Click Save.
Use a Quick Action from a Process

Create a record, update a record, or log a call by using an object-specific or global action that you
EDITIONS
or another administrator created for your organization.
In order to use an object-specific action or global action from a process, those actions must exist Available in:
in your organization. • Enterprise
• Performance
If your organization is using object-specific and global actions to help your users more easily create
• Unlimited
and update records, you can also use those actions in your process. When you use these quick
• Developer
actions in a process, you can only set values for fields that are part of the action's layout. If you don’t
already have one of these actions created, see “Creating Global Actions” or “Create Object-Specific
Actions” in the Salesforce Help for details.. USER PERMISSIONS
After you’ve created an action and selected “Quick Actions” for the type, fill in the relevant fields to
add the action to your process. The new or updated record will appear as if the user who started
processes:
the process—by creating or editing a record—created or updated it.
1. Enter a name for this action. Flow”
This text appears on the canvas and helps you differentiate this action from others in your AND
process. The name is truncated to fit on the canvas. “View All Data”
23
2. Filter to specify the kind of action you want to use.
Filter Search By Lets You Search Through

Global actions All global actions in your organization. You then filter even further by selecting the Type of actions that you
need to search through.
Object All object-specific actions in your organization that are associated with a certain Object Name . Global
actions can’t be filtered by object.
Type All object-specific and global actions in your organization based on the type, such as Create a Record or Log
a Call.
• If you selected Global actions or Type, for Type select the specific type of quick action that you want to use.
• If you selected Object, for Object search for and select the object that you want to filter by. You see only actions whose
Object Name is the selected object.
3. For Action , search for and select the action that you want to use.
4. Set field values for the action.
Rows that appear automatically represent the action’s required fields. To set values for the action’s optional fields, click Add Row.
Warning: Be careful not to remove required rows. If the action doesn’t set values for required fields, the user who starts the
process—by creating or editing a record—sees an error when the process tries to execute this action. If you accidentally
remove rows for a required field, you can see which fields are required by looking at the action’s layout.
If the action doesn’t have any required fields, a row appears with an empty Field .
You can set values for only fields that are included in the action’s layout.
Value Set a value for the field by using the text entry field to manually enter a value or the field picker to use a field
value from a related record. See Setting Values in the Process Builder on page 5 for details.
5. Click Save.
24
Launch a Trigger-Ready Flow from a Process

Launch a flow from your process to automate complex business processes—create flows to perform
EDITIONS
logic and have events trigger the flows via processes—without writing code.
In order to launch a trigger-ready flow from a process, you must create and activate the flow. For Available in:
details, see “Create a Flow” in the Salesforce Help.. • Enterprise
• Performance
• Unlimited
This text appears on the canvas and helps you differentiate this action from others in your • Developer
2. For Flow , search for and select the flow that you want to launch from this process. USER PERMISSIONS
Only active, trigger-ready flows are available.
3. Optionally, click Add Row to set values for the flow’s variables. processes:
Flow Start typing, and then select the variable whose value you want to set. Flow”
Variable You can set values for any variables in the flow that have Input/Output AND
Type set to Input Only or Input and Output. sObject variables and sObject “View All Data”
collection variables aren’t supported.
Value Set a value for the flow variable by using the text entry field to manually
enter a value or the field picker to use a field value from a related record. See
Setting Values in the Process Builder on page 5 for details.
• For collection variables, you must use the text entry field to specify a
value that matches the collection variable’s data type.
• For sObject variables, you must use the field picker to select an ID field
for a record whose object type matches the sObject variable’s object
type.
• For sObject collection variables, you must use the field picker to select
a related list whose object type matches the sObject collection variable’s
object type.
Note: If the related list is empty when the flow tries to populate
the sObject collection variable with field values from those
records, the process fails.
4. Click Save.
25
Send an Email from a Process

Easily send an email from a process by using an email alert. Email alerts are configured outside of
EDITIONS
the Process Builder and contain the standard text, list of recipients, and template for an email.
In order to send an email from a process, you must create the email alert. Available in:
• Enterprise
You can use only email alerts that are associated with the same object that the process is associated
• Performance
with. The record that started the process is used as the starting point for any merge fields that are
• Unlimited
used in the email alert.
• Developer
After you’ve created an action and selected “Email Alerts” for the type, fill in the relevant fields to
add the action to your process.
USER PERMISSIONS
This text appears on the canvas and helps you differentiate this action from others in your To create processes:
process. The name is truncated to fit on the canvas. • “View All Data”
2. For Email Alert , type two or more letters to search for the email alert that you want to
use to send an email.
3. Click Save.
Submit a Record for Approval from a Process

Submit the record that started the process for approval.
EDITIONS
After you’ve created an action and selected “Submit for Approval” for the type, fill in the relevant
fields to add the action to your process. Available in:
• Enterprise
Only the record that started the process will be submitted. You can’t submit any related records
• Performance
for approval.
• Unlimited
1. Enter a name for this action. • Developer
USER PERMISSIONS
2. For Approval Process , indicate whether you need to submit the record through the
default approval process or through a specific approval process. To create, edit, or view
processes:
The process fails if: • “Manage Force.com
• The record is submitted to the default approval process, and there are no active approval Flow”
processes for the record’s object type. AND
• The record is submitted to the default approval process, and it doesn’t meet the criteria for “View All Data”
any of the approval processes for the record’s object type.
• The record is submitted to a specific approval process, and it doesn’t meet the entry criteria.
3. If you need to submit the record to a specific approval process:

a. Search for and select the approval process.
b. Indicate whether you need to skip the entry criteria for the approval process.
4. For Submitter , identify who should receive notifications about the approval request.
26
Value Description
Current User The user who triggered the process by creating or editing a record.
User Field from a Record The user ID that’s stored in a field value on the record that’s being submitted for approval or another
record.
Other User A specific user in your organization.
If the submitter isn’t an allowed initial submitter on the approval process that runs, the process fails. Make sure that the initial
submitters for the approval processes that are related to this object include all users who could trigger this process. For details about
setting the initial submitters for an approval process, see Creating Approval Processes.
5. If necessary, enter submission comments.

Submission comments appear in the approval history for the specified record. This text also appears in the initial approval request
email if the template uses the {!ApprovalRequest.Comments} merge field.
6. Click Save.
Update Records from a Process

Update one or more records—that are related to the record that started the process—by manually
EDITIONS
entering values or by using the values from related records.
After you’ve created an action and selected “Update Records” for the action type, fill in the relevant Available in:
fields to add the action to your process. The records’ Last Modified By field will be set to • Enterprise
the user who started the process—by creating or editing a record. • Performance
• Unlimited
• Developer
USER PERMISSIONS
2. For Object , open the drop-down list, select the record or records that you need to update,
and then click Insert. To create, edit, or view
You can update only the record that started the process or records that are related to it. processes:
• To update the record that started the process, select the object name in the far left column. Flow”
AND
“View All Data”
27
• To update a record that’s related to the record that started the process, select one of the field names in the second column.
If you select a field that ends in “ID,” you’re selecting a single record. This field name corresponds to a lookup field on the original
record. For details on lookup fields, see Custom Field Types.
For example, if a case record started the process and you select Account Id , this action updates the account that’s associated
with the case.
If you select a plural item that doesn’t end in “ID,” you’re updating all the records of that object type that are related to the record
that started the process. This plural item corresponds to child records of the original record, which might appear in a related list
on the original record. For details on related lists, see Customizing Page Layouts.
For example, if you select CaseComments, this action updates all the case comments that are related to the case.
28
• To update fields on a related record, click next to a field (ending in “ID”) to access that record’s fields.
For example, let’s say that, for a process that evaluates a case record (1), you want to update all contacts that are related to the
case’s parent account. Click next to Account ID (2), then Contacts (3), and then Insert.
3. Click Add Row for each additional field value that you need to define. Click to remove unnecessary rows.
4. Specify the new field values.
You can assign values to fields only on the record or records that you identified in the Object field. Use a separate
Update Records action to update fields on related records.
Value Set a value for the field by using the text entry field to manually enter a value or the field picker to use a field value from
a related record. See Setting Values in the Process Builder on page 5 for details.
5. Click Save.
29
Using Process Builder (Beta) Managing Processes
Managing Processes
To manage a process, from Setup, click Create > Workflow & Approvals > Processes.
EDITIONS
From the process management page, you can:
Available in:
• Edit a process
• Enterprise
• Create a process • Performance
• Delete an inactive process • Unlimited
• See the statuses of your existing processes • Developer
From the Process Builder, you can:

• Activate the process USER PERMISSIONS
• Edit the process’s properties To manage processes:
Flow”
AND
“View All Data”
Process Status
Each process has a status that determines whether the process can be edited, activated, or deleted.
EDITIONS
Status Description Editable? Available in:
Active The process has been activated. No • Enterprise
• Performance
You can’t make changes to an active process. However, when you • Unlimited
open an active process (by clicking Edit on the process management • Developer
page), you can click Save As to save it as a new draft process. Then
you can make any necessary changes to the new draft process and
then activate it. Don’t forget to deactivate the original process if
appropriate.
Draft The process is inactive and can be activated. Yes
InvalidDraft The process is inactive, and it doesn’t have a trigger defined, so it Yes
can’t be activated. After you define the process’s trigger, the status
changes to Draft.
Obsolete The process was deactivated. No

You can’t make changes to or activate an obsolete process. However,
when you open an obsolete process (by clicking Edit on the process
management page), you can click Save As to save it as a new draft
process. Then you can make any necessary changes to the new draft
process and then activate it.
30
Using Process Builder (Beta) Activate a Process
Activate a Process
Salesforce doesn’t start using a process to evaluate records as they’re created or edited until you
EDITIONS
activate it.
After you activate a process, you can no longer edit that process. However, you can click Save As Available in:
to save the process as a new draft process. • Enterprise
• Performance
You can’t activate a process unless it has:
• Unlimited
• At least one defined criteria node • Developer
• At least one defined immediate or scheduled action
1. From Setup, click Create > Workflow & Approvals > Processes. USER PERMISSIONS
2. Next to the process that you need to activate, click Edit.
To activate or deactivate
3. Click Activate. processes:
After you’ve activated your process, consider creating or editing test records that will start the • “Manage Force.com
process to make sure it’s working correctly. If you do, remember to delete those test records or Flow”
return them to their previous values once you’ve confirmed that your process works as designed. AND
If you later want Salesforce to stop using a process to evaluate records as they’re created or edited, “View All Data”
open the active process and click Deactivate.
Delete a Process
If you no longer need to use a process that you’ve defined, you can delete it. You can delete processes
EDITIONS
with a status of Obsolete, Draft, or InvalidDraft, but you can’t delete active processes.
To delete an active process, you must first deactivate it and then wait for 12 hours. If a process has Available in:
any scheduled actions, it can’t be deleted until those pending actions have been executed or • Enterprise
deleted. • Performance
• Unlimited
1. From Setup, click Create > Workflow & Approvals > Processes.
• Developer
2. Click Del for the process that you need to delete.
USER PERMISSIONS
To delete processes:
Flow”
AND
“View All Data”
31
Using Process Builder (Beta) Delete Unexecuted Scheduled Actions
Delete Unexecuted Scheduled Actions

If you no longer need to wait for a process’s scheduled actions to be executed—for example,
EDITIONS
because you need to delete the associated process—you can delete the unexecuted group of
scheduled actions. Available in:
1. From Setup, click Create > Workflow & Approvals > Flows. • Enterprise
The Waiting Interviews related list displays any unexecuted scheduled actions in your • Performance
organization, as well as any waiting flow interviews. • Unlimited
• Developer
2. For each unexecuted group of scheduled actions that you want to delete, click Del.
You can identify the correct row by the Flow Name field, which corresponds to the process’
USER PERMISSIONS
Process Name .
To delete unexecuted
scheduled actions:
Flow”
Troubleshooting Your Processes

Use these tips to help solve problems that arise when you’re working with processes.
EDITIONS
Available in:
Errors Received in the Process Builder • Enterprise
The API names for criteria nodes and actions are created in the background. When you create or • Performance
update processes, you might see error messages that reference those names to help you identify • Unlimited
specifically where the problem occurred. • Developer
API Name Description

processName _myRule_ x • processName is the API name for the entire process.
• x is the number of the criteria.
For example, Process1_myRule_2 corresponds to the
second criteria node in a process with an API name of
“Process1.”
processName_myRule_x_Ay • processName is the API name for the entire process.

• x is the number of the criteria.
• y is the number of the action.
For example, Process1_myRule_2_A1 corresponds
to the first action that’s associated with the second criteria
node in a process with an API name of “Process1.”
32
Using Process Builder (Beta) Troubleshooting Your Processes
API Name Description

myVariable_current. field field is the name of the field that’s referenced. myVariable_current refers
to the field values that the record had when it started the process.
For example, myVariable_current.Id corresponds to the record’s field
value for Id when the record started the process.
myVariable_old. field field is the name of the field that’s referenced. myVariable_old refers to
the most recent previous values of the record that started the process.
For example, myVariable_old.Id corresponds to the record’s field value for
Id immediately before the record started the process.
For example:
process_myRule_2 (Formula) - The element has an invalid reference to
“myVariable_current.AnnualRevenue”.
• process_myRule_2 refers to the second criteria of your process. (Formula) signifies that the problem is in the criteria
node’s formula.
• myVariable_current.AnnualRevenue refers to the value for the field AnnualRevenue when the record started
the process.
Note: Error or warning messages might refer to a “flow” instead of a “process.” Those messages still apply to your process.
Errors Received after a Process Starts Evaluating a Record

When a user performs an action that triggers a process (such as creating a record), and that process fails:
• The user sees a page with this error: “Workflow Action Failed to Trigger Flow.”
• The administrator who created the process receives an email with details about what went wrong. The subject line is:
Unhandled process fault from Visual Workflow : Process_Name : Error .
Use debug logs to find information about your running processes. From Setup, click Monitoring > Debug Logs or Logs > Debug
Logs, create a new debug log, and configure your filters to include the WORKFLOW category, at a log level of FINER. For details, see
“Monitoring Debug Logs” in the Salesforce Help.
33
INDEX
A L
Accessibility 9 Limitations 7
Actions Limitations, formula 17
create a record 20 Limits
define 18 Apex governor 7
post to Chatter 21–23 shared with rules 7
schedule 10, 19 shared with Visual Workflow 7
send email 26
submit for approval 26 M
update records 27 Manage 30
use a global action 23, 25
use an object-specific action 23, 25 O
Activate 31 Overview 1
C P
Considerations Process tool comparison 2
activation 12 Properties, define 13
administration 12
design 9 R
limits 7 Requirements 7
scheduled actions 10
Create 13 S
Critera Set values 5
formula limitations 17 Statuses 30
Criteria System requirements 7
define 15
set previously met condition 17 T
Troubleshooting 32
D
Delete 31 U
Delete, unexecuted scheduled actions 32 User interface 4
E W
Example 2 When to start, define 14
34

Salesforce Process Builder Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Salesforce Process Builder Guide

Uploaded by

Copyright:

Available Formats

Using Process Builder (Beta)

Salesforce.com, Winter ’15

USING PROCESS BUILDER (BETA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Process Builder Overview

When Should I Use a Process?

Sample Process: Opportunity Management

Understanding the Process Builder User Interface

Button Bar (1)

• One or more criteria nodes (4)

• One or more actions (5)

Setting Values in the Process Builder

Text Entry Field

Process Limits and Considerations

Description Per-Organization Limit

Total flows and processes 1000

Active flows and processes 500

Apex Governors and Limits for Processes

Description Per-Transaction Limit

Total number of records retrieved by SOQL queries 50,000

Total number of DML statements issued 150

Total number of records processed as a result of DML statements 10,000

Process Builder Accessibility Considerations

Process Design Considerations

Process Scheduled Actions Considerations

Transactions and Scheduled Actions

• You can’t set a schedule to zero days or hours.

• Salesforce ignores schedules that reference null field values.

Process Administration Considerations

Process Activation Considerations

– Deactivating Self-Service Portal, Customer Portal, or partner portal users

Define the Process Properties

Description Optional. A description for your process.

Identify Which Records to Evaluate

Add Process Criteria

If you need... Select

To evaluate the record by using a formula. Formula

c. If you need to remove unnecessary rows, click .

d. Define the field values that you need to evaluate.

Operator The available operators depend on the field’s data type.

5. If you selected “Formula evaluates to true,” define the formula.

Set the Previously Met Condition

• The record was updated, and its current values meet

Add Actions to Your Process

Launch a Trigger-Ready Flow from a Process

Specify When Your Actions Should Execute

Create a Record from a Process

3. Click Add Row to enter values for other fields.

Create a Chatter Post from a Process

Post to a User’s Chatter Feed from a Process

Post to a Chatter Group from a Process

Post to a Record’s Chatter Feed from a Process

Use a Quick Action from a Process

2. Filter to specify the kind of action you want to use.

Filter Search By Lets You Search Through

Launch a Trigger-Ready Flow from a Process

Send an Email from a Process

Submit a Record for Approval from a Process

3. If you need to submit the record to a specific approval process:

Other User A specific user in your organization.

5. If necessary, enter submission comments.

Update Records from a Process

From the Process Builder, you can:

Draft The process is inactive and can be activated. Yes