Declaring and managing dependencies

Declaring dependencies lets you reuse decision artifacts within a decision service.

Automation Decision Services allows you to 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 defined in a data model in multiple other decision artifacts.

Declaring dependencies

Some dependencies are automatically declared when reusing decision artifacts:
Other dependencies need to be manually declared before you can reuse a decision artifact:

Ordering dependencies

The order in which the dependencies of a decision artifact is displayed in the Dependencies tab determines how ambiguities between data types are resolved.

For example, if a decision model has a dependency on two data models that contain data types with the same fully qualified name, data types from the data model that is listed higher will be used in priority.

To reorder dependencies, use the up and down arrows located next to each dependency.

Removing dependencies

Important: When deleting a function node in a decision model or a function task node in a task model, the dependency to the reused model is not automatically removed. It needs to be removed manually, as described below.
You can remove a dependency between two decision artifacts from the Dependencies tab:
  1. Open the source decision artifact, that is the decision artifact that reuses another one.
  2. Go to the Dependencies tab.
  3. Browse to the dependency that you want to remove and click the Remove Remove dependency icon icon.