- Release Notes
- Introduction
- Governance
- Source Control
- CI/CD Pipelines
- Feeds Management
- Logging
Automation Ops user guide
This sections describes the steps you need to take to identify all the processes that use a specific dependency in a specific Orchestrator tenant/ folder.
To initiate a dependency search task, take the following steps:
-
In the Dependency search window, provide details for the following fields:
-
Tenant (Required) - specify the tenant name.
-
Folder (Required) - specify the folder name.
-
Package name (Required) - specify the package name.
-
Version (Optional) - specify the package version. If you do not mention the version, the search results will include all versions of the package mentioned in Package name.
-
-
Select Submit to trigger the dependency search.
You can only have one dependency search task for each tenant at a time. Also, the dependency search focuses on the specified folder, not including any of its sub-folders.
Each search result includes details about tenant name, folder name, searched package and version (if provided), the search status and possible actions.
-
InProgress - indicates that the search task is still ongoing and no actions are available at this point.
-
Faulted - indicates that the search task has failed and no actions are available at this point.
-
Completed - indicates that that the search task is done and the following actions are available:
-
Download JSON - you can download the search results as a
.jsonfile. -
Download CSV - you can download the search results as a
.csvfile. -
View Processes - displays the Process results windows where you can view details for all the identified processes.
-
