Blueprint FAQ

browse by topic general docid\ qe6ei9dywuhja9wziurbe deployment docid\ qe6ei9dywuhja9wziurbe products & licensing docid\ qe6ei9dywuhja9wziurbe generative ai docid\ qe6ei9dywuhja9wziurbe migration support docid\ qe6ei9dywuhja9wziurbe general what is blueprint? blueprint is a software tool purpose built to support and accelerate migrating from legacy rpa tools to microsoft power automate desktop (pad), as well as managing a pad automation estate at scale it offers three products map (migration analysis & planning) analyzes an existing rpa estate to generate effort estimates, complexity insights, and migration sequencing recommendations before conversion begins blueprint migrator converts automations from uipath, automation anywhere a360, and blue prism into pad flows algorithmically, reducing the time and manual effort required for migration alc (automation lifecycle control) governs pad flows across their full lifecycle — from ideation and build through operation and retirement — providing visibility into flow health, quality, and change history how do i import a bot? see importing rpa files to migrator docid\ td9tcfofalwo0p8mvj0is or importing rpa files to analyze/alc docid\ ckl3q65h7j8bq1niblc14 how do i export a bot? see exporting rpa from blueprint docid\ b1anm09c4wv55i1hz346o how do i change my password? see change your password docid\ skb2lu7zbsi17oekedfs8 deployment is the product available as a cloud service or can it be installed on premise? both options are supported blueprint can be deployed as a cloud hosted service or installed on premise is it worth pursuing cloud hosting if internal approval processes are lengthy? yes cloud hosted deployments offer significant long term advantages — including reduced infrastructure overhead, faster access to updates, and lower operational maintenance burden — that outweigh the upfront approval effort products & licensing what are the blueprint products? blueprint licenses three products map (migration analysis & planning) — analyzes and estimates an rpa migration to pad before conversion begins used to assess your automation estate, generate effort estimates, identify complexity, and prioritize migration sequencing often referred to as an assessment docid\ ap78dzb10ftoym9p4eta1 migrator — converts automations from legacy rpa tools — uipath, automation anywhere automation360, and blue prism — to microsoft power automate desktop (pad) handles code conversion algorithmically, resolving actions, subflows, variables, and dependencies to produce pad flows alc (automation lifecycle control) — governs and improves pad flows across their full lifecycle — from initial ideation and build through to operation and retirement provides visibility into flow health, change history, and quality, enabling teams to manage their pad automation estate at scale how does the license model work? each product is licensed separately you purchase a set number of licenses, and each within that bot that you work with consumes one license map licenses are consumed upon import ⓘ map example if you purchase 25 licenses, you can assess 25 automations assessing additional automations requires purchasing additional licenses migrator licenses are consumed upon conversion (export) ⓘ migrator example if you purchase 10 licenses, you can convert the code of 10 automations converting additional automations requires purchasing additional licenses re converting the same automation — for example, with different blueprint tool conversion settings — does not consume additional licenses, provided the source automation code remains unchanged alc licenses are concurrent ⓘ alc example if you purchase 5 licenses on a 1 year term, you can work with up to 5 pad flows in alc at any one time you can change which flows are active throughout the year, but the maximum concurrent count is fixed at 5 what consumes a license in blueprint? licenses are consumed per how mains are counted varies by source platform uipath each project includes a main xaml file the total main xaml count equals the license count blue prism each process contains one main page the total main page count equals the license count automation anywhere a360 a360 does not define mains in its architecture blueprint counts root task bots as mains what is a bot? a bot is the root entry point of an automation and everything it calls during execution — its full call tree or dependency tree rpa platform a bot maps to uipath the main xaml in a process, plus all referenced xaml files blue prism the main page in a process, plus all referenced process and object pages automation anywhere 360 a root task bot (not called by any other bot), plus all referenced task bots power automate desktop a desktop flow what is a main? a main is the only root entry point of an automation — it is where execution begins and does not include the full call tree or dependency tree the term varies by platform rpa platform a main maps to uipath the main xaml in a process blue prism the main page in a process automation anywhere 360 a root task bot (not called by any other bot) power automate desktop the main subflow of a desktop flow are there limits on the number of users i can create? no, there are no user limits in any blueprint tool are there limits on data volume in my instance? yes there are technical limits on data volume as follows migrator limits flows to a total of 1 million characters blueprint provides features to help split automations that exceed this threshold into multiple pad flows migrator & map there is a limit of 100,000 actions per project if you exceed this during import, create a new project docid\ gj2vgt4x8vp2rf5sxk0fa to continue imported rpa files are subject to a 50mb compressed file size limit this is rarely encountered and is usually caused by embedded images, which blueprint does not require to resolve decompress the file, remove all images, then recompress before importing into blueprint how do i see how many licenses i have used or have remaining? see license and activity reporting docid\ tiivvofat ccsyu2p3mmm will additional licenses be consumed if i activate a process more than once? no blueprint detects previously imported identical components and flags them as duplicates duplicates are excluded from license consumption and separated out in dashboards & reports docid\ c6x2ob4hlstuhqvulwrsj what triggers a licenses running low warning to be displayed? when remaining licenses fall below approximately 20% of the total purchased, blueprint displays a warning during activation to prompt users to procure additional licenses contact blueprint support docid 09xnuekxn6xqp kqik69 or your success manager mailto\ customersuccess\@blueprintsys com for assistance what triggers an out of licenses error to be displayed? when a user attempts to import or activate processes that require more licenses than are available, blueprint returns an error additional licenses must be procured to continue contact blueprint support docid 09xnuekxn6xqp kqik69 or your success manager mailto\ customersuccess\@blueprintsys com for assistance how do i purchase additional licenses? contact your blueprint sales representative, your success manager mailto\ customersuccess\@blueprintsys com or blueprint support docid 09xnuekxn6xqp kqik69 generative ai can blueprint work with our own on premise genai solution? yes this requires a small amount of development work by blueprint you will need to provide a technical specification for your in house genai solution so we can build the appropriate connector contact your success manager mailto\ customersuccess\@blueprintsys com for more information what genai provider does blueprint use, and do we need our own account? blueprint uses openai genai capabilities are bundled as part of the product license — you do not need to provide your own openai account does blueprint's genai provider train its models on our company data? no see the general faq and model training faq sections of openai enterprise privacy https //openai com/enterprise privacy/ do all blueprint products use genai? it depends on the product product uses genai details map ✅ uses genai for its analyze capabilities — the features that interpret and describe source rpa code the migration specific analysis capabilities in map do not use genai migrator ✖️ does not use genai alc ✅ uses genai for most, but not all, of its features genai can be disabled across all products by an administrator using a single setting see genai settings docid\ okpnybw2 gz1 0iheok23 for details migration support to learn more about migration output in pad, please see why migrated flows look different in pad docid\ lh4ifp7kppgdfendnhitd what blueprint converts which source rpa tools does blueprint support for migration to power automate desktop (pad)? uipath (including uipath studiox) blue prism automation anywhere automation360 which specific rpa actions does blueprint convert vs not convert? blueprint's conversion logic is largely algorithmic rather than table based, which means whether a specific action — with its associated parameters and settings — converts is determined when the algorithms run against your actual data to get a precise picture for your automation estate, import your rpa data into blueprint and generate the conversion reports these will show exactly what converts and what does not for your specific dataset for most datasets, blueprint achieves a conversion rate above 95% does blueprint convert uipath custom actions? uipath custom actions can be built using low code (e g uipath studio) or pro code (e g c#) blueprint handles each case as follows low code custom actions blueprint converts the custom action code to a pad flow pro code custom actions the developer will need to re create the action in power platform however, blueprint resolves all usages of that custom action across the automation estate, so no manual work is required for each call note that if there are any pro code custom actions in your data they are shown in the custom actions tab of rules after you generate rules refer to using rules docid\ ln7dxyaelvpd89ii09xoz does blueprint convert vbos and extended vbos? in the case of custom vbos the code within the vbo action itself is converted to pad actions blueprint converts calls to standard vbos into pad actions when blueprint detects that a standard vbo has been extended actions that have not been modified are converted to pad actions actions that have been modified or added are converted to pad flows or subflows are libraries migrated? in blue prism libraries are essentially vbos standard vbos are converted directly to pad actions where custom actions have been created, which is the case for extended standard vbos or custom vbos, blueprint will convert those actions at every point they are called, or you can make the equivalent of a reusable library by using blueprint's "export as vbo" feature refer to exporting libraries as reusable flows docid\ c2xk1qcu9jsqzpnujgvx3 in uipath libraries can be created using lo code (studio) or pro code (e g c#) those created using pro code will appear as custom actions in blueprint rules where you choose the mapping approach using a rule refer to map custom actions docid 3roqyijge55p1x28c4ykf for those created using lo code blueprint will convert the workflows to pad subflows in every flow created, or you can make the equivalent of a reusable library by using blueprint's "export as library" feature refer to exporting libraries as reusable flows docid\ c2xk1qcu9jsqzpnujgvx3 completing your pad code will my automation migrate 100% fully end to end? no feature differences between source and target rpa tools mean bots will not be fully migrated developer code completion work is required before migrated bots are production ready what will my migrated code look like? migrated bots aim for functional equivalence but will require post migration completion work before they are production ready platform differences between source and target rpa tools mean one source action may expand into multiple pad actions to preserve the intended behavior blueprint offers rules and supports asenumerable and xmldocument mappings, mid value wildcard matching, and region based image selectors to improve fidelity and reduce manual fixes blueprint also embeds comments into the pad code to help you complete them why does blueprint add extra code in a migrated automation? blueprint adds code to preserve functional equivalence between source and target rpa tools one source action may require multiple pad actions to behave the same way ex an action in uipath may need to be migrated as many actions in pad in order to function similarly where no combination of standard pad actions can replicate the source logic — or where the result would be overly verbose — blueprint may use a net script instead blueprint also adds optional elements such as todo comments, regions, and logging these can be toggled off in migration preferences docid\ miqcvzfhmck8gephwje1e if they're not required for your migration why does blueprint generate so many variables blueprint offers the option on export to utilize pad local variables if you decide not to use local variables, blueprint simulates scope and prevents variables from colliding or overwriting one another by adding prefixes to variable names per subflow variable prefixing is configurable — see variable prefixing docid\ lvidy2 rg7bpa9sjxzn4u for more details why do some variable datatypes appear not to migrate? pad handles variable typing at runtime and supports a core set of datatypes blueprint maps or converts others as needed collection data migrates via asenumerable support, converting lists into pad datatables xml payloads use native xmldocument support both reduce manual datatype adjustments while preserving bot behavior why do some processes or sub processes appear to be missing? by default, blueprint inlines subflows that are called only once or are very short — these will appear embedded within their parent flow in pad rather than as separate subflows to locate inlined logic or adjust this behavior verify your export wizard option docid\ lvidy2 rg7bpa9sjxzn4u selections check the rpa import log docid\ lh0ylrtxzb3w8g175l1ou in your project folder for import failures the log file is appended with an asterisk ( ) when a problem is encountered during import failures appear at the top of the log use bulk reimport and recalculate docid\ ei1zv8hnni9mwxclsvo5m to force a fresh migration of chosen processes in export wizard options docid\ lvidy2 rg7bpa9sjxzn4u , change your call or embed settings from system recommended to call everything to prevent inlining and keep all subflows discrete do todos and compiler errors represent all post conversion work? resolving todos and compiler errors will make your migrated code functionally complete and compilable, but runtime validation is still required selectors in particular often need to be reviewed, retested, and re spied against your target applications after an initial test run — blueprint cannot validate selectors during migration because we do not have access to your applications other runtime errors may also surface during testing contact blueprint support docid 09xnuekxn6xqp kqik69 for assistance with any post migration issues