As many business processes span across a multitude of different systems and applications, a means to interact with these systems and applications is required in the business process management system. In SAP Build Process Automation, you use Actions to accomplish the integration. Application Programming Interfaces (APIs) from the source and target systems to interact with, are encapsulated as Actions within Actions projects. Those Actions projects are then held in an Actions projects library and from there, can be integrated into the business processes. This approach offers various advantages compared to direct API integration into the respective process:
- There is an abstraction of the API. The process developer does not need to know exactly about technical details of the API.
- APIs can be adjusted to the process developers needs, only exposing endpoints and data that is required or safe to use by the process developers.
- Actions can be configured once, and then be reused across different business process projects.
- Actions projects allow versioning and thus, make it easier to deal with changing process requirements or changing API versions.
As Actions rely on the OpenAPI Specification standard (https://spec.openapis.org/oas/v3.1.0#openapi-specification) for API definition, they aren't limited to APIs from SAP systems, but provide the option to integrate any API that is or can be described in the OpenAPI Specification. A large number of API definitions, especially for but not limited to SAP solutions, can be found in the SAP Business Accelerator Hub.
Note
You'll find additional information on APIs, specifically on SAP Build Process Automation APIs, and how to interact with them on a more technical level in unit API Integration of SAP Build Process Automation.Actions Editor
The Actions Editor lets you compose multiple Actions from an underlying API into an Actions project. Note that you don't have to include all possible parameters of an API endpoint as parameters in the respective Actions, and you also don't have to include all available response body fields in the response provided through the Action. By that, only information relevant to the business process can be included.
Once your Actions have been defined, the project needs to be released into a version and then published to the Actions library.
After APIs have been encapsulated in an Actions project and published to the library, adding them as action to a process is quite simple. Select the corresponding step type Actions and browse the Actions library. Select the action required in your process, and choose Add. Once the Action step is included in your process, make sure to define its parameters:
- Destination variable: A process variable that will hold the technical SAP BTP destination name to be used for accessing the underlying API at process runtime. This variable can be filled with a destination name during deployment of the process.
- Inputs: Mapping of process content to all parameters, that the action requires in order to be performed (for example, the Sales Order Number, when retrieving a Sales Order entry from an SAP S/4HANA system).
- Outputs: Overview of the Actions call result, as defined in the respective action.