Using the Rules Wizard

the rules wizard is a guided alternative to the rules table and rules csv for configuring conversion rules rather than working across all rules for a project, the wizard narrows focus to only the rules relevant to the specific call trees being exported — and only for the rpa tool of those call trees the wizard improves on the rules table in three key ways scoped view — only shows rules relevant to the automations you are exporting, rather than all rules across the project live selections — instead of manually copying and pasting ids and names of pad flows, queues, and blueprint processes, the wizard presents live lists you can select from directly validation and guidance — validates your selections as you make them and provides contextual guidance at each step the wizard covers three rule types reuse , queue , and unresolved references all other rule types are configured in the rules table accessing the wizard the rules wizard appears automatically when rules are enabled in settings and you initiate an export to power automate desktop you can bypass the wizard if you prefer to work directly in the rules table ⓘ if you bypass the wizard, any rules that are enabled in the rules table will still be applied to the export to export with no rules applied, ensure all rules are disabled in the rules table before exporting before launching, the wizard performs two checks single rpa tool scope — the selected call trees must all belong to the same rpa source tool rules are current — if rules need to be regenerated, you will be prompted to regenerate them or proceed with the current rules if both checks pass, the wizard launches and guides you through each rule stage all changes made in the wizard are saved back to the rules table after the export is initiated, so they can be applied to future exports stage 1 reuse rules this stage appears when reusable components are detected in the call tree each row represents a component with an opportunity for reuse — either because it is called from multiple call trees (and would otherwise be duplicated as subflows across multiple flows) or because multiple copies exist in the source for each row, select how blueprint should handle the component row disabled — every occurrence of this action is replaced with a todo comment in the converted pad code row enabled, no selection — blueprint automatically creates a new pad flow using the action's name, and all occurrences reference that flow row enabled, existing pad flow selected — all occurrences reference the designated pad flow ⓘ if the value in the choice field appears in red, the selected pad flow no longer exists if not resolved before export, all occurrences will be replaced with a todo comment use the add processes button to manually add a process from the current scope to the list when finished, click next to proceed to the queue rules stage stage 2 queue rules this stage appears when queue references are found in the call tree each row represents a queue name found in the source code that can be mapped to a pad queue for each row, select how blueprint should handle the queue row disabled — blueprint creates a new variable used in all references for this queue row enabled, no selection — blueprint creates a new variable used in all references for this queue row enabled, existing pad queue selected — all references are replaced with the selected pad queue ⓘ if the value in the choice field appears in red, the selected queue no longer exists in pad if not resolved before export, blueprint will create a new variable for all references to this queue when finished, click next to proceed to the unresolved references stage stage 3 unresolved references rules this stage appears when missing references are found in the call tree each row defines how a missing reference should be handled during conversion for each row, select how blueprint should handle the reference row disabled — every occurrence of this action is replaced with a todo comment in the converted pad code row enabled, no selection — blueprint automatically creates a new pad flow using the action's name, and all occurrences reference that flow row enabled, existing pad flow selected — all occurrences reference the designated pad flow row enabled, existing blueprint process selected — blueprint automatically creates a subflow, and all occurrences reference that subflow row enabled, script entered — all occurrences are replaced with the specified script ⓘ if the value in the choice field appears in red, the selected component no longer exists if not resolved before export, all occurrences of the unresolved reference will be replaced with a todo comment when finished, click next to complete the wizard and initiate the export