The below table shows the list of ServiceNow inbound email action rules that are checked by Quality Clouds.
| Description | Severity | Area of impact |
|---|---|---|
| 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 – Optimize Loops | Warning | Performance |
| JavaScript – Use === comparison | Warning | Manageability |
| Inbound Email Actions with hard-coded sys_ids | Medium | Manageability |
| Inbound Email Actions using GlideRecord and getRowCount | Medium | Scalability |
| Modified Out of the Box Element | Warning | Scalability |
