Work Queues Mapping

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.

Users can either add new rules by clicking Add New, or by uploading a CSV template.

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

Enhancement:

Release 8.3: Blueprint has improved its logic for substituting Work Queues during Blue Prism to PAD migrations when Rules are used to define queue mappings.

  • When a Rule is defined to map a Blue Prism Work Queue to a PAD-compatible queue name or ID, Blueprint now applies enhanced substitution logic to ensure:
    • Accurate queue name resolution
    • Consistent queue ID assignment
    • Fallback handling if a Rule is incomplete or ambiguous
    Example of enhancement:

Rule Definition:

1 If QueueName = "BP_Orders", then use "PAD_Orders_Queue"

Before:

  • Substitution might fail if the queue name was referenced indirectly or embedded in a variable.

Now:

  • Blueprint resolves the queue name even in dynamic or indirect references and applies the correct PAD queue mapping.

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:

Using Dashboard

The Rules dashboard is currently only able to modify existing work queue items.

Blue Prism to PAD

  1. Work Queues: Get Item by ID (All Statuses)

Updated was introduced in Blueprint 8.3

Blueprint now supports mapping the Blue Prism “Get Item by ID” action to Power Automate Desktop (PAD), with support for all item statuses.

  • When a Blue Prism process retrieves a specific queue item by its ID, Blueprint now maps this to PAD’s Dataverse or custom queue logic.
  • The enhancement ensures that items in any status (e.g., New, Pending, Completed, Exception) can be retrieved, not just active or available ones.

Example from BP

Example Migration in PAD

1 Action: Get Item by ID

2 Input: Item ID = 12345

1 Action: Get row from Dataverse table (or custom queue)

2 Filter: ID = 12345

3 Status: Any

  1. Work Queues: Is Item in Queue

Updated was introduced in Blueprint 8.3

Blueprint now supports mapping the Blue Prism “Is Item in Queue” logic to Power Automate Desktop (PAD), enabling direct checks for the existence of a queue item by key or ID.

  • When a Blue Prism process checks whether a specific item exists in a queue, Blueprint now maps this to a PAD-compatible lookup, typically using:
    • Dataverse query (if using Dataverse queues)
    • Loop and conditional check (for custom queues)

Example from BP

Example Migration in PAD

1 Action: Is Item in Queue

2 Input: Item Key = "Invoice_123"

1 Action: Get rows from Dataverse table

2 Filter: Key = "Invoice_123"

3 Condition: If count > 0 → Item exists

  1. Work Queues: Get Item Data

Updated was introduced in Blueprint 8.3

Blueprint now supports mapping the Blue Prism “Get Item Data” action to Power Automate Desktop (PAD), enabling retrieval of all fields associated with a specific queue item.

  • When a Blue Prism process retrieves data from a queue item, Blueprint now maps this to:
    • A Dataverse “Get row” action (if using Dataverse queues), or
    • A custom object lookup (if using custom queue structures).
  • All fields (e.g., ID, status, custom data fields) are extracted and made available for downstream use.

Example from BP

Example Migration in PAD

1 Action: Get Item Data

2 Input: Item ID = 12345

3 Output: Collection with fields like Name, Amount, Status

1 Action: Get rows from Dataverse table

2 Filter: ID = 12345

3 Output: %QueueItemData%

How did we do?