- Stage Event depends on Event-Driven Architecture which empowers applications to convey inside and outside of Salesforce.
- Stage occasions depend on the distribute/buy-in model and work straightforwardly with a message transport that handles the line of approaching occasions and cycles tuning in for them.
- This is underlying constant combination designs in the Salesforce Platform which assists with lessening highlight point joining.
Conveying Custom Notifications with Platform Events
- Stage occasions are essential for Salesforce's venture informing stage. The stage gives an occasion driven by informing engineering to empower applications to convey inside and outside of Salesforce.
- Prior to jumping into stage occasions, investigate what an occasion-based programming framework is.
Characterizing Your Custom Platform Event
- Custom stage occasions are sObjects, like custom items. Characterize a stage occasion similarly you characterize a custom item.
Distributing Platform Events
- After a stage occasion has been characterized in your Salesforce organization, distribute occasion messages from a Salesforce application utilizing cycles, streams, or Apex or an outside application utilizing Salesforce APIs.
Don't forget to check out: Salesforce Connect - Quick Start | Apex Developer Guide
Buying into Platform Events
- Get stage occasions in measures, streams, Apex triggers, or CometD customers.
Testing Your Platform Event in Apex
- Add Apex tests to test stage occasion supporters. Before you can bundle or send Apex code, including triggers, to creation, it should have tests and adequate code inclusion. Add Apex tests to give code inclusion to your triggers.
Encoding Platform Event Messages at Rest in the Event Bus
- For expanded security, you can empower encryption of stage occasion messages while they're put away in the occasion transport in a Shield Encryption organization.
Screen Platform Event Publishing and Delivery Usage
- To get useful information for occasion distributing and CometD-customer conveyance, question the PlatformEventUsageMetric object.
- Utilization information is accessible throughout the previous 24 hours, finishing at the most recent hour, and for authentic day-by-day use.
Stage Event Considerations
- Find out about exceptional practices identified with characterizing, distributing, and buying into stage occasions.
- Figure out how to test stage occasions. What's more, get an outline of the different occasions that Salesforce offers.
- Look at stage occasion applications—a start to finish model utilizing streams, a Java customer, and test applications that cover business situations.
Here is some phrasing we ought to recall:-
Occasion: An adjustment of express that is significant in a business cycle.
Occasion message/Notification: A message that contains information about the occasion.
Occasion maker: The distributor of an occasion message over a channel.
Divert: A conductor wherein an occasion maker sends a message. Occasion shoppers buy into the channel to get messages. Additionally alluded to as occasion transport in Salesforce.
Occasion purchaser: An endorser of a channel that gets messages from the channel.
Check out another amazing blog by Manish here: Custom Roll-up Summary on Account Object | Salesforce Developer Guide
ReplayId System Field and Event Retention
- Salesforce stores stage occasions for 24 hours. You can recover put away occasions in API customers yet not in Apex.
- Every occasion record contains a field, called ReplayID, that the framework populates after the occasion is distributed.
- Each replay ID is destined to be higher than the ID of the past occasion, yet not really adjoining for back-to-back occasions.
- You can recover all put-away occasions, or you can indicate the replay ID of an occasion as the gauge for the recovered part of occasions.