Process Details

Process Tabs

After clicking on a process from any page within Analyze, users will be directed to the Details Tab of that process, where they can navigate to any of the other associated tabs.

Header Options

Export Reports

Users can export any table related to the [Flow/Automation/Process/Main Task Bot] they are currently viewing.

1. Click the Export Reports button on the top right and select the report(s) you want to export. This will submit a job that you can monitor on the Jobs page. Once the job is complete, you can download your report(s) by clicking the download icon next to the completed job.

See Flow in PAD

For flows imported from Dataverse, users will have an additional "See Flow in PAD" button. This feature allows users to open the current PAD flow directly from Blueprint.

Create Specification

Users can summarize all information about a process in Assess as an exportable document, similar to a PDD or SDD.

1. Click Create Specification button on the top right and select the pieces of information you wish to include. You can also drag and reorder items to organize the content as desired.
   The document can be exported as a PDF or Word file.

Details

The Details tab displays high-level information about the process, organized by several topics.

General Information

PAD - Additional Information (if imported from Dataverse)

Security

Characteristics

Custom and Legacy Content

This section allows users to add any information that may not have been captured during the import to Analyze.

• To add new information, click the Add New button in the top right. Users can name the Additional Information section and include any rich text description they like.
• To add existing legacy documentation, click the Import Document button in the top right. This will allow users to import any word document. Each document section will appear as a new row in the Custom and Legacy Content section.
  • Document sections will appear in the table in the same order they exist in the document
  • Descriptions of the sections will be in rich-text in the side-panel editor
  • Fonts, tables, images, and other rich text elements will appear as they were in the original document

Tags

Users can apply existing tags to the current process by clicking the Tags field and selecting from the available options.

Description

Users can add a description to the process. If the user has set up their GenAI settings and the toggle is ON,  they will see an option to Generate with AI. This option creates a detailed summary of the current process, including information on accessed applications.

Subflows/Sub-Process/Pages/Child Task Bot

This page provides high level details to all sub-processes that are called by the current process.

Table Glossary

Apps

Within the Apps tab, users can view information on Native and External applications accessed by the current process.

To switch between Native Application Information and External Web/UI Applications, click the dropdown in the center.

• Native Apps are applications that your RPA platform supports natively. 

Native Application Information - Table Glossary

• External Apps are applications that your RPA platform interacts with using generic actions (e.g., Run Application, Launch Browser). Some of these may overlap with Native App interactions.

External Application Information - Table Glossary

Compliance

The Compliance tab displays information on all compliance violations for the current process

Table Glossary

Opportunities

The Opportunities tab displays potential opportunities for reuse or cloud transformation in the current process. To switch between Reusability and Cloudability, click the dropdown in the center.

Reusability

Example:

• Process A has 10 actions that match with both Process B and Process C.
• Process B has only 8 of those 10 actions that match with both Process A and Process C.
• Process C has 14 matching actions in total, which include the 10 from Process A and the 8 from Process B.

So, although the Flows share actions, the total number of actions can be different because one Flow may contain more or fewer matching actions than another.

Card Glossary (Left)

Graph Legend (Right)

All Reuse Opportunities - Table Glossary (Bottom)

Cloudability

User can definite a Cloudability Threshold setting in Settings > Analyze > Analyze Settings > General Settings.

Analyze will display Cloudability metrics for all processes in the current Flow/Automation/Process/Main Task Bot, but those that surpass the defined Cloudability Threshold will be highlighted in the charts and table for added visibility.

Card Glossary (Left)

Graph Legend (Right)

All Cloud Opportunities - Table Glossary (Bottom)

Reviews

The Review tab enables users to collaborate and conduct manual reviews of their processes.

Review Status

Reviews can have 3 statuses

1. Not Approved – Any process not in state Approved or Code Changed
2. Approved – Any process that has been Approved by a user
3. Code Change – If a newer version of the process is reimported, it should go through the review process again. Blueprint will automatically label newer versions of imported processes as a Code Change.

Actions

On the right side of the page, users can choose to:

• Leave a Comment
• Approve – Users can optional leave a comment on approval as well

Any action will be logged in the table on the left in chronological order.

Reviewers

Any user that Leaves a Comment or Approves is automatically added as a Reviewer. Users can also manually add other reviewers by clicking the whitespace in the Reviewers field and typing the name of a user in Blueprint.

Tests

The Tests tab allows users to create new Tests or see all existing Tests for the current process.

Table Glossary

Create New Tests

1. From the Tests tab, click the Create button in the top right
2. Select the type of test from the dropdown
   1. AI Generated Manual
   2. Automated (PAD only)
   3. Manual

Create Manual Tests

• AI Generated Manual – Requires user to set up their GenAI Settings.
  • Blueprint’s trained AI model will analyze the current process and generate Tests, Test Steps, and a Description for your manual test.
• Manual
  • User will be prompted to provide Test Steps and a Description for their test.

Submit Manual Test Runs

1. Fill out the Manual Test Run fields on the right, including:
   1. Start Date
   2. Test Result
   3. Add any comment or notes that should be added
   4. Click Submit

Create Automated Tests (PAD Only)

Requires user to set up Dataverse Synchronization and Service Account Secret. See Settings and Configuration - Power Automate Desktop

• In the set up wizard, user will need to:
  • Select Connection
  • Select Mode
• In the Automated Test Details page, user will need to:
  • Set a schedule for the Test to run
  • Create Test Cases - Users can select any PAD action within the flow and configure any number of asserts that must be met during runtime. If any assert is not met, the test will fail.
  • When finished setting up the Automated Test, click "Publish" in the top right

Test Runs

The Test Runs tab displays data on the Runs associated with the given process, provided there is an associated Test.

Test Coverage (PAD Only)

This is the percentage of total actions that have been executed in at least 1 Automated Test Run. Total Coverage only accounts for Test Runs since the most recent modification date. If a newer version of the Flow has been imported, Test Coverage resets to 0%.

Table Glossary

Diagrams

The Diagram tab displays the Blueprint-generated Process Diagram, Structure Diagram, and any custom diagram the user has created.

On import, Blueprint will automatically generate a Process Diagram (either with or without GenAI) and a Structure Diagram.

1. Structure Diagram - Displays the entire process call tree and provides detailed information on each individual sub-process.
   1. Features:
      1. Click each shape to view detailed information, including:
         1. Generating an AI description of the subprocess
         2. Number of Actions
         3. Cloudability Opportunities
         4. Reuse Opportunities
         5. Number of Applications interacted with
         6. Risk Level
         7. Sensitive Data Detected ( )
      2. A thin, vertical bar on the right side of each shape is color-coded based on complexity.
      3. A legend located at the top left indicates:
         1. If a sub-process is reused multiple times within the call tree.
         2. If a sub-process is referenced but was not included during import.
         3. The complexity color coding.
      4. A "Center on Root" button, located at the top left, allows you to bring the root shape into focus quickly.
      5. Click the minus icon under any shape with dependencies to collapse the tree from that point on
      6. Clicking any "External Process" shape will take you to that process's Structure Diagram
2. Process Diagram - A high-level process diagram detailing what the bot does. Users can click any shape to see more information about the specific process being represented. Users can also add or modify the Process Diagram using the BPMN Shape Library on the left side.
   1. AI Generated Diagram – A higher level process diagram
      1. Requires the user has set up their GenAI and the toggle is ON (See Settings and Configuration - GenAI)
   2. Blueprint Generated Diagram – A more technical process diagram

Users can also create custom Diagrams by clicking the Create button on the top right and using the provided Shape Library.

Flow Activity (Analyze - PAD only)

The Flow Activity tab displays operational data on current PAD Flow, provided it has run in the connected Environment. For more information, see this article.

Card Glossary

Chart Glossary

Certain metrics are considered anomalous if they are +/- 3 standard deviations away from the mean. Metrics with Anomaly tracking will have a legend indicating Average and ± std.dev*3

Table Glossary

Changes (Analyze - PAD only)

Within the Changes tab, users can see historical versions of PAD Flows (called flow-versions). Every time a user explicitly imports a flow-version it will appear in the table. 

In addition, Blueprint Assess will automatically retrieve flow-versions from Power Platform once a day if the flow has been changed and the user hasn’t imported it in a 24 hour period.  

The “Import User” column shows whether a flow-version was imported by a user, or automatically by the Blueprint Assess product.

Table Glossary

Renamed Subflow Similarity Level

When a renamed sub-flow also has its contents change, it is subjective when you’d call it a new sub-flow vs. a renamed sub-flow.  If you change the name and one character within it, you would consider it the same sub-flow just with a different name (renamed).  However if you change its name and completely re-write the contents, you would consider it an entirely different flow.  Blueprint Assess lets you adjust the level at which you’d consider it a renamed vs. new sub-flow with this percentage field.  The default is set to 75%.

Comparing Flow-Versions

1. Select any two (2) flow-versions. The Compare button will become available only when two flow-versions are selected.
2. Click the Compare button to see the list of sub-flows and their change status. There will be two tabs available at the top called Subflows and Variables

Subflows

• Click a changed Subflow to see detailed changes

• Differences Tab:   Shows precise changes using red-strike font for deletions and green font for additions
• Older Version Tab:  Shows actions of the original/older flow-version
• Newer Version Tab:  Show actions of the newer flow-version

Variables

Display all Input, Output, and Flow variables that have changed between the selected versions

• Shows precise changes using red-strike font for deletions and green font for additions

Schema V1 Flow-Versions

Sometimes a flow-version has a “V1*” appended to its name (see below). This denotes that the flow has been stored in Power Platform using Dataverse schema v1, whereas all other flow-versions are stored using Dataverse schema v2. 

When Blueprint Migrate creates PAD flows, they are stored in schema v1.  The first time a developer edits the flow, it is then saved in schema v2 going forward. Therefore, only the first/oldest flow-version should ever have this annotation.

When a user chooses to compare a schema v2 flow-version with a schema v1 flow-version, they will not only see changes that were made by a developer, but will also see the schema differences which may be confusing.  For this reason, Blueprint highlights schema v1 flow-versions and provides a note explaining this for the user.