Calling published automation services
You can call automation services from the user interfaces of your business applications.
Automation services are published workflow automations that can be discovered and added to your business application (application) in a consistent way. You can also reuse existing process applications from traditional workflow capabilities or create an external automation service from the services in an OpenAPI or Swagger file.
Before you begin
- An automation must be published as an automation service in IBM Business Automation Studio before you can call them from your application.
About this task
Your application user interfaces are made up of pages, views, actions, and automation services. Actions and automation services provide you with the ability to call server-side logic from your user interface. Actions are usually implemented by more technical users to achieve automation functionality that is specific to your application. Think of actions as the customizable entities that can be used to achieve more complex automations. Whereas automation services are reused across the platform after they are published to Business Automation Studio. Automation services are added to applications from the component pane.
You can add synchronous or asynchronous automation services to your application. If your application invokes a synchronous automation service, the application will receive a response. You can think of synchronous as a two-way invocation. If your application invokes an asynchronous automation service, it is a one-way transaction where no response is captured.
Procedure
Results
The entry fields for your user interface are automatically generated based on your selections in the Call an automation service dialog, specifically the input and output parameters.