GRC Metrics - How to enable threshold evaluation for ad-hoc metric data tasks

[Yong Zeng Lee]

Hi Community,

I’m currently working on GRC Metrics in ServiceNow and came across a limitation regarding threshold evaluation.

Based on the official ServiceNow documentation:

• Threshold evaluation is supported for metric data tasks that are generated on a recurring basis from a metric definition.

• The docs also mention that threshold evaluation is not applicable for ad-hoc metric data tasks.

My question:
👉Is there any supported way to enable threshold evaluation for ad-hoc metric data tasks, or is the limitation absolute?

• Has anyone tried a workaround (e.g., custom scripts, scheduled jobs) to make threshold evaluation apply to ad-hoc metric data?

• Or is it a best practice to only rely on standard metric data tasks if threshold evaluation is required? 

Example use case:
In some business scenarios, there’s a need to evaluate thresholds for one-off / ad-hoc metrics rather than recurring ones.

For example:

• An organization undergoes a regulatory audit or penetration test where a large batch of vulnerabilities is identified in a single snapshot.

• A GRC team may want to record this data as an ad-hoc metric (e.g., “Number of high-severity vulnerabilities identified during audit X”).

• Even though it’s a one-off measurement, management may want to immediately evaluate it against a threshold (e.g., if more than 10 critical vulnerabilities are found, the metric should automatically be marked as Breached).

I’d appreciate guidance from anyone who has implemented this in a real-world scenario.

Thanks in advance!