A queue is a container that enables you to hold an unlimited number of items. Queue items can store multiple types of data, such as invoice information or customer details. This information can be processed in other systems - SAP or Salesforce, for instance.
New queues created in Orchestrator are empty by default. To populate queues with items, to change their status and process them, you have to use Studio activities. As soon as queue items are processed, they become transactions.
Queues enable you to create large automation projects underlied by complex logic. For example, you can create a process that collects all invoice information and creates a queue item for each piece of data to store it. Subsequently, you can create another process that gathers the information from Orchestrator, and uses it to perform additional tasks, such as paying the invoices in a different application, postponing their payment according to their due date or value, sending emails to the accounting team every time a bill is paid, etc.
Queue Item Statuses are controlled by RPA developers when they create the automation projects.
The Queues page enables you to create new queues. It also provides you with viewing access to the previously created queues, to charts with the transaction status progress over time, and to various other details, such as average execution time and the total number of successful transactions.
The Transactions page displays the transactions from a given queue. It also shows their statuses, the dates when they should be processed, the Robot that processed them, and the type of exception thrown or assigned reference - if any.
You can search for a specific transaction or a group of them, according to a custom reference, which is added through the Reference property of the Add Queue Item and Add Transaction Item activities. The reference can be used to link your transactions to other applications used within an automation project. Additionally, this feature enables you to search for certain transactions, in Orchestrator, according to the provided custom reference.
Transaction references can also be enforced to be unique, at queue level. This feature is enabled when creating the queue and applies to all transactions except deleted or retried ones. This makes identifying a specific item a breeze and eases the review process.
If a duplicate reference is encountered while adding items to a queue, the job fails with a Faulted status and displays the
Execution error: UiPath.Core.Activities.OrchestratorHttpException: Error creating Transaction. Duplicate Reference. error message in the Job Details window.
Information stored in queue items is displayed in Orchestrator, in the Transaction Details window, under Specific Data. Additionally, if the item failed and was retried, the history of the item is displayed in the same window.
The Transaction Details window contains two tabs: Details and Comments. The Comments tab enables you to view and add transaction-related comments in case you need to share information about a specific transaction with your teammates.
All the users with View and Edit access to Queues and Transactions can add, edit, or remove comments. For more information, see Managing Transactions and Field Descriptions for Transactions.
You can export all the transactions and information related to a given queue to a .csv file, by clicking the Export button, in the Transactions page. All page filtering options apply to the generated file, too.
Updated 3 years ago
|Studio Activities Used with Queues|
|Queue Item Statuses|
|Managing Queues in Orchestrator|
|Managing Queues in Studio|
|Field Descriptions for Queues|
|Field Descriptions for Transactions|