Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Four ways to automate business processes

A brief summary of the four Sales

Tool

Information

Process Builder

  • The process builder tool has Has a visual designer and is useful if you have

  • Useful for multiple if/then statements in your process.Only creates records and will

  • Creates records but would not delete them. Can update

  • Updated fields in related records.

  • Can invoke other processes, launch a flow, and submit for approval.

  • Can post to Chatter, send an email alert, or send a custom notification

  • Starts when records change, can be invoked by another process, or when a platofrm platform event is received. Can be invoked by another process.

Flow Builder

  • The flow builder tool has Works with Pulsar

  • Has a visual designer.

  • Good for complex processes with multiple layers of evaluation.

  • Starts on a button or link click, on access to a page or tab, on access from a utility bar, when a process starts, or when Apex is called

  • What sets the flow builder apart is that it supports user interaction.

  • It cannot invoke other processes

  • Similar to the Process builder with except that it can send outbound messages without code and update any record, not just related records.

Workflow

  • The workflow tool is the simplest option and a good choice if you only have a single if/then statement in your process.

  • It only starts when a record is changed, and supports time-based actions.

  • The workflow can only create record tasks and only updates the record or its parent.

  • It can send outbound messages without code.

Approvals

  • The approvals tool is also good for a single if/then statement, but

  • it starts in more ways - when a user clicks a button or link, when a process or flow starts with a Submit for Approval action, or when Apex is called.

  • The approvals tool only creates record tasks, only sends email alerts, and can send outbound messages without code.

  • Like the workflow tool, the approvals tool only updates the record or its parent.

Which tools does Pulsar support?

Fully offline use

Pulsar only supports fully offline use for automation using one of the four tools mentioned above: the flow builder.Note -

When creating flows using the flow builder, save them as the Field Service Mobile Flow type. Pulsar fully supports mobile flows for offline use. If you save the flow as a screen flow, your flow will only run when online during a sync.

Offline initiation

For the process builder and approval tools only, you can initiate a process while offline, using a custom button, for instance, and mark a field on the object. The process would then watch for this change to the and kick off the process when you are back online. An example of this a Submit for Approval button.

Alternative solutions

If you want to use the other workflow solutions with Pulsar when you are completely offline, you will need to rewrite these pages or triggers using one of the two methods Pulsar has to offer. You can use Pulsar as a platform and HTML/Javascript or the Pulsar Settings Language (PSL) to create a custom Pulsar app to perform the same tasks offline.

Automation tips

  • Coordinate offline /and online record updatesif it , to avoid overwriting data.

  • If your process runs in SFS mobile app then will run in Pulsar, because they use the same engine.

  • If you use Apex triggers or want to send emails, you cannot do this while offline. The triggers will fire and the emails will send the next time you are online.

  • If you use Lightning pages, Visualforce pages, or Apex triggers do , they will not work with Pulsar. See the page about this...Refer to VisualForce, Lightning Components, and Apex Triggers.

  • When using the flow builder tool, a good rule of thumb is that if your automated process works in the Salesforce Field Service mobile app, then it will work in Pulsar.

Questions

Which process automation tool - https://help.salesforce.com/s/articleView?id=sf.process_which_tool.htm&type=5