- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- SmartCard Authentication
- Configuring automation capabilities
- Audit
- Settings - Tenant Level
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- About Processes
- Managing Processes
- Managing Package Requirements
- Recording
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Other Configurations
- Integrations
- Host administration
- Organization administration
- Troubleshooting
Managing Package Requirements
An RPA journey starts in Studio, the realm of workflows and activities. In designing workflows developers can use various objects, which are typically managed centrally from Orchestrator using folders, which enable you to maintain fine-grained control over your automations and the associated objects.
These objects are essential for a successful process execution. Lacking any of the indicated objects prevents the process from executing successfully.
The Package Requirements tab allows you to identify missing objects and manually add them at the process level. This helps with:
- educating users about process dependencies,
- reducing manual workflow debugging,
-
identifying missing objects without the need to switch between Studio and Orchestrator UI.
.xaml
files and aggregates their intrinsic objects, such as:
Depending on whether the respective objects are detected or not, there are two Package Requirements tab behaviors:
- Tab turns red - the workflow has some dependencies that are not present in Orchestrator, therefore you need to add them.
-
Tab is empty, displaying that "This package version contains no requirements." - the uploaded package does not have any requirements.
Note: Orchestrator does not automatically detect the requirements for the packages that stored in external feeds.
-
Available - the object is present in Orchestrator. No further action needed.
-
Missing - the object is not present in the current folder in Orchestrator. You can either link it or add it into the corresponding Orchestrator folder, provided you have the proper permissions.
-
Folder not found - the object supposedly exists in an Orchestrator folder that was referenced in the Folder path field of an activity, but:
-
the folder does not exist in Orchestrator. You should add the folder in Orchestrator, use the same name as indicated in the Folder path column, and assign users to it.
-
you do not have access to that folder. You should ask for access to the Orchestrator folder indicated in the Folder Path column.
-
-
Unknown - the object name could not be determined. No available actions to perform. There are several scenarios which may result in an Unknown status:
-
you do not have the correct permissions set for that type of object;
-
a workflow activity references a queue item, for example, which cannot be linked to its queue.
Note: The unknown status of an object does not prevent the process from executing successfully.
-
In addition to the general statuses, triggers display the following statuses:
-
Pending creation - adding a trigger requires associating it to an existing process. While the process gets created, the trigger resides in Orchestrator memory and it becomes active after the process creation. You can edit triggers from the package requirements tab while they have this status. Later on, you have the option to edit them from the Triggers page.
-
Invalid configuration - the selected runtime is not available.
-
Duplicate name - the trigger name is duplicated.
To manage package requirements, you need the following permissions:
I want to ... |
I need ... |
The folder access I need ... |
---|---|---|
... see the available packages |
View permissions on Packages (tenant level) |
Not applicable, as Packages permissions are set at tenant level. |
... upload a package |
Create permissions on Packages (tenant level) |
Not applicable, as Packages permissions are set at tenant level. |
... see the available objects |
View permissions on the specified object |
Get access to the folder(s) that contains the object. |
... add an object |
Create permissions on the specific type of object |
Get access to the folder(s) you want to add the object to. |
... import an object from a different folder |
Create and View permissions on the specific type of object |
Get access to:
|
For each missing object, except action catalogs, you have the option to add it or to import it in the current folder, provided you have the necessary permissions.
Prerequisites: Make sure you have Create permissions on the specific object and access to the folder you want to add the object to.
If you suspect the missing object exists in the current tenant, but in a different folder, you can import it into the current folder.
Prerequisites: Make sure your have View and Create permissions on the specific object, and access to both the folder you are importing from, and the folder you are importing the object to.
In the case of multi-layered process dependencies, Orchestrator detects and shows only the first level dependency for a given process.
For example, process A needs process B to start, and process B needs process C to start. The dependency hierarchy is A > B > C. In this case, when checking package requirements for process A, Orchestrator detects and displays the first level of dependency for it, that is process B. If process B is missing, you can add it from the Package Requirements tab, but if process C is missing, you need to identify it as missing yourself and add it manually.
Orchestrator detects the action catalogs required to execute the process, but you cannot add the missing ones from the Package Requirements tab, as action catalogs are objects configurable via Action Center.
Prerequisites: Make sure you have Create permissions on the specific object and access to the folder you want to add the object to.
Proceed with the following steps:
- Head over to the corresponding Action Center instance.
- Access the Admin Settings page.
- Select the process folder .
- Click Add new catalog. Make sure to use the name detected as missing in the Package Requirements tab.
- Click Create.