Reusing or Copying Orchestration Components
Orchestration components are reusable. A component such as a white list or cross reference created for one orchestration can be used in other orchestrations. When you add a step to an orchestration, the Orchestrator Studio gives you the option to create a new component for the step or select from a list of existing components.
If you reuse a component, you must make sure to not modify the component in any way that would break the functionality of other orchestrations that use the same component.
The Orchestrator Studio also provides a copy feature that enables you to create a new component from a copy of an existing component. The existing component can serve as a template for creating the new component. Because you are using a copy, you do not have to worry about breaking existing orchestrations where the original component is used.