An issue represents a single non-compliance with a best practice or rule within your instance.

How Is Issue Severity Assigned?

#

Issue severity is determined based on several factors that influence the Quality of Cloud (QoC) calculation.
Each scan evaluates all detected issues and assigns a severity level that contributes to the global quality score.

Below are the severity levels with examples of issues that may fall under each one.

Severity Level: High

#

Issues marked High impact essential requirements and often indicate practices that can degrade system usage or testing.
These issues significantly contribute to the QoC reduction.

 Examples of High-Severity Issues:

•  Business Rule affected
•  Unused inactivity with monitors
•  Synchronous AJAX calls (getReference, getXMLWait) in Client Scripts
•  GlideRecord usage in Client Scripts affecting Portal Widgets
•  High Security Settings plugin disabled
•  DOM manipulation in Client Scripts
•  DOM manipulation in UI Policies
•  OnBefore Business Rules updating records on current tables
•  Business Rules using SOAP getResponse
•  Contextual Security Plugin disabled
•  “Security Manager” set to Allow Access
•  UI Policies using GlideRecord
•  SOAP Timeout > 500 minutes
•  JavaScript – Avoid usage of WebDB
•  JavaScript – Avoid Function Constructors
  
  

Severity Level: Medium

#

Medium issues affect important requirements but usually have moderate remediation difficulty.
They still contribute to the QoC score.

 Examples of Medium-Severity Issues:

•  Client Scripts using console.log
•  Client Scripts without a function wrapper
•  Modules pointing to large tables without filters
•  User Preference “Rows per Page” > 100
•  “Items per Page” system property > 100
•  JDBC Data Sources with Use last run datetime unchecked
•  “Update on Iterate” enabled
•  Server UI Actions using GlideRecord and getRowCount
•  Users with excessive rows per page
•  Hard-coded sys_id in Client Scripts
•  Hard-coded sys_id in UI Policies
•  Hard-coded sys_id in Script Includes
•  Hard-coded sys_id in Transform Scripts
•  “Auto-Complete Wait Time” > 750 ms
•  Catalog Client Scripts using console.log
  
  

Severity Level: Low

#

Low-severity issues affect minor requirements and are relatively easier to remediate.
They still contribute to the QoC indicator.

Examples of Low-Severity Issues:

•  Transform Maps with “Run business rules” enabled
•  Business Rules with debugging statements in production
•  Business Rules using eval()
•  TaskSLAController trace level not set to notice
  
•  “Go To search” set to “contains”
•  Debug properties enabled in production
•  Client Scripts with an empty script field
•  “Auto-complete Search” set to “contains”
•  Script Includes with debugging in production
•  Catalog Client Scripts with empty script fields
•  JavaScript – Avoid usage of alert()
  
  

Severity Level: Warning

#

A Warning is assigned when issues from any level (High, Medium, Low) are found in:

•  Inactive configuration items
•  Commented-out code
  
  

⚠️ Warnings do NOT contribute to the Quality of Cloud calculation or to the global count of issues in a scan.

 Examples of Warning-Level Issues:

• Any High/Medium/Low issue detected on inactive CIs
• Any High/Medium/Low issue inside commented-out code