UiPath to PAD Migration Output

this article covers uipath specific behaviors, mappings, and known differences to be aware of when reviewing migrated pad output selectors blueprint converts uipath selectors to pad format where supported the following technologies and attributes are recognized technology supported 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 available in pad java title, app, cls, idx, aaname, role, name, virtualname, tablerow, tablecol sap app, title, id, idx ocr / native text — not supported where possible, blueprint generates multiple selectors per ui element to increase the likelihood of a match parent attributes in uipath, "parent" attributes are ancestor attributes — not strict parents for example, parentname="container" means the first ancestor with that name, which may not be the immediate parent if a selector has multiple parent attributes (e g , parentclass and parentid ), those attributes do not necessarily reference the same ancestor anchors anchors are supported using the \ has() pseudo selector in pad mid value wildcard support blueprint preserves and translates mid value wildcards from uipath selectors into equivalent pad formats mid value wildcards use within a string — not just at the start or end btn submit matches btn primary submit, btn secondary submit, etc file 2025 csv matches file report 2025 q1 csv, file 2025 summary csv, etc example uipath \<wnd app='app exe' title=' invoice 2025 ' /> pad equivalent — window title invoice 2025 pad handles these patterns using regex or wildcard syntax depending on control type and selector engine dynamic selectors for ui desktop automation, blueprint attempts conversion of dynamic selectors using a generated subflow called convert uipath selector this conversion does not always produce a working selector — some will require manual resolution this same subflow is also applied for dynamic web selectors, where it may work in certain cases, with the same caveat that manual resolution may still be required global variables setting the following variables in your pad flow helps improve migration quality by aligning file path behavior between uipath and pad variable behavior difference how to reconcile %basepath% uipath resolves relative paths from the main xaml file; pad resolves them from the pad installation folder set %basepath% to where specific project files will be located after migration %special folder x% supports applicationdata, commonapplicationdata, localapplicationdata, cookies, favorites, history, internetcache, programs, mymusic, mypictures, recent, sendto, startmenu, startup, system, templates, desktopdirectory, personal, programfiles, commonprogramfiles set %special folder x% to the correct folder path in your environment net script imports blueprint automatically assigns the required net namespaces to %defaultrundotnetscriptimports% on a per xaml basis you no longer need to configure namespaces globally — each migrated file receives only what its scripts need you can override or customize %defaultrundotnetscriptimports% if needed see setting up defaultrundotnetscriptreferences docid 821wzumakctteumhg9aat for full configuration details generate data table from text blueprint automatically maps uipath's generate data table activity to pad's convert text to data table action when the input is csv formatted pad output is configured with column delimiter , row delimiter \n (or as detected) first row as header enabled if applicable ⓘ this mapping applies only when the input clearly matches csv structure non csv formats may require manual adjustment post migration select menu item — sap mapping blueprint maps uipath's select item activity in sap gui automation to the equivalent pad sap action when a select item activity targets an sap menu or dropdown, blueprint generates a pad sap gui step using either populate text field on sap screen or click ui element in window , depending on the sap control type ⓘ this mapping applies only when the sap selector is clearly identifiable and the control supports interaction in pad when native support is unavailable, blueprint falls back to keyboard navigation or scripting