Hi Team,
Does anyone know how to fix the solarwinds-ServiceNow integration for alerting to populate correct option in the Impact field for the incident?
Check the raw payload that SolarWinds sends over to ServiceNow to make sure its sending the right code over. It could be mapping on the ServiceNow side also.
The Impact (not urgency) field options are configured in the Servicenow ticket trigger action in Solarwinds? This should be pulled from Servicenow by Solarwinds.