V r Cloud

  Understanding Salesforce Outbound Messages Outbound messaging allows you to specify that changes to fields within Salesforce can cause messages with field values to be sent to designated external servers. After you set up outbound messaging, when a triggering event occurs, a message is sent to the specified endpoint URL. The message contains the fields specified when you created the outbound message. Once the endpoint URL receives the message, it can take the information from the message and process it. Outbound messaging uses the  notifications()  call to send SOAP messages over HTTP(S) to a designated endpoint when triggered by a workflow rule.  Outbound messages need an endpoint URL which we need to mention while configuring outbound messages.  You can use a postman or any of the following to create your own endpoint. 1. Requestbin   2. Hookbin 3. Requestcatcher   4. Integration Playground for our example, we will use Integration Playground Defini...

Asynchronous Apex Triggers In Summer 19 release Salesforce introduce a new feature to process data using a combination of 'Asynchronous Apex Triggers' and Change Data Capture. Any DML on Salesforce records causes platform to start a series of calculations, run business logic and database updates, all these are called as an Apex Transactions. You can reduce the Apex transaction time to complete the business logic and limit constraints by decoupling resource-intensive, non-transactional logic from database transaction and execute asynchronously.  Asynchronous Apex triggers are change event triggers that run asynchronously after a database transaction is completed. They are ‘after-insert’ triggers and can be defined with the after insert keywords. They can be created the same way we create regular Apex triggers. You set the trigger to use a change event object instead of an sObject. The change event object name is suffixed with ChangeEvent. For example, Account change e...