Manage your work items in RPA Hub
Manage your work items more efficiently in RPA Hub. You can view your work items, mark them as complete, and reassign a work item.
Before you begin
Create a queue. For more information, see Create a queue in RPA Hub.
Role required: sn_rpa_fdn.rpa_developer, sn_rpa_fdn.rpa_business_user, sn_rpa_fdn.rpa_support_user, or sn_rpa_fdn.rpa_admin
Procedure
Navigate to All > Robotic Process Automation > RPA Hub Workspace.
Select the list icon (
List icon.\).
On the Lists tab, under Build, select Queues.
Open the queue to view your work items.
To mark a work item as complete or reassign a work item, select the appropriate action on the Work Items tab.
| Option | Action |
|---|---|
| To mark a work item as complete |
|
| To reassign a work item |
|
On the Work Items tab, open a work item to view the details on the form.
In the Activity and Compose fields, view the activity of the form, work notes, and additional comments.
Parent Topic:Work items in RPA Hub
Related topics
Queue implementation in RPA Hub
Work item form in RPA Hub
Use the Work item form to view more details of the executed work items.
| Field | Description |
|---|---|
| Name | Name of the work item. |
| Work Queue | Name of the queue. |
| Status | Status of the work item. |
| Exception Type | Type of the exception:- Application - For example, if an issue persists with an associated application such as SAP. - Business - For example, if an issue requires a manual intervention to fix it. The auto retry functionality retries the work items based on the exception type. If the Exception Type field is Application, then the work item is auto retried. Roles required to edit this field: RPA robot. |
| Started On | Start date and time of the work item. |
| Completed On | Completion date and time of the work item. |
| Attempts Count | Number of times the work item is picked for auto retry.The minimum value is 0. |
| Details | |
| Priority | Priority of the work item:- Critical - High - Medium - Low The assigned robot executes the bot process as per the defined priority in the work queue. |
| Type | String field to define the type of work item. |
| Stage | Custom field for the robot to maintain different stages of the transaction. |
| SLA | Time and date that the SLA was started. |
| Robot | Name of the robot that is assigned to the work queue. |
| Created | Creation date and time of the work item. |
| Last Started Time | Last start time of the work item. |
| Deferred Till | Work item that is not picked until the specified date and time. |
| Completed By | Name of the robot who has completed the work item. |
| Remarks | Remarks updated by the robot runtimes. |
| Content | |
| Request Content | Non sensitive content which is displayed in plain text in the Work Item form and can be used for work item processing. |
| Sensitive Request Content | Sensitive request content which is encrypted and masked in the Work Item form and can be used for work item processing.When the work item is picked, the sensitive data is decrypted and passed to the RPA Desktop Design Studio or robots. With this option, you can pass sensitive information through queues. For example, credit card details are encrypted. |
| Response Content | Content that is added or updated when a work item is picked after the transaction. |
| Transaction Activity | |
| Work notes | Work notes for the work item. |
| Additional Comments | Comments for updating this work item. |
| Activity | Transaction logs for the selected work item. |
Related topics
Using auto-retry functionality for your failed work items in RPA Hub