Business Rules rules

The below table shows the list of ServiceNow business rules rules that are checked by Quality Clouds.

See the Business rules best practices for designing and implementing business rules.

Description	Severity	Area of impact
Business Rules defined on the Global table	High	Scalability
Business Rules without function	High	Scalability
Business Rules using GlideRecord and getRowCount	Medium	Scalability
Modified Out of the Box Element	Warning	Scalability
Business Rules with debugging statement	Low	Scalability
Potential recursive Business Rules	High	Performance
onBefore Business Rules should not update records on other tables	High	Performance
Synchronous Business Rules making SOAP or REST calls	High	Performance
Business Rules using the SOAP getResponse method	High	Performance
JavaScript - Optimize Loops	Warning	Performance
Business Rules using eval function	High	Security
JavaScript - Avoid use of debugger statements	High	Security
JavaScript - Avoid use of Function Constructors	High	Security
JavaScript - Avoid unrestricted targetOrigin on cross-domain messaging	High	Security
JavaScript - Avoid use of WebDB	High	Security
Possible extra-sensitive PII usage in configuration element - Gender	High	Security
Possible extra-sensitive PII usage in configuration element - Religion	High	Security
Possible use of private data	Warning	Security
Possible PII usage in configuration element - Email	Warning	Security
Possible PII usage in configuration element - Address	Warning	Security
Possible PII usage in configuration element - Nationality	Warning	Security
Possible PII usage in configuration element - Passport	Warning	Security
JavaScript - Avoid making connections on unsafe protocols	Warning	Security
Scripts should not use gs.sql	High	Manageability
Business Rules with hard-coded sys_ids	Medium	Manageability
JavaScript - Use === comparison	Warning	Manageability
Unlogged API call error condition	Medium	Manageability
The demo_data_running_trigger business rule should be disabled	High	Manageability