Severity of issues

Several topics may trigger severity issues in the calculation (results) of the Quality of Cloud indicator. The different levels of severity issues are calculated on the global count of issues associated with each scan. Find below the different levels of severity issues along with examples of some of the issues that can be raised.

Severity Level 'High'

Issues ranked among the 'High' level affect essential requirements for which there are measures to resolve at a high level. The usage or testing of the system may proceed in a debased manner. The severity issues contributes to the cloud indicator. 

Please find below the list of some of the issues raised with severity level 'High':

  • Business Rule affected
  • Unused Inactivity with the monitors
  • Synchronous AJAX call (getReference, getXMLWait) in Client Scripts
  • GlideRecord usage on Client Scripts affecting the Portal Widget
  • High Security Settings plugin disabled
  • Document Object Model (DOM) manipulation in Client Scripts
  • Document Object Model (DOM) manipulation in UI Policies
  • OnBefore Business Rules updating records on current tables
  • Business Rules using the SOAP getResponse method
  • Contextual Security Plugin disabled
  • The "Security Manager" System Property default behaviour set to "Allow Access
  • UI Policies using GlideRecord
  • SOAP Timeout Value over 500 minutes

  • Javascript - Avoid use of WebDB

  • Javascript - Avoid use of Function Constructors

Severity Level 'Medium'

Issues ranked among the 'Medium' level affect essential requirements for which there are measures to resolve at a medium level. The severity issues contributes to the cloud indicator. 

Please find below the list of some of the issues raised with severity level 'Medium':

  • Client Scripts with the console.log debugging method
  • Client Scripts without function
  • Modules pointing to big tables without a filter
  • The default system User Preference 'Rows per Page' set above 100
  • The "Items per Page" System Property includes options over 100
  • JDBC Data Sources with 'Use last run datetime' option unchecked
  • The 'Update on Iterate' System Property enabled
  • Server UI Actions using GlideRecord and getRowCount
  • Users with too many rows per page

  • Client Scripts with hard-coded sys_ids

  • UI Policies with hard-coded sys_ids
  • Script Includes with hard-coded sys_ids
  • Transform Scripts with hard-coded sys_ids
  • The "Auto-Complete Wait Time" System Property exceeds 750ms
  • Catalog Client Scripts with the console.log debugging method

Severity Level 'Low'

Issues ranked among the 'Low' level affect essential requirements for which there are measures to resolve at a low level. The severity issues contributes to the cloud indicator. 

Please find below the list of some of the issues raised with severity level 'Low':

  • Transform Maps with "Run business rules" option enabled
  • Business Rules with debugging statements in production
  • Business Rules using eval function
  • The "Log/trace level of TaskSLAController" System Property not set to "notice"
  • The "Go To search" System Property set to "contains" operator
  • Debugging properties enabled in production environments
  • Client Scripts with empty script field
  • The "Auto-complete Search" System Property set to "contains" operator
  • Script Includes with debugging statements in production
  • Catalog Client Scripts with empty script field
  • Javascript - Avoid use of alert function

Severity Level 'Warning'

There is an exception to take in account, when an issue is detected on an inactive configuration item, or in a commented block of code. In this case, the severity of the issue is reduced to a 'Warning' issue. This severity does not contribute to the calculation of the Quality of Cloud indicator, nor is it accounted for on the global count of issues associated with each scan. 

Please find below the list of some of the issues raised with severity level 'Warning':

  • Any issue of severity High, Medium or Low while detected on an inactive configuration item
  • Any issue of severity High, Medium or Low while detected in a commented out line of code

What's here


Related content

Rules and rulesets