What would you use to save changes to an external entity?

The choice to use the Send external object activity for saving changes to an external entity is appropriate because this method is specifically designed to handle communications and data modifications with external systems or services. When working with external entities, the system typically communicates over APIs or other integration layers, and the Send external object activity streamlines this process.

This activity allows you to send updated data back to the external source, ensuring that changes made within the application are reflected in the external system. It effectively serializes the changes to the specified external entity format and transmits them to the external service, where they can be processed. This is crucial for maintaining data consistency between your Mendix application and the external data source.

In contrast, options like the Save Entity activity or Update Entity action are primarily geared towards internal entities within the Mendix application's domain model and do not apply to external systems. They handle interactions with data that is already part of your Mendix application and are not designed for directly connecting or altering data that exists outside of your Mendix environment.

The Publish changes command also focuses on sending notifications or updates related to entities within a Mendix application rather than managing or saving changes to external systems. Thus, the Send external object activity is the most fitting solution for this scenario