Sometimes events on Salesforce need to be handled by an external system due to the scale or type of process being executed. Consider the use case of a user in Salesforce needing to get pricing for an order they are building in Salesforce while on the phone with a customer. The pricing logic already exists in a third-party system. Instead of creating this logic in Salesforce, it will be leveraged by making a request of the third-party system. The response, in this case the pricing, will be returned and stored back in Salesforce. What is the optimal solution

A trigger that upon saving

customer order, will make a real time callout saving the pricing back in Salesforce

Explanation:

Salesforce a software that is used to organise customer interactions in such a way that transactions between the company and customer is effectively managed by the software.

In the given scenario pricing needs to be handled by an external system. The response will be returned and stored back in Salesforce.

Instead of doing this manually the best solution will be to have an trigger that starts a real-time callout, saving the pricing back in the salesforce.

An trigger allows one to perform customised actions before or after an event. The action can be an update or deletion.

answer; blank(1); /// whitelisting; blank(2); // blacklisting;