FAQ: Completing PAD Code Post-Migration

to learn more about migration output in pad, please see working with migration output in power automate desktop (pad) docid\ lh4ifp7kppgdfendnhitd will my automation migrate 100% fully end to end? no bots will not be fully migrated due to feature differences between source and target rpa tools developer code completion work will be required to make migrated bots production ready what will my migrated code look like? migrated bots aim for functional equivalence but will likely require post migration completion due to platform differences one source action can expand into multiple pad actions to preserve the intended behavior blueprint supports bulk reimport/recalculate, asenumerable and xmldocument mappings for collections and xml data, plus mid value wildcard matching and region based image selectors to improve fidelity and reduce manual fixes—prioritizing functionality, then clarity why does it look like blueprint generates so many variables? pad does not support variable scoping in order to simulate scope to avoid collisions and overriding variables we add prefixes for each subflow pad does not support variable scoping to simulate scope and avoid collisions, blueprint adds prefixes for each subflow additional options in migration preferences allow users to control variable naming and reduce verbosity variable prefixing remains configurable in the export wizard see variable prefixing docid\ lvidy2 rg7bpa9sjxzn4u for more details it doesn't seem like some variable datatype are migrated over? pad handles variable typing at runtime and supports a core set of datatypes, so blueprint maps or converts others as needed collection data migrates via asenumerable support (converting lists into pad datatables) and xml payloads use native xmldocument support—reducing manual datatype adjustments while maintaining bot behavior why does it look like blueprint is adding extra code? blueprint migrate adds code to preserve functionality between source and target rpa tools newer mappings such as “open excel – read only” and “get subfolders” reduce the need for verbose or scripted workarounds ex an action in uipath may need to be migrated as many actions in pad in order to function similarly if there is no combination of standard pad actions to support the actions in the source bot or if the migration result would have been too verbose or complicated, blueprint may use a net script instead blueprint also adds optional code like todo comments, regions, logging, etc if your organization doesn’t need certain optional code types, you can toggle them off in migration preferences docid\ miqcvzfhmck8gephwje1e why is blueprint making duplicate subflows? the logic is the same, but the parameters differ due to pad’s lack support for variable scoping blueprint continues to optimize subflow reuse and parameter handling in each release why does it seem like some processes/sub processes are missing? by default, blueprint inlines subflows that are called only once or are short—so they won’t appear as separate flows to review/import missing logic ver ify your variable prefixing docid\ lvidy2 rg7bpa9sjxzn4u selections check the rpa import log docid\ lh0ylrtxzb3w8g175l1ou in your project folder for any import failures ⓘ rpa import logs with failures will display a in the file name and import failures will be listed at the top of the log use bulk reimport and recalculate docid\ ei1zv8hnni9mwxclsvo5m to force a fresh migration of chosen processes toggle ‘call everything’ under export wizard options to prevent inlining and ensure all subflows remain discrete this behavior is configurable to change this behavior, go to export wizard options docid\ miqcvzfhmck8gephwje1e and change call or embed settings from system recommended to call everything does resolving todos and compiler errors fully prepare a migrated bot for production? no while todos and compiler errors make up the bulk of the work, selectors will need to be reviewed and tested as well blueprint cannot test the efficacy of the selectors when migrating to pad because we likely will not have access to your applications if you notice an issue with selectors in your migrated bots, please reach out to our blueprint support team https //community blueprintsys com/ or your success manager what about my custom actions/libraries? blueprint can only migrate standard actions; however, blueprint can still help with custom actions and libraries via rules docid\ sywfxlo yt6kytda7uoya