- Hardware and Software Requirements
- Server Installation
- Updating the License
- Deploying the UiPath Process Mining Profiler
- Deploying a Connector (.mvp)
- Updating UiPath Process Mining
- Updating a Customized Version of an App or Discovery Accelerator
- Installing a Training Environment
- Set up Single Sign-on Through Azure Active Directory
- Set up Single Sign-on Through Integrated Windows Authentication
- Adding Superadmin AD Groups
- Adding End-user AD Groups
- Two-Factor Authentication
- Introduction to AppOne
- Analyzing Data in AppOne
- Overview of Menus and Dashboards in AppOne
- Introduction to Purchase-to-Pay Discovery Accelerator
- Analyzing Data With Purchase-to-Pay Discovery Accelerator
- Overview of Menus and Dashboards
- Menu Compliance
- Deploying the Basic Connector
- Introduction to Basic Connector
- Input Tables of the Basic Connector
- Adding Tags
- Adding Automation Estimates
- Adding Due Dates
- Adding Reference Models
- Setting up Actionable Insights
- Setting Collapsible Charts
- Using the Output Dataset in AppOne
- Output Tables of the Basic Connector
- Introduction to SAP Connector
- SAP Input
- Checking the Data in the SAP Connector
- Adding Process Specific Tags to the SAP Connector for AppOne
- Adding Process Specific Due Dates to the SAP Connector for AppOne
- Adding Automation Estimates to the SAP Connector for AppOne
- Adding Attributes to the SAP Connector for AppOne
- Adding Activities to the SAP Connector for AppOne
- Adding Entities to the SAP Connector for AppOne
- HTML Panels
- Migrating Legacy Charts to New Charts
- Join Tables
- Global Tables
- Introduction to Table Items
- Display Format
- Rebrand and Restyle Apps and Discovery Accelerators
- Use Sharding in Your Applications
- Create an Anonymized Dataset
- Set up Automated Data Refreshes
- Use an Access Matrix to Enable Role-Based Access to Data
- Introduction to SQL Connectors
- Setting up a SQL Connector
- CData Sync Extractions
- Running a SQL Connector
- Editing Transformations
- Releasing a SQL Connector
- Scheduling Data Extraction
- Structure of Transformations
- Using SQL Connectors for Released Apps
- Generating a Cache With Scripts
- Setting up a Local Test Environment
- Separate Development and Production Environments
Finding Application Issues
You can find issues by running a Quick scan or a Full scan.
Quick Scan Vs. Full Scan
The Quick scan is a light-weight and fast way to scan for the most obvious issues. With the Quick scan, data and expressions (except for deprecated expressions) are ignored. A Quick scan will take up at the last two seconds.
The Full scan performs an in-depth evaluation of your application, covering expressions, actions etc. and may take up significantly more time.
To help you to find errors fast, a quick scan is automatically started when you open your application. If any errors or deprecated functions are detected, the Tools panel opens, where you can check the issues.
When the Commit dialog is opened from within your application a full scan of your application is started in the background to help you to find any issues before you commit your application changes.
The results of the scan are displayed in the Full scan results pane in the Commit dialog. See illustration below.
Click on Go to issues… to open Issues pane in the Tools panel where you can check the issues found.
See illustration below.
Manually Starting Scans
From the Issues pane in the Tools panel, you can manually start a Quick scan or a Full scan.
Follow these steps to manually start a scan.
Click on Tools in the lower left corner of your open application window.
Click on the blue Issues pane icon. The Issues pane opens, displaying the results of the last performed scan.
Click on QUICK SCAN or FULL SCAN in the header of the Issues pane.
The Issues pane is cleared, and the requested scan is started.
Cancel Full Scan
For large applications, the full scan may be time consuming and you may want to cancel the scan before it is finished.
A full scan consists of five stages. When you cancel the scan, the results up to the last successful finished state are displayed. Press Esc or Cancel to cancel a full scan.
The results of the last performed scan are displayed in the Issues pane of the Tools panel. It also displays the time when the last performed scan was finished. The issues are grouped and listed in order of importance:
Informational messages.Note: A summary of the scan results with the number of issues found in each category is displayed in the header of the Tools panel. This is also visible when the Tools panel is not open.
When working on an expression the Expression editor provides you with immediate feedback when an issue is found. The category of the issue is displayed in front of the line, and what is wrong is underlined with the corresponding color. The same issue categories as used in the quick scan and the full scan are used in the Expression editor.
See illustration below.