- Release notes
- Getting started
- Installation
- Configuration
- Integrations
- Authentication
- Working with Apps and Discovery Accelerators
- AppOne menus and dashboards
- AppOne setup
- TemplateOne 1.0.0 menus and dashboards
- TemplateOne 1.0.0 setup
- TemplateOne menus and fashboards
- TemplateOne 2021.4.0 setup
- Purchase to Pay Discovery Accelerator menus and dashboards
- Purchase to Pay Discovery Accelerator Setup
- Order to Cash Discovery Accelerator menus and dashboards
- Order to Cash Discovery Accelerator Setup
- Basic Connector for AppOne
- SAP Connectors
- 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
- SAP Order to Cash Connector for AppOne
- SAP Purchase to Pay Connector for AppOne
- SAP Connector for Purchase to Pay Discovery Accelerator
- SAP Connector for Order-to-Cash Discovery Accelerator
- Superadmin
- Dashboards and charts
- Tables and table items
- Application integrity
- Maintain Application integrity
- Finding Application issues
- Solving Application issues
- How to ....
- Working with SQL connectors
- 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
- Useful resources
Finding Application issues
You can find issues by running a Quick scan or a 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.
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.
|
Step |
Action |
|---|---|
|
1 |
Click on Tools in the lower left corner of your open application window. |
|
2 |
Click on the blue Issues pane icon. The Issues pane opens, displaying the results of the last performed scan. |
|
3 |
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.
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:
- Errors
- Deprecates
- Warnings
-
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.
