Blueprism to PAD Migration Output Details
This article describe Blueprism to Power Automate Desktop (PAD) specific conversions explanations. For generic conversion information, read Working with Migration Output in Power Automate Desktop (PAD)
Collections Conversion
Collections in Blueprism have two primary interfaces which differ quite a bit from a typical list or array. For example, a single row collection behave like a dictionary/custom object. The properties within the object in row 0 can be accessed as a key/value pair. In other to replicate this behaviour Blueprint converts collections into a Custom Object with the following signature:
{ "Counter": 0, "Items": [] }
Selectors
PAD supports the following attributes and technologies when converting selectors from Blueprism
Technology | Attributes | Notes |
Web | ElementType, InnerText, MatchIndex, PageAddress, Src, Name, Class, Id, XPath, InputType | A backup selector is created using XPath |
UIA | ControlType, Name, MatchIndex, AutomationId, ClassName, LocalizedControlType, Enabled, | |
AA | Role, Enabled, Name, Visible, Id, ClassName, MatchIndex | Direct support not yet available in PAD. |
Java | Conversion not supported. Different Java technology is used in PAD | |
SAP | Id | |
Region | Images are used where native PAD actions for images exist |
When possible Blueprint will create multiple selectors per UI element to increase the possibility of a match.
Blue Prism to PAD Error Handling
- BP to PAD Local Exceptions
- BP to PAD Global Exceptions
- BP to PAD Multi Entry and Multi Exists
- BP to PAD Exception Type and Details