SK SKYVVA Documentation

8. How to send big size data from Salesforce to Mule without hitting the governor limit?

This operation works like a HTTP listener but the additionally it can gather multiple package of messages before sending to the next processor of mule. The number of message for a request decided by the header information provided with the request. It supports following header information along with the request:

Content-Type : It only supports application/json TransactionId : Unique value for one bulk of messages. (e.g We have 3 message to send then it should be same for all of that three messages). CurrentPackage : It should have the current package number of the message from a bulk messages. (It should be start in ascending order) CompleteNumberOfPackage: Total number of package contained in a bulk message. Use-case :

1st Message : [{ "message": "1st message"}]

2nd Message: [{ "message": "2nd message", "details" : {"status": "success"} }]

3rd Message: [{ "message": "Final message", "details" : {"status": "Completed"} }]

The output will be written to a file with bellow content. [ { "message": "1st message" }, { "message": "2nd message", "details": { "status": "success" } }, { "message": "Final message", "details": { "status": "Completed" } } ] Mule configuration for Collector operation: Create a HTTP Listener using Skyvva Collector

Create a flow using the above collector configuration

Configure the path for which you want to configure the collector.

Open this article in the interactive viewer →