As a workflow developer, you can use object reference information to optimize your development life cycle.
With the Automation Orchestrator Client, you can find object reference information. This feature has two functions:
- Find Dependencies: find information about object dependencies in your workflows. Dependencies can include other workflows, actions, resource elements, and configuration elements.
Note: Found dependencies can also include commented out code. For example, a workflow can include a line of code referencing an action that is commented out. The addition of commented out code in the list of found dependencies is expected behavior.
- Find Usages: learn if the selected workflow is used in other workflows in the Automation Orchestrator Client library.
You can access information about object references from the workflow editor or from the Automation Orchestrator Client library in either Card View, List View, or Tree View. For more information on the different types of content organization of the Automation Orchestrator Client library, see Content organization in the Automation Orchestrator Client.
The following procedure demonstrates how you can access object references from the workflow editor.
Prerequisites
Develop a workflow that includes at least one object reference.