You can automate business processes to save users' time and enforce consistency. Salesforce has point-and-click tools to easily automate your business processes. Learn how to use these tools with Pulsar to automate processes for offline useThis page aims to explain if any of these processes can be used offline within Pulsar.
Four ways to automate business processes
...
Tool | Information |
---|---|
Process Builder Can be initiated by Pulsar |
|
Flow Builder |
|
Workflow |
|
Approvals |
|
Which tools does Pulsar support?
Flow Builder Tool - Fully Offline
...
if you are running Salesforce Field Service within Pulsar.
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.flow can not run from within Pulsar. The reason is simple. Salesforce platform doesn’t allow users with restrictive permissions to query flow definitions but SFS mobile flow is designed to workaround this limitation. This is why both Pulsar and SFS mobile can query the definitions and run them offline with the flow engine implemented to function completely offline within each of these apps.
If you wanted to recreate a screen flow to run within Pulsar, 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. For more information, refer to:
Process Builder and Approval Tools - Offline Initiation
For the process builder and approval tools, you can initiate a process in Pulsar while offline. For example, you can use a custom button (Submit for Approval, for instance), and mark a checkbox field in the object indicating you would like to submit this record for approval. The process would then on the backend should be modified slightly to watch for this change to the field and kick off the process when you are online as the data syncs from Pulsar to Salesforce.
Workflow Tool - Custom Solution
...
...
Developer Tips
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.
Coordinate offline and online record updates or deletes, to avoid overwriting data. This is just the reality of dealing with a completely offline/disconnected system. The backend needs to recognize the actions were already taken by Pulsar when offline and skip repeating these actions when the data syncs from Pulsar to Salesforce.
If you want to send emails as part of your automation process, you cannot do really achieve this while offline. The emails will send be automatically sent by the process the next time you are onlinesync Pulsar.
If you use Lightning pages, Visualforce pages, or Apex triggers in your process automation, they will not work with Pulsar. Refer to VisualForce, Lightning Components, and Apex Triggers.