| Table of Contents |
|---|
1. Chaining Flows
This is a real use-case for an integration I do with my client. I have modified the concept to show you but the process is the same.
...
Firstly we will look at the website.
Mock Website https://jodiem.formtitan.com/origin/ft5f37318e1604833404141/origin/?device=Desktop#/
...
We are going to pretend this is the back end of the website
We have some properties and some brokers on the website
...
| Warning |
|---|
NOTE: Notifications ONLY work IF the user has cleared their notifications! More than 20 notifications and you don’t get “notified” |
The website is updated
...
2. Replace Wait
I have a DLRS that updates the Account from the value of the Properties relates.
...
| Note |
|---|
you would not use this scenario without a heap of DLRS updates on Account. |
The Flow triggered after the Property is set to Active
Property-AfterCreateUpdate-Active
...
All it does is publish the Platform Event.
This is doing exactly the same as setting a Wait element.
I’m using the same Platform Event.
Flow FlowControl-LGAStage
...
| Note |
|---|
Note you can’t do a condition on the Flow Trigger for Platform Events so I am using a decision. |
This way I could add more decisions and do different things for different Flow Stage values in my published PE. It all just depends on how awkward one flow would be to manage.
You could just create different Platform Events for different conditions also.
3. External System Updates
When the Property is sold a Platform Event is sent by the Website. It runs this Flow.
Flow PE-PropertySold
...
This is the Platform Event
...
Here is the REST API call that the Website will send to Salesforce by the authenticated Integration user.
...
This is mocked up in Postman.
When the API call happens, the flow runs
A notification is created
...
The Property is updated
...
Discount
Price Sold
Status
A Chatter post is created
...
4. Flow Error Alerts
The built in Platform Event of Flow Execution Error Event
Flow Flow Error NotificationFlow Error Notification
...
I have a Flow on the broker that is hard coded to cause an error for this example.
...
The ugly error message is displayed to the user
...
But they get a notification telling them what the issue is
...
(I hard coded “a garbage value” instead of the email address).