Control Room allows filtering of the displayed queue items using exact tags and by
using wildcards

Wildcards are not allowed in the Tag Fitter property of the Work Queues business object
Get Next Item action

Work Queue item Status can only be set to Completed or Exception

Tags can be used allow flexibility in the order items are worked within a single Work
Queue

Something that identifies the type of work that was performed Example tags might be:
Funds Transferred, SIM Card Requested, Account, Closed, Account Suspended, Account
Noted

Something that identifies exact datetime of a step in the process. Example of tags might
include Account Closed 20/03/2017 12:12:16, Work
Completed 20/03/2017 12:12:16: Request Loaded 20/03/2017 12:12:16

Something that identifies the source of work. Example of tags might include: Email, Web
Form, Excel Adhoc. Database

Something that identifies the client record to make work queue items easier to search.
Example tags might be a phone number, customer reference number or ID, customer full
name. For example: +4407994446767, 00023231 A; Mr John A Smith

Something that identifies the type of process scenario. Example of tags might include:
Invalid Product, Unrecognised customer, Goneaway Marker, Invalid Status

The process will work all stages in the "Access Customer Account page until the error is
thrown and then focus would move to the breakpoint at "Get Customer Details" stage.

The process will work all stages in the 'Access Customer Account1 page until the error
is thrown and then focus would move to the "Recover 1 stage

The process will work all stages in the "Access Customer Account' page until the error is
thrown and then focus would move to the stage containing the error on the "Access
Customer Account" page,

The process will work all stages in the "Access Customer Account" page until the error
is thrown and then focus would move to the "Exception 1 stage.

It is common for duplicate elements to be found based upon the attributes that are ticked
by default using the Blue Prism product. Time needs to be spent experimenting with the
attribute ticks until a unique, reliable, and consistent selection of attributes are found.

It will not be possible to interface with the element in a unique way. You will need to use
Surface Automation techniques for this element.

A code stage interface will need to be created and used for this application, this will give
you more flexibility to interact with the application elements.

You will need to make the attributes you have selected dynamic. This will allow your flow
to loop around, incrementing the attribute value until the correct element is found and used.

The process will work all stages in the; Access Customer Account" page until the error is
thrown and then focus will move to the "Get Customer Details" stage.

The process will work all stages in the "Access Customer Account" page until the error
is thrown and then focus will move to the "Recover 1 stage.

The process would will all stages in the "Access Customer Account' page until the error
is thrown and then focus will move to the stage containing the error on the ''Access
Customer Account" page.

The process will work all stages in the 'Access Customer Account" page until the error is
thrown and then focus would move to the appropriate recover stage on the 'Access
Customer Account" page.

Refresh a Work Queue

Create a Work Queue

Encrypt a Work Queue

Rename a Work Queue

The flow will pass through calculation stage "A"

The flow will pass through calculation stage "B"

The flow will pass through calculation stage "C"

An exception will be thrown

Adding a tag requires an item to be locked

Adding a tag requires an item to be locked if there are multiple resources working the
same queue

Adding a tag does not require an item to be locked