Before you start

Decision Intelligence Client Managed Software includes Decision Designer, which is a development environment for creating decision services. In this tutorial, you use Decision Designer to define and run a decision service. Then, you expose your decision service and share your changes with your collaborators. You also look at assigning collaborators to your decision automation. After you further define your decision service, you share more changes, and then deploy the service to a runtime environment to run it in a Swagger UI:

You start by creating a decision automation to hold a decision service. A decision service uses decision artifacts to define a business decision:

• Decision model: Contains a diagram that has nodes for decisions and data input. The decision nodes hold the logic that processes the information from the input data nodes. The diagram directs the flow of data among the nodes (see Creating a decision diagram). Predictive and function nodes use other models that are defined in the decision service (see Calling other models).
• Task model: Chains together tasks, and specifies the conditions for running them.
• Predictive model: Applies data from a machine learning model.
• Generative AI model: Analyzes or generates content based on the context of the decision service.
• Data model: Defines the custom data types that are used in the decision service.
• External libraries: Contain data types and functions that are used in models in the decision service.
• Decision operations: Define entry points to models.

This tutorial covers the creation and use of a decision service that is based on a decision model. It does not cover external libraries, or predictive or task models. You can find samples that use the models and external libraries in the GitHub repository Decision Intelligence Client Managed Software samples .