Work Queues Mapping

Updated by Anshu Joshi

Work Queues in the source tool (Blue Prism/UiPath) do not include the Work Queue ID and Name which are required to map and execute the Queues in PAD. In this scenario, we have to use rules to map source-target queue name/id.

Using CSV

  1. Import CSV

To map the Work Queues, the user needs to configure the rules and then import the CSV.

Fill in the following columns:

  • Column ("IsActive") = 1 (TRUE)
  • Column ("ScopeId") = Blueprint Scope or Project Id where the bot is imported
  • Column ("SourceObjectName") = Name of the Queue in the Source tool
  • Column ("SourceActionType") = WORK_QUEUE
  • Column ("TargetObjectId") = Work Queue Id from Work Queue created through PAD
  • Column ("TargetObjectName") = Work Queue Name from Work Queue created through PAD
  • Column ("TargetActionType") = WORK_QUEUE
  • Column ("DefaultValue") = Used for defining Rules for Priority Property

Note:
- CSV file format is also accepted to edit rules.
- To import rules, from the Rules dashboard, click Advanced -> Import Rules From CSV

Example

Work Queue details can be found on the Power Platform online site under Work Queues -> Advanced details.

How to Set Rules for PAD Queue Id and Name

Using the mapping below we can map PAD Queue Id and Name.

Only for Blue Prism

How to Set Rules for Queue Key

Using the mapping below we can map the internal key ID of the Queue to the PAD Name. Use the "DefaultValue" column:

{
    "Key": "Id",
}

How to Set Rules for Queue Priority

Use the "DefaultValue " column to set up the rules for Priority. Using the mapping sheet (Rules) we can map the Priority property.

Rules for Priority:

You can set mappings for Blue Prism Priority with the following methods:

  1. If priority is set via strings (i.e., Low, Normal, High) you can set Direct Rules:
    "PriorityRules": {
        "DirectRules": {
            "[high]": "HIGH",
            "[normal]": "NORMAL",
            "[low]": "LOW"
        },
 }
  1. If priority is set via integers (i.e., 1 - 5), you can also set Normal Priority Range to assign Priorities to the Queue:
    "PriorityRules": {
            "NormalPriorityRange": {
            "LowerBound": 2,
            "UpperBound": 3
        }
    }

  • Blueprint assumes the closer the value is to 0, the higher the priority.
  • In the example above
    • If the Priority value is below the lower bound, it will be mapped to High priority in PAD (i.e., if Blue Prism property Priority = 1).
    • If the value is above the UpperBound, it will be mapped to Low priority in PAD (i.e., if Blue Prism property Priority = 4).
    • If the value is between the two bounds, it will be mapped to Normal priority in PAD

This is how the mapping looks in PAD:

How did we do?