UiPath to PAD Migration Output Details

Updated by Luka Koczorowski

UiPath to PAD Common Items

Selectors

PAD supports the following attributes and technologies when converting selectors from UiPath

Technology

Attributes

Notes

Web

tag, id, aaname, name, idx, type, tablerow, tablecol, css-selector, class, src, title

UIA

app, title, cls, name, role, automationid, idx, ctrlname, aaname, tableRow, tableCol

AA

app, title, cls, name, role, ctrlid, idx, ctrlname, aaname, text

Direct support not yet available in PAD.

Java

title, app, cls, idx, aaname, role, name, virtualname, tableRow, tableCol

SAP

app, title, id, idx

OCR / Native Text

Not supported

When possible Blueprint will create multiple selectors per UI element to increase the possibility of a matches.

Parent Attributes

In UiPath, parent attributes are not in fact parent attribute, they are ancestor attributes. For example, when a selector has parentName="container" this means that the first ancestor to have a name, is container. This ancestor is not necessarily the parent. Furthermore, if a selector has multiple parent attributes, for example parentclass and parentid, those attributes do not necessarily reference the same ancestor.

Anchors

Anchors are supported using the :has() psuedo selector in PAD.

VARIABLES

  1. UiPath Global Variables
    Setting these variables will help improve migration quality.

    Variable

    Behavior

    How to Reconcile in PAD

    %BasePath%

    In UiPath, relative file or folder paths are relative to the main xaml file. In PAD, relative file or folder paths are relative to PAD installation folder.

    Set %BasePath% where specific project files will be located after migration

    %SPECIAL_FOLDER_X%

    Possible Special Folders:

    ApplicationData, CommonApplicationData, LocalApplicationData, Cookies, Favorites, History, InternetCache, Programs, MyMusic, MyPictures, Recent, SendTo, StartMenu, Startup, System, Templates, DesktopDirectory, Personal, ProgramFiles, CommonProgramFiles

    Set %SPECIAL_FOLDER_X% where specific folder will be located after migration


How did we do?