Catalog Client Scripts Rules

< 1 min read

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

See the for designing and implementing client scripts.

Description	Severity	Area of impact
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 – Nationality	Warning	Security
Possible PII usage in configuration element – Address	Warning	Security
Possible PII usage in configuration element – Email	Warning	Security
Possible PII usage in configuration element – Passport	Warning	Security
JavaScript – Avoid use of Function Constructors	High	Security
JavaScript – Avoid use of WebDB	High	Security
JavaScript – Avoid use of debugger statements	High	Security
JavaScript – Avoid unrestricted targetOrigin on cross-domain messaging	High	Security
JavaScript – Avoid making connections on unsafe protocols	Warning	Security
JavaScript – Avoid use of Eval function	High	Security
Javascript – Avoid use of alert function	Low	Scalability
Javascript – Avoid use of local storage on Client Scripts	High	Security
JavaScript – Optimize Loops	Warning	Performance
JavaScript – Use === comparison	Warning	Manageability
Catalog Client Scripts with hard-coded sys_ids	Medium	Manageability
Document Object Model (DOM) manipulation in Catalog Client Scripts	High	Manageability
Synchronous AJAX call in Catalog Client Scripts	High	Performance
Catalog Client Scripts should not use unsupported scripting APIs	High	Manageability
Catalog Client Scripts with the console.log debugging method	Medium	Performance
GlideRecord usage on Catalog Client Scripts	High	Performance
Catalog Client Scripts with empty script field	Low	Performance
Catalog Client Scripts without function	Medium	Scalability
Modified Out of the Box Element	Warning	Scalability

Updated on March 21, 2025

Was it helpful ?