Estimator Reports
13 min
the estimator provides four report views accessible from the center dropdown within the estimator dashboard all exports trigger a job — navigate to jobs and click download ( ) to retrieve the file estimator report orders all call trees by size and complexity, largest first use this report to understand migration effort per call tree and compare blueprint assisted vs manual migration timelines exporting export current view to excel — exports two sheets the dashboard table as displayed, and adjustable metrics at time of export export consolidated todos and compiler errors to excel — exports three sheets todos grouped by type (parameters removed), compiler errors grouped by type (parameters removed), and metrics at time of export export estimator template to excel — exports a comprehensive migration planning workbook with adjustable productivity metrics, contingency factors, and bot complexity classifications; white background cells are editable table columns rank — blueprint's ordering of all call trees by size and complexity; rank 1 is the largest and most complex metrics call tree — name of the root (main) process hierarchy — the folder path of the call tree estimated completion effort (hrs) — the effort to bring blueprint's migrated pad code to a production ready state blueprint effort saved (hrs) — the amount of effort, in hours, blueprint saves compared to doing the migration manually manual rewrite effort (hrs) — the effort to rewrite the selected scope by hand advanced estimator report orders all call trees by size and complexity, largest first use this report to understand migration effort per call tree and compare blueprint assisted vs manual migration timelines exporting export current view to excel — exports two sheets the dashboard table as displayed, and adjustable metrics at time of export export consolidated todos and compiler errors to excel — exports three sheets todos grouped by type (parameters removed), compiler errors grouped by type (parameters removed), and metrics at time of export export estimator template to excel — exports a comprehensive migration planning workbook with adjustable productivity metrics, contingency factors, and bot complexity classifications; white background cells are editable table columns rank — blueprint's ordering of all call trees by size and complexity; rank 1 is the largest and most complex metrics call tree — name of the root (main) process hierarchy — the folder path of the call tree completely migrated actions — actions that migrated to pad without a compiler error actions with compiler errors — actions that migrated but contain a compiler error requiring manual fix compiler errors — total compiler error count; a single action can contain multiple errors todos — todo comments requiring review, completion, or refactoring selectors — total selector count effort blueprint saves (est ) — estimated hours saved by using blueprint (completely migrated actions ÷ rpa developer productivity) + (compiler errors ÷ compiler error fix rate) effort to complete code with blueprint todo fix effort (hrs) — estimated hours to resolve todos compiler error fix effort (hrs) — estimated hours to resolve compiler errors selector fix effort (hrs) — estimated hours to respy non functional selectors total effort (est ) — sum of todo fix effort and compiler error fix effort manual migration total manual effort (est ) — estimated hours to manually rewrite the call tree without blueprint view call tree — click to generate a visual diagram of the call tree selector report the rows in this report show screens and elements being accessed by the automation, and the pad selectors that will be used to access them notes for type ui, the row could represent either an element selector, or a window selector (when element is empty) for type web, the row is always an element selector there might be multiple selectors generated for an element clicking the "info" icon that appears in the selector column will show all generated selectors ⓘ click combine duplicate selectors to merge duplicate selectors that interact with the same web or ui application, even when the page or window name differs exporting export current view to excel — exports the table as displayed table columns type — either ui or web interaction domain / ui application — web domain or name of the ui application web page / window name — full url or window name of the ui application element — name of the element selector — the selector that will be generated in pad click the 'info' icon to view more than one selector references — number of times the element is referenced across different actions maintainability orders all call trees by maintainability score, least maintainable first use this report to identify automations that may require additional cleanup work after migration exporting export current view to excel — exports the table as displayed plus two additional columns process id and maintainability score table columns maintainability rank — ordering of all call trees from least to most maintainable; rank 1 is the least maintainable call tree — name of the root (main) process target actions — number of pad actions in the migrated output, including comments and regions target actions / source actions — ratio of pad output lines to source actions in blueprint # target regions — count of regions used in the pad output # user comments — count of comments in the export # target subflows — count of subflows created in the pad output # unmapped reuse opportunities — count of reuse opportunities not yet implemented # complex nested ifs — count of if statements nested four levels deep or more # complex expressions — count of complex expressions in the export failed exports lists all call trees that failed to export during estimator calculation processes in this report are excluded from effort estimates exporting export current view to excel — exports the table as displayed table columns process id — blueprint id of the main process that failed to export process name — name of the main process that failed to export