Blue Prism to PAD Migration Output

this article covers blue prism specific behaviors, mappings, and known differences to be aware of when reviewing migrated pad output for general migration output concepts, see working with migration output in power automate desktop (pad) docid\ lh4ifp7kppgdfendnhitd collections conversion blue prism collections have two primary interfaces that differ significantly from a standard list or array a single row collection behaves like a dictionary — properties in row 0 are accessed as key/value pairs blueprint converts all blue prism collections into native pad data tables each collection field becomes a column header, and each row maps directly to a table row all collections output as pad data tables — more compatible with pad's native actions and easier to manipulate using built in table operations selectors blueprint converts blue prism selectors to pad format where supported technology supported 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 available in pad java — conversion not supported — different java technology is used in pad sap id region — images are used where native pad image actions exist where possible, blueprint generates multiple selectors per ui element to increase the likelihood of a match region based image selectors when a ui element cannot be reliably identified using standard selectors — such as in sap, citrix, or legacy systems — blueprint generates a region based image selector using pad's image fallback mechanism this allows automation to continue even when traditional selectors fail error handling local exceptions in blue prism, a recover stage placed inside a block catches errors local to that block blueprint migrates this using pad's on block error action, which is equivalent to a try/catch block when an error occurs within the on block error scope error details are recorded in the lasterror variable blueprint uses a stop flow action instead of convert text to number 1/0 when throwing or rethrowing errors if no error occurs, or the error is handled, the flow resumes — equivalent to blue prism's resume stage, which in pad resets the onerror variable to false and continues execution global exceptions in blue prism, a recover stage placed outside a block functions as global error handling, catching any error that occurs outside defined blocks blueprint migrates this using a global on block error scope in pad, with the same lasterror variable and stop flow pattern described above multi entry and multi exit points blue prism supports error blocks with multiple entry and exit points — a structure pad cannot replicate directly blueprint flattens this into a linear structure using set variables , if statements, and go to actions multiple entries blueprint creates an entrydestination variable and uses it in if/elseif statements to determine which path to execute multiple exits blueprint creates an exitdestination variable and uses it in if/elseif statements to determine the exit path exception type and details blue prism's exception stage allows users to manually throw exceptions, with an option to preserve the current exception type in pad when preserve exception is selected, blueprint migrates this as an if statement that retrieves the last exception details from lasterror when custom type and details are provided with preserve type unchecked , blueprint migrates the custom type and detail values directly work queue handling fetchxml queue filtering when a blue prism process uses queue filtering logic, blueprint translates it into fetchxml queries compatible with pad's dataverse connector this enables more precise and performant filtering of queue items, particularly for dataverse backed queues json conversions blueprint supports several json to collection conversion patterns, all outputting to pad data tables skipping array wrapper — when the outer array contains a uniform structure, blueprint skips it and converts the inner objects directly into a data table array of objects — when the json is an array of objects, blueprint converts each object into a table row and extracts keys as column headers referencing individual items — after converting a json array to a data table, individual rows can be accessed using standard pad table referencing %datatable\[1]\['name']% vbo matching blueprint excludes intentionally unimported vbo pages — those matched to standard pad actions — from appearing in the missing processes report and call tree visualizations when a vbo page is matched to a known pad equivalent and not imported, it is recognized as intentionally excluded and no longer flagged as missing additional mappings unsupported attach stages when a blue prism attach stage cannot be mapped to a pad equivalent, blueprint previously inserted a todo comment as of v8 3, these are downgraded to info comments , indicating the stage is unsupported but does not require immediate manual intervention // info attach stage not supported in pad no direct equivalent available get subfolders blue prism's "get subfolders" logic maps to pad's get subfolders in folder action output is a list of folder paths that can be looped through or filtered using pad's native actions blue prism pad output action get subfolders / input c \invoices / output collection of folder names action get subfolders in folder / folder c \invoices / output %subfolders% open excel – read only blue prism's open workbook action with read only mode maps to pad's launch excel action with the read only flag enabled, preserving the original file integrity blue prism pad output action open workbook / path c \reports\june xlsx / read only true action launch excel / open excel file c \reports\june xlsx / read only yes