LinkedIn

OrderStatusChangedEvent - Salesforce Standard Platform Event fired during Order Status Changes

-

 A sales process is normally completed by placing an order and contracting the products. In most cases, the actual ordering will be happening in an external system and not in salesforce. So in this case it is important to send order-related changes to the external system as soon as its status is updated in salesforce.

Salesforce has introduced a new standard platform event to support this-  called OrderStatusChangedEvent. This is available as part of API version 51.0 and above.

Let us see this in detail:



How to enable OrderStatusChangedEvent 

Under Order Setting, we can enable this standard platform event:

Setup->Feature Settings->Sales->Order Setting->Enable Order Events


When this will be fired?

This standard platform event will be fired when:

1. Status is updated for an existing order

Supported Subscribers

OrderStatusChangedEvent can be subscribed internally and externally.


Subscribing through Flows

Let us see an example of how to subscribe to standard OrderStatusChangedEvent using Flows.

Use Case - Notify Account Owner when an order status is updated

1. Create New Flow

Create a new flow of type platform event-Triggered flow:



2. Choose platform event

Choose platform event as "Order Status Changed event"




3. Assign recipient List

Our requirement is to send a notification to Account Owner when order status is updated. So let us create a list variable to store Account owner email.


And add an assignment Logic to populate this variable with Account owner's email:


4. Send email Notification

Add an Action and select Send email.



Do the below assignment:

Body - Order status got updated to {!$Record.NewStatus} from  {!$Record.OldStatus} 

Subject - {!$Record.Order.OrderNumber} - Status got updated

Email Addresses (collection) - variable - emaillist


Final Flow looks like below and you can activate it.


5. Update Order status to verify email

Let us create a new account, contract, order and add order product.

Then try to update Order status from Draft to Activated. The account owner will be receiving a new email notification.


Email:


Subscribing through Streaming API(CometD)

Please refer to this blogpost to understand how to subscribe to salesforce platform events using comentD.

Using the same approach we can see OrderStatusChangedEvent subscription details.

Use the below command to subscribe to OrderStatusChangedEvent .

java -classpath target/emp-connector-0.0.1-SNAPSHOT-phat.jar com.salesforce.emp.connector.example.LoginExample <username> <password+sectoken> /event/OrderStatusChangedEvent

Since platform events are available for 24 hours in the queue, you can see all the published events till this time getting subscribed:


Advantages of Consuming Standard platform Event

1. Internally - We will be able to keep related operations asynchronous and will be able to take advantages of govornor limits and performance.

2. Externally - Multiple systems will be able to subscribe to the standard event and no need to define custom process/approach for integration.

In our next blog, we can see another useful standard platform event.


Comments

  1. Unknown30 April 2021 at 11:06

    This comment has been removed by the author.

    ReplyDelete
  2. Unknown30 April 2021 at 11:09

    Meera Hi,
    Thank you for your post!
    Can you elaborate further on the differences between using this event with Platform Event-Trigger Flow rather than, for example, using an after trigger Flow?

    ReplyDelete
    Replies
    1. Meera R Nair3 May 2021 at 00:08

      After trigger flow is synchronous execution - meaning, that operation is part of your current process, in our case order update. So this can affect, governor limits and save performance. But when you fire a platform event and then we use platform event based operations to do additional operations - it is getting executed in a separate thread. meaning asynchronously. For operations which consumes more time/governor limits - always asynchronous mode of execution is better.

      Delete
    2. Unknown3 May 2021 at 09:59

      Got it, thank you very much for your answer!

      Delete
  3. bhanu21 October 2021 at 08:07

    Nice and good article. It is very useful for me to learn and understand easily
    Salesforce CPQ Online Training Hyderabad
    Salesforce CPQ Online Training India

    ReplyDelete

Post a Comment

Popular posts from this blog

Subscribing to Salesforce Platform Events using External Java Client - CometD

-
Image
Platform Events follow event based Architecture, where multiple subscribers can subscribe to a published event in real time manner.  Below diagram shows the basic Architecture of the event-based communication Model: Event - This is a change in state for a business process Event Message - Data about the event Producer - Publisher of the event Event Bus - A communication and storage service for published events Event Consumer - A subscriber to the channel Platform events can be subscribed internally and also externally Platfrom events  - Internal Subscription Below are some scenarios in which you can consume platform events internally: 1. When we need to execute functionalities asynchronously to save govornor limits 2. To build a proper exception logging framework - You can find more details here  How to subscribe Internally? we can see more details about this in a different blogpost. Platfrom events  - External Consumption Many Organizations are moving to event-based integration appr
Read more

Salesforce Security - Restriction Rules and Scoping Rules

-
Image
1. Overview Salesforce provides a very effective security model where we always start with the most restrictive access and then open up access using additional mechanisms like sharing rules, and manual sharing based on the requirements.   But there might be scenarios where we need to restrict access based on specific criteria. Salesforce recently introduced 2 approaches to support this requirement. Those are restriction rules and scoping rules. Let us see this in detail. 2. Restriction Rules - Overview Using restriction rules we can apply an additional level of filter on top of records to which a specific user is having access. 3. Scoping Rules - Overview Scoping rules help to filter the default records visible for a user based on specific criteria. But it is not preventing access to other records. 4. Compare Restriction Rules and Scoping Rules 5. Restriction Rule - Example Company ABC is having Job Applications getting created through their company portal and synched to Salesforce. T
Read more

How to develop reusable Invocable Apex methods for Flows

-
Image
 Salesforce is adding many new features and capabilities to Flows. But there are still some scenarios where you need to call apex methods from Flows to execute complex operations - when Flow is not capable of doing that or the performance will be low when you implement that using flows. Let us see how we can build reusable apex methods for Flows. For this let us consider 2 sample scenarios: Scenario 1 - Quick Create Account/Contact I want to build a screen, where the user can select the object needs to be created, and then create a record of that object by entering the required details. Also if the record creation is getting failed, I want to create an exception record with details. Solution Let us see how we can utilize Apex action for this. For this first let us create an Apex Invocable method, which can accept a list of wrapper class as shown below: You can see, this invocable method is accepting a List of wrapper class variables and also returning a list of wrapper class variables.
Read more