An integration designed to modify data can be invoked from several locations within an Appian application. It can be called asynchronously within a process model using the dedicated "Call Integration" smart service. It can also be called synchronously from any expression using the a!integration() function. This allows it to be used directly in an expression rule or, very commonly, within the saveInto parameter of a SAIL interface component to trigger the data modification in response to user interaction.

A. Web API (GET): A Web API is an endpoint that exposes Appian functionality to external systems; it is not a location within Appian from which you call an integration.

C. Web API (POST, PUT, DELETE): Similar to the GET Web API, this object is an inbound endpoint. While it can execute an integration internally, it is not a location where a designer calls the integration from.

1. Process Model (D): "The Call Integration smart service is a powerful tool that allows you to start an integration from a process model."

Source: Appian Documentation

"Call Integration Smart Service".

2. Expression or Rule (B) & SAIL saveInto parameter (E): "You can call an integration from any expression using the a!integration() function. This allows you to call an integration from an interface

web API

or other expression." The documentation further clarifies its use in interfaces: "For example

you could use this function in the saveInto parameter of a button component..."

Source: Appian Documentation

"Calling an Integration".

3. SAIL saveInto parameter (E): The a!save function

used within saveInto

can execute an integration rule. "The value parameter [of a!save] is...evaluated and saved into the target...when the user interacts with the component." This evaluated value can be the result of an a!integration() call.

Source: Appian Documentation

"a!save() Function".