Reusing decision artifacts

Reusing decision artifacts within a decision service

You can reuse decision artifacts throughout a decision service. For example, you can use the output of a decision model in another decision model, or use the vocabulary that is defined in a data model in multiple other decision artifacts. When an artifact is reused within a decision service, a dependency must be declared. This may happen automatically, but sometimes the dependency needs to be created manually:

Dependencies are automatically declared when...

• Adding function nodes in decision models. For more information, see Calling other models.
• Adding function task nodes in task models. For more information, see Adding a function task node.
• Selecting a data model at the creation of a decision model, task model, or predictive model. For more information, see Using data models in other decision artifacts.

Dependencies need to be manually declared when...

• Reusing data types from a data model in another data model. For more information, see Using data models in other decision artifacts.
• Using data types from an external library in a decision artifact. For more information, see Using an external library in a decision service.

Reusing decision artifacts across decision services

Decision artifacts can be reused across multiple decision services within the same decision automation. The process to reuse decision artifacts across decision services consists of two steps:

1. Publish the artifact to make it discoverable by other decision services. The publication process takes place at the automation level.
2. Manually declare a dependency in the consuming decision service to reference the published artifact.

For detailed instructions, see the Publishing decision artifacts topic below.