This site is in beta. We welcome your feedback
This Level 3 documentation and implementation diagram shows an example of the claim check pattern that depicts an event being published when a record is modified. The message body of the event is stored in a separate data store while the header, which contains a claim check, is passed to a subscriber. The subscriber then uses the claim check to retrieve the message body when it's ready to process the information.

Download Diagram
Open the template in Lucidchart (Lucidchart account required)

Pattern Overview

With the claim check pattern, instead of the complete representation of the transformed data being passed through the event bus, the message body is stored independently, while a message header containing a pointer to where the data is stored (a claim check) is sent to the subscribers. The main benefits of this pattern are lower data volumes being sent through the event bus and increased likelihood that messages will fit within the size limitations of the subscribing systems.

This is a Level 3 Documentation and Implementation diagram according to the Salesforce diagram framework.

Learn more by reading the Architect's Guide to Event-Driven Architecture with Salesforce.