Loading...
Loading...
The "sn_priority_group" value is not set and is causing the Incident Impact to set as Null. Steps to Reproduce 1. Disable the "Alert Priority Queue" scheduled script execution (both instances, if there are two - there's a separate defect on this topic). 2. Create an alert of "Critical" severity 3. Note that the sn_priority_group of the alert remains null (because of step 1) 4. Run the "Create Incident" subflow for this alert 5. Open the execution details for the subflow, and look at the output data for step "Calculate Values (Based on the Alert)" Expected: incidentImpact should be 3 (or 1 or 2, depending on alert severity in step 2). Actual: incidentImpact is null
This problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this article to be notified when more information becomes available.
PRB1532588
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.