Exception reason integration

concept brazil Updated Oct 27, 2026 1 min read exception-reason-integration.md
Raw file servicenow.com

You can synchronize exception reasons from non-production to Production instances after a record is created or updated.

When a developer creates or updates an exception reason on a non-production instance, the integration automatically propagates that change to the production instance. If production approvals are enabled, the exception reason enters a Requested state and triggers an approval workflow before taking effect.

Where to configure

  • On each non-production instance where you want exceptions approved in production, select Enable approvals in production.
  • On production, specify the approval group in the Approval group(s) field on the Exception Reason tab of Scan Engine Properties, in the Exception Behaviour section. That group is notified when a new exception is raised.

Approval workflow

When Enable approvals in production is selected in Scan Engine Properties, the following workflow applies:

  1. A developer creates or updates an exception reason on the non-production instance.
  2. The exception reason is synced to production in a Requested state.
  3. An approval request is sent to the configured approval group(s).
  4. After the request is approved or rejected, the status syncs back to the instance where the exception was raised.

Prerequisites

Parent Topic:Scan Engine integrations

Search documentation
Search document titles and file paths on the brazil branch