- Release Notes Cloud Insights
- Getting Started
- Access and Permissions
- Notifications
- Interacting with Insights
- Action Center Integration
- Automation Hub Integration
- Autopilot integration
- Document Understanding Integration
- License monitoring integrations
- Real-time Monitoring
- Real Time Data Export
- Troubleshooting
Insights
Automation Hub ROI Data Model
The ROI explore brings together data from Automation Hub and Orchestrator, joining them based on the idea to Orchestrator package linkage performed under the Execution Assessment in Automation Hub.
Custom Fields | Custom Dimension; Custom Measure; Table calculation;
Start from scratch or use existing Dimensions and Measures to create new fields in the Data Model. Perform enhancements and data transformations by using formulas, filters, sorts. |
Dimension Group | Dimensions | Type | Description |
---|---|---|---|
Average of Reviews | Number | Average of the ratings given by the reviewers | |
Component URL | String | URL of the component | |
Creation Date |
| Date | Date when the component was created |
Is Active (Yes / No) | Yes/No | Showing if the component is deleted or not (Yes = component is not deleted, No = component was deleted) | |
Name | String | Name of the component, as defined by the author | |
Summary | String | Summary of the component, as defined by the author | |
Type | String | Type of component: custom activity, snippet, workflow template, connector, dashboard, ML model, solution | |
Versions | Number of Downloads | Number | Number of component downloads performed by the users |
Versions | Status | String | Status of the component's version |
Versions | Version | String | Version number for the component |
Versions | Version Creation Date | Date | Date when the component's version was created |
Versions | Version Creation Month | Date | Date when the component's version was created |
Versions | Version Creation Quarter | Date | Date when the component's version was created |
Versions | Version Creation Time | Date | Date when the component's version was created |
Versions | Version Creation Week | Date | Date when the component's version was created |
Versions | Version Creation Year | Date | Date when the component's version was created |
Measure | Type | Description |
---|---|---|
Count | Number | Count of components, based on the applied dimensions |
Dimension Group | Dimensions | Type | Description |
---|---|---|---|
Execution Info | Process Uses Queues | Number | The answer to the "Using queue" question in the AH Execution assessment |
Measure Group | Measures | Type | Description |
---|---|---|---|
Actual Benefits | Total Actual Automated Volumes | Number | Sum of all the successful job runs or successful queue item runs (if using queues) |
Actual Benefits | Total Actual Cost Savings | Number | Sum of all the actual costs savings, obtained as per run cost saving * successful runs. Group by process and/ or idea. |
Actual Benefits | Total Actual Hours Saved | Number | Sum of all the actual hours saved, obtained as per run time saving * successful runs. Group by process and/ or idea. |
Execution Info | Cost Savings Per Run | Number | Cost savings per one successful job / queue item run, measured in the service currency, as auto-computed in the Execution assessment |
Execution Info | Time Savings Per Run | Number | Time saved per one successful job / queue item run, measured in minutes, as auto-computed in the Execution assessment |
Prorated Benefits | Prorated Target Cost Savings | Number | Target cost savings adapted to the time span on which the process was run (prorated) |
Prorated Benefits | Prorated Target Hours Saved | Number | Target hours saved adapted to the time span on which the process was run (prorated) |
Prorated Benefits | Prorated Target Volumes | Number | Target automated volumes adapted to the time span on which the process was run (prorated) |
Target Benefits | Yearly Target Automated Volumes | Number | Estimated yearly number of transactions / runs that will be performed by the automation successfully. This is computed based on the Automation Hub Detailed or Citizen developer assessment data |
Target Benefits | Yearly Target Cost Savings | Number | Estimated yearly cost savings based on the metadata collected in Automation Hub, in the Execution assessment. Group by process and/ or idea |
Target Benefits | Yearly Target Hours Saved | Number | Estimated yearly hours saved based on the metadata collected in Automation Hub, in the Execution assessment. Group by process and/ or idea |
Dimension Group | Dimensions | Type | Description |
---|---|---|---|
Category 1 | Level Name | String | Category Level Name |
Category 1 | Name | String | Category Name |
Category 1 | Order Number | Number | The order in which the categories are displayed in the Automation Hub user interface |
Category 2 | Level Name | String | Category Level Name |
Category 2 | Name | String | Category Name |
Category 2 | Order Number | Number | The order in which the categories are displayed in the Automation Hub user interface |
Category 3 | Level Name | String | Category Level Name |
Category 3 | Name | String | Category Name |
Category 3 | Order Number | Number | The order in which the categories are displayed in the Automation Hub user interface |
Category 4 | Level Name | String | Category Level Name |
Category 4 | Name | String | Category Name |
Category 4 | Order Number | Number | The order in which the categories are displayed in the Automation Hub user interface |
Category 5 | Level Name | String | Category Level Name |
Category 5 | Name | String | Category Name |
Category 5 | Order Number | Number | The order in which the categories are displayed in the Automation Hub user interface |
Dimension Group | Dimensions | Type | Description |
---|---|---|---|
Answer (DateTime) Date |
| Date | The Answer converted to a DateTime value |
Question | Assessment Source | String | This will indicate the type of Assessment the question belongs to (Overview, high-level assessment etc.) |
Question | Key | String | The unique identifier of a Question, corresponding to the Variable name in the user interface. Title is not guaranteed to be unique. |
Question | Title | String | The Question Title as configured in the Assessment |
Measures | Type | Description |
---|---|---|
Count | Number | Count of date-type questions |
Max Date | Time | Maximum date from the answers of date-type questions |
Min Date | Time | Minimum date from the answers of date-type questions |
Dimension Group | Dimensions | Type | Description |
---|---|---|---|
Answer | Display Value | String | The answer value displayed in the UI |
Answer | Raw Value | Number | The answer value, as it is stored in the database |
Question | Assessment Source | String | This will indicate the type of Assessment the question belongs to (Overview, high-level assessment etc.) |
Question | Key | String | The unique identifier of a Question, corresponding to the Variable name in the user interface. Title is not guaranteed to be unique. |
Question | Title | String | The Question Title as configured in the Assessment |
Measures | Type | Description |
---|---|---|
Count | Number | Under the Count measure, we count all the answers from the various questions of type numerical and/or percentage - this requires additional filtering. |
Average | Number | Under the Average measure, we average all the answers from the various questions of type numerical and/or percentage - this requires additional filtering. |
Sum | Number | Under the Sum measure, we sum up all the answers from the various questions of type numerical and/or percentage - this requires additional filtering. |
Dimension Group | Dimensions | Type | Description |
---|---|---|---|
Applications | Application Full Name | String | Concatenation of the application name, version and language for easier search |
Applications | Application Language | String | Language of the application as defined in the Application Inventory |
Applications | Application Name | String | Name of the application as defined in the Application Inventory |
Applications | Application Version | String | Version of the application as defined in the Application Inventory |
Auto-generated ID | Number | Unique ID assigned to each idea, in the Tenant database | |
Collaborators | Active user | Number | User is active: 1 (Active) , 0 (Inactive), 3 (Deleted) |
Collaborators | Business Unit | String | User’s Business Unit |
Collaborators | Collaborator Role | String | Role of this collaborator |
Collaborators | Department | String | Department of this collaborator |
Collaborators | String | User's Email address | |
Collaborators | First Name | String | User’s First Name |
Collaborators | Last Name | String | User’s Last Name |
Collaborators | Location | String | User's Location |
Creation Date |
| Date | Idea Creation Date. Can be different than the Submission date, in case of ideas saved of draft first. |
Idea Name | String | Idea Name, as defined in the field Automation Name | |
Idea Slug | String | Idea's slug used to construct Idea URL. It is unique. | |
Idea Source | String | Submission type (eg Employee-driven; CoE-driven; Task Mining; Process Mining; Citizen Developer; Change Request) | |
Idea URL | String | Idea's URL | |
Idea Path | String | Idea's Path contains everything except the base path (ex. cloud.uipath.com) | |
Last Update Date |
| Date | Last idea update - can be a change in the Phase, Status, details in the automation profile, Cost-Benefit Analysis, documentation. |
Phase | Phase Name | String | Phase Name as displayed in the user interface |
Phase | Phase Order | Number | Phase Order in the idea's lifecyle |
Priority | Number | Idea's Priority | |
Q&A - All types | Answer Display Value | String | The answer value displayed in the UI |
Q&A - All types | Answer Raw Value | String | The answer value, as it is stored in the database |
Q&A - All types | Question Assessment Source | String | This will indicate the type of Assessment the question belongs to (Overview, high-level assessment etc.) |
Q&A - All types | Question Key | String | The unique identifier of a Question, corresponding to the Variable name in the user interface. Title is not guaranteed to be unique. |
Q&A - All types | Question Title | String | The Question Title as configured in the Assessment |
Status | Phase Status Name | String | Phase Status name as displayed in the user interface |
Status | Phase Status Order | Number | Phase Status order |
Submission Date |
| Date | Idea Submission Date |
Tags | Tag Name | String | List with all the Tags created. When associated with an Idea Name, reflects the tags applied for the idea. |
Measures | Type | Description |
---|---|---|
Count | Number | Total number of submitted Ideas |
List of Unique Idea Names | String | Concatenates all Unique Idea names. |
Sum | Number | Under the Sum measure, we sum up all the answers from the various questions of type numerical and/or percentage - this requires additional filtering. |
Organization scoped view | |
---|---|
Dimensions |
Description |
Tenant field | The name of the tenant where the idea is defined. This is only available in Organization scoped views |
Dimension Group | Dimensions | Type | Description |
---|---|---|---|
Folder | String | Folder where the job is defined | |
Process Name | String | The name of the process | |
Robot Type | String | The type of robot that executed the job. The available options are: Attended, Unattended, NonProduction, Testing, Other | |
Run Date |
| Date |
Measures | Type | Description |
---|---|---|
Successful Job Runs | Number | Count of Successful Job Runs |
Successful Queue Runs | Number | Count of Successful Queue Runs |
This view, part of the Jobs explore, matches processes to specific apps that it interacts with.
Data | Description |
---|---|
Application Name | The name of the application. If it's a web application, it will be the browser name. If the application name is a dynamic parameter, the name will be unknown. |
Application Name Or Url | It's a URL if the application is web application, otherwise it's the application name. It shows as unknown if both application and URL are dynamic parameters. |
Application Type | The type of application. |
Application Url | URL of the web application. It's displayed as unknown if it's parameter. |
Folder | The folder where the process is located. |
Package Creation Date | The date when the packages was created. |
Package Id | The ID of the package. |
Process Creation Date | The date when the process was created. |
Process Display Name | The display name of the process. It's updated when the process package version is updated. |
Process Id | The ID of the process. |
Process Name | The name of the process package. |
Process Version | The active version of the process package. A process can have multiple versions and it's the active version or the last configured version. |
Process Version Creation Date | The date of when the process’s version is updated. |
Process Version Id | This is updated when the package is updated in the process. |
The Process Application views are associated with the following Explores: Jobs, Jobs - Org.
Measures | Description |
---|---|
List of Unique Application Names | Concatenates all unique application names. |
List of Unique Process Display | Concatenates all unique process displays. |
List of Unique Process Names | Concatenates all unique process names. |
List of Unique Urls | Concatenates all unique URLs. |