What does a scan look for? #
The scans search for adherence or its lack to the following rules:
- Common rules, i.e.:
- Technical best practices by SaaS platform vendor (ServiceNow, Salesforce and Office 365)
- Software development industry standards
- Quality Clouds recommended best practices
- Custom rules – client-defined technical best practices
Types of scans #
Full scan #
A full-code scan is a unique time Quality Clouds runs the quality checks of a SaaS platform instance. The full-code scan creates a complete drill-down view of the quality data, and it refreshes all the views.
Platforms available: ServiceNow, Salesforce and Office365.
Where to launch the scan: Schedules, Launch scan section.
Where to view the issues: Views on ServiceNow, Salesforce and Office365 platforms.
Profiling scan #
A profiling scan is a scheduled scan, run on a frequent, regular basis (usually weekly, depending on your pricing scheme) to check for the health of your instance and generate the high-level KPIs only in the Instance Profiling view.
Platforms available: ServiceNow, Salesforce and Office365.
Where to launch the scan: Schedules, Launch scan section.
Where to view the issues: Views on ServiceNow, Salesforce and Office365 platforms.
Operational scans #
This is an add-on to Quality Clouds. See our solutions and pricing for more information: https://www.qualityclouds.com/contact/.
The operational scan is an automated process that runs periodically against your productive SaaS environments and warns you about alerts that need attention. The scan is scheduled to run daily and results in an email report. Find out more here.
Platforms available: ServiceNow, Salesforce and Office365.
Where to launch the scan: Schedules, Launch scan section.
Where to view the issues: Alert view on ServiceNow, Salesforce and Office365 platforms.
Update set scan (ServiceNow) #
This is an add-on to Quality Clouds. See our solutions and pricing for more information: https://www.qualityclouds.com/contact/.
An update set scan gives you a visual list of the type of issues found and a link to the ServiceNow pages with the best practices. For more information about how to analyze your ServiceNow update set, click here.
Platforms available: ServiceNow.
Where to launch the scan: ServiceNow App, Schedules and Launch scan section.
Where to view the issues: ServiceNow App and LiveCheck ServiceNow view.
Feature branch scan (Salesforce and Office365) #
Checks all the changes you’re working on in a feature branch before deploying them to a Git master branch.
The feature branch scans run against different repositories on each scan, and only scan the changes that have been committed to the feature branch. The name of the feature branch needs to be specified at the time of launching a scan.
For Salesforce, you can run the feature branch scans from the portal and from the app.
For the time being, you can only see the issues detected by a scan in the app. See more in Working with scans in the app.
Platforms available: Salesforce and Office365.
Where to launch the scan: Salesforce App, and Launch scan section.
Where to view the issues: Salesforce App and views on Salesforce and Office365 platforms.
Application Scan (ServiceNow) #
Platforms available: ServiceNow.
Where to launch the scan: ServiceNow App.
Where to view the issues: ServiceNow App and ServiceNow LiveCheck view.
→ Next steps for working with scans #
Scanning Update Sets In ServiceNow
What is being scanned? #
Depending on the SaaS platform, Quality Clouds scans different elements. Both code and configuration is being scanned.
Quality Clouds does not analyse or scan any data.
The following element types are being checked:
Where does a scan run? #
Each scan runs on Quality Clouds secure and reliable environment from top cloud service providers. The code is parsed in-memory, and is never stored anywhere.
What is the result of a scan? #
The results of the scan is a set of metrics and indicators per instance. The result (not the code or data) is stored and displayed in the views.
