Blue Prism: VBO Matching on Import

when importing blue prism files, migrator automatically attempts to match extended or custom vbo objects against its repository of standard blue prism vbos this improves mapping percentages by referencing blueprint's built in action equivalents rather than importing each vbo page as a separate process for example, a custom object named "excel vbo v2" may be matched to the standard "ms excel vbo " for any pages within that object that match standard pages (such as launch excel or write to excel), migrator uses its own repository for those commands instead of importing them how matches are displayed in the import modal objects matched to a standard vbo are indicated with an arrow (→) followed by the matched vbo name matched pages within that object are displayed in bold matched processes are unchecked by default — blueprint will use the corresponding action rather than importing them as processes check/uncheck behavior matched and unchecked — page is not imported; it is converted to an action using blueprint's repository matched and checked — page is imported as a process unmatched and checked — page is imported as a process unmatched and unchecked — page is excluded entirely and removed from all missing process diagnostics