LFS Version requirement: 12.64 or higher
Encouraging the use of our product, especially platform events, is crucial. Some users may hesitate to adopt platform events due to unfamiliarity, but we believe that providing the right resources can close this knowledge gap. By addressing these issues, we aim to help more users fully utilise platform events, enhancing their overall experience with our product.
The package includes a new flow designed to respond to the i42as__OrderEvent__c.
This flow is easily customisable by administrators, allowing for flexibility. Importantly, it starts in an inactive draft state, enabling administrators to adjust the logic to their needs before activation. Once tailored, the flow can be activated ensuring smooth integration of platform events into existing processes.
How to use the flow?
First, you need to add the logic you want to run when an event is received. Then you will only need to activate the updated flow version.
This flow is auto-launched which means that as soon as you activate it, it will listen to the events of i42as__OrderEvent__c type on the background and any time Limio publishes an event of this type, it will get evoked executing the defined logic.
In our example draft flow, we mapped event's order type value to the description of an asset record.
Note: this is for example purposes only and needs to be updated to meet your business case.
What fields does the event include?
The event's data model is available in the platform event definition in the setup. Field mappings for each order type are outlined in this document: i42as__OrderEvent__c Platform Event.
Comments
0 comments
Please sign in to leave a comment.