Reusable Orchestration Components

Orchestration components are reusable. A single component, such as a rule or cross reference, can be included as a step in more than one orchestration. Because components are reusable, before modifying an existing component, the Orchestrator Studio has a "Where Used" button that you can use to view a list of all orchestrations where the component is used.

If a component is used by more than one orchestration, you should evaluate how it is used in other orchestrations before modifying it. You must not modify the component in any way that would break the functionality of other orchestrations.

The Orchestrator Studio also provides a copy feature so you can create a new component by copying an existing component. When you copy an existing component, you give the copy a new, unique name. The original component is preserved, enabling you to modify the new component as necessary, thereby eliminating the risk of breaking other orchestrations where the original component is used.