Building and deploying from Decision Designer
Automation Decision Services provides the embedded build service, which allows you to trigger building and deploying a decision service in a selected version of your project from Decision Designer.
Before you begin
The decision runtime must be installed.
For more information about the installation, see Preparing to install Automation Decision Services.
About this task
When decision services are deployed successfully, they can be later used as automation services, or can be used by the decision runtime for executing decisions. Client applications can call decision services by using the runtime REST API.
- Decision services are ready to be published as automation services.
Automation services become discoverable across Business Automation Studio and can be used in other applications. For more information about automation services, see Business automations.
- Decision service archives are generated for decision services, and deployed to the decision
runtime.
Decision service archives that are built from Decision Designer are deployed to the decision runtime in the deployment space ID (deploymentSpaceId) named
embedded.
Procedure
Results
The value for the decisionId parameter is displayed next to the deployment status. This value is used for executing the decision service later. For more information, see Executing decision services.
- Click the horizontal three-dot Test icon
for the decision service
in the Deploy tab. - Swagger UI opens and you can start testing the deployed decision service.
For more information about the runtime REST API, see Runtime REST API reference.
What to do next
- You can now publish the decision service as an automation service in Business Automation Studio. For more information, see Publishing decision services as automation services.
- The decision service is now ready to be used by the decision runtime to execute decisions. For more information, see Executing decision services.