Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Example: Watching the incident priority

Log in to subscribe to topics and get notified when content changes.

Example: Watching the incident priority

The following example shows what happens to the Priority field on the incident form when both the Impact and Urgency fields change.

The Incident form has two client-side data lookups change the priority. Additionally, server-side ACLs and the data lookup engine fire when the record is saved. Finally, a client-side UI policy sets the Priority field back to read-only, which is the default setting.
Table 1. Watching the incident priority
Original values
  • Priority:1 - Critical
  • Impact:1 - High
  • Urgency:1 - High
First Change
  1. The user changes the Impact value to 3 - Low.
  2. The priority automatically changes to 3 - Moderate based on the Priority Lookup data lookup definition used by default in ServiceNow incidents.
Note: At this point, the record has not been saved.
Second Change
  1. The user changes the Urgency value to 2 - Medium.
  2. The priority automatically changes to 4 - Low based on the same Priority Lookup data lookup definition.
  3. The user saves the record by right-clicking the form header and choosing Save.
Figure 1. Field watcher example
Note: The values that change from 1 to 3, and then from 3 to 4, refer to the numerical values in the choice list.


The following video demonstrates how to perform field-level debugging with the field watcher.