Implement an external call when an existing function does not exist to cleanse, analyze, or transform data.

Be cautious when you implement an external call because the call can impact the performance of the MDM Hub and business entity service call response.

Identify when you want to use the external call. For example, run an external call when a user navigates from one child record to another or when the user clicks

Save

.

Define a separate class for each external call.

If you include the inParams process method parameter with the validateOnly property in an external call, ensure that you set the validateOnly property to one of the following values:

false or null. Runs the external call after the user clicks
Save
.
true. Runs the external call after the user updates a parent or child record and then navigates to another child record.

If you include custom properties in subsequent external calls up to the AfterEverything event, add the custom properties in the outParams process method parameter.

The final WriteCO.AfterEverything event during a save operation returns row IDs of parent and child records. If you require other data, call read business entity services.

Do not implement external calls for read operations because read operations occur during the following operations:

Search
Read before write
Read after write

Validate records through cleanse functions.

If you implement additional validation, perform the additional validation at the WriteCO.AfterEverything event when the validateOnly property is set to one of the following values:

false or null. For a base object.
true. For a child record.

Make a business entity services call from an external call similar to any external application that uses business entity services calls to read or write data.