Compared
to workflow rules, process builder should be used to build more complex business
processes, such as use Apex to make web service callouts, using a script for a
customer call, Sort, iterate over several records, and use data from third party
services.
It is quite painful that it’s not possible to change the
order of the criteria nodes or the order of the actions of the process, the
only way of changing this is to start over the process.
Another pain point that we cannot see the scheduled time
based workflow under the time based workflow queue.
Multiple Rules in one Process and the enhanced Visual
Interface provides the flow of the business process and the visual diagrams
always helps users to understand the business without digging in to the
salesforce workflow rules individually.
What is a process builder?
·
Simple - Design with point and click NOT code,
·
Powerful - Five new actions not available in
workflows
·
Flexible - Build automated process that better
match how your business works
·
Visual - View your process in an intuitive
interface.
The following capabilities of a workflow could be replaced
with process builder’s features,
·
Email
·
Tasks
·
Field Update
·
Outbound Messages
The actions available through the process builder would
be.
·
Apex, - Executing an APEX business logic will
allows us to cater more complex business logic and enhance the scalability
factor. The apex class must have evocable method, eg: this should be a public
method.
·
Create a record – You can select the particular
object and provide the variables to be updated along with a single value or a
value form another object record.
·
Update any related record—not just the record or
its parent – functionality similar to create a record, excepts which updates
the existing one.
·
Use a quick action to create a record, update a
record, or log a call - Use this action type to invoke an object-specific or
global action that has already been created in your organization
·
Launch a flow—as an immediate or a scheduled
action – Only active flows would be possible and the flows should not relate
with any screens.
·
Send an email - Select an existing email alert
for the object that the process is associated with.
·
Post to Chatter – You can post to a User, Chatter
Group, or to the existing record, also we can use @mentions and add topics.
·
Submit for approval – This requires the Approval
Process and could be a default one or a Specific one and the submitter could be
current user, User field from a record or other user.

No comments:
Post a Comment