Map Queues

in pad queues are power platform objects that are referenced by pad actions using a work queue id users can use rules in blueprint to specify the work queue id to be used in the pad queue actions it generates when you generate rules blueprint will create a rule for every queue activity from uipath and every queue stage from blue prism you can then configure the rule with the work queue id and name that you'd like to use from power platform you can also create a rule to map queues without generating rules by using the add new button if a variable is being used by the source rpa code to reference the queue, you can use a rule to map the action to a single, specific pad work queue this often makes sense because in many cases the source automation only uses a variable because it reads the queue name from a spreadsheet and the value never changes if you don't configure the rule, then blueprint will use a variable for the queue in the pad action and you'll need to set that variable to the work queue id in pad ensure that the correct scope and source rpa tool is selected and that rules have been generated for more information, see using the rules table docid\ avz8twdvuyflf y9v6ds1 work queues table explained column description enabled by default rules are disabled when disabled a rule will have no affect on export when enabled, rule will be applied where applicable best practice is to leave a rule disabled until it is fully configured occurrences number of occurrences of this unresolved reference click the number to see a list scope the scope can be either a project or entire blueprint instance when using a project as a scope, the rule will apply to all applicable processes within the project this flexibility allows users to haven different rule sets for different projects source work queue name name of the queue as referenced in actions from the source rpa tool note these might be variables instead of static names target work queue id work queue id from pad in the web portal for power platform in the left navigation select ( more) work queues , choose a queue, then click advanced details to reveal the work queue id target work queue name name of the work queue in pad work queue configuration mapping of queue item priorities see section below for details mapping queue item priorities (work queue configuration) each rpa tool has their own way to prioritize queue items, and these approaches need to be mapped if the converted automations are to function in pad the same way they functioned in the old rpa tool this mapping of queue item prioritization can be specified in the work queue configuration column blue prism how to set rules for queue key blue prism allows you to optionally set one of the fields of the queue items to be a "key" this is defined in the queue definition in the system area of blue prism, and is not available to blueprint as part of the bprelease import however, you can define this field as part of a queue rule so it is factored into the conversion to pad you do this in the work queue configuration field of the rule, using this syntax { "key" "sin" } where "sin" is the name of the key field that was set in the blue prism queue definition see example blue prism below how to set rules for queue priority blue prism allows you to use any whole numbers to indicate priority, so there is no fixed range also note that lower numbers mean higher priority, and they allow negative numbers (example 10 is higher priority than 5) by contrast pad supports three priority levels low, normal, and high to map blue prism queue priorities to pad queue priorities you define numeric ranges for low, normal, and high and blueprint will convert according to those ranges you do this by specifying a lowerbound number and an upperbound number pad priority blue prism priority high any numbers less than lowerbound normal any numbers between lowerbound and upperbound low any numbers greater than upperbound the syntax to use in the work queue configuration is as follows (assume lowerbound=4 and upperbound=9) { "priorityrules" {"normalpriorityrange" {"lowerbound" 4,"upperbound" 9} } } uipath similar to pad, uipath uses a three value range for priorities high, normal, low in this case you use direct mapping instead of bounded ranges the syntax to use in the work queue configuration is as follows { "priorityrules" {"directrules" {"\[high]" "high", "\[normal]" "normal","\[low]" "low"} } }