To rename a field label in ServiceNow (such as changing " Priority " to " PValue " ), you must eitherupdate the dictionary definitionorchange the field label.

Right-click on the " Priority " field labelin the form.

Select " Configure Dictionary " .

Update the " Label " fieldto " PValue " .

Save the changes.

The new label will now be reflected across the system where applicable.

Right-click on the " Priority " field labelin the form.

Select " Configure Label " .

Update thelabel textto " PValue " .

Save the changes.

This methodonly changes the field labelfor display purposeswithout affecting the underlying database structure.

B. Right-click on Priority and select Configure Display Settings

There isno " Configure Display Settings " option when right-clicking on a field label in ServiceNow.

D. Right-click on Priority and select Configure Column

" Configure Column " is used forlist views, not for changing field labels on forms.

ServiceNow Field Labels and Dictionary

ServiceNow CSA Training Module: " Configuring Forms and Fields "

Option 1: Configure Dictionary (Recommended for Full Customization)Option 2: Configure Label (Quick Change for Display Purposes)Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

ADisplay Business Ruleis aserver-side scriptin ServiceNow thatruns before the form is displayed to the user.

Populatesg_scratchpad(Shared Data Object)

g_scratchpadis atemporary objectthat storesserver-side dataand makes it available toclient-side scripts (e.g., Client Scripts, UI Policies).

Example: If you need topass user-specific information(e.g., " Manager Name " or " User Role " ) from the server to the client, you useg_scratchpad.

Runs Before the Form Loads

Executesbefore data is sent to the client, ensuring thatpreprocessed datais available.

Improves performanceby reducing unnecessary server calls.

Does Not Modify Records Directly

Unlike other Business Rules (Before,After,Async),Display rules do not modify the recordbeing loaded.

They only preparedata for the client-side.

Primary Purpose of a Display Business Rule:

Example of a Display Business Rule:// Runs before the form loads

(functionexecuteRule(current, gScratchpad) {

gScratchpad.manager_name= current.manager.getDisplayValue();

})(current, gScratchpad);

This scriptretrieves the manager’s namefrom the server andmakes it available on the client-sideusingg_scratchpad.manager_name.

AClient Scriptcan then useg_scratchpad.manager_nameto display the manager’s name in a fieldwithout making another server call.

A. To monitor fields on a form, and provide feedbackIncorrect– This describesClient Scripts and UI Policies, not Display Business Rules.

C. To set fields to mandatory, hidden, and read-onlyIncorrect– These actions arehandled by UI Policies or Client Scripts, not Display Business Rules.

D. To define what happens on a form when a particular field changesIncorrect– This is the function of anOnChange Client Script, not a Display Business Rule.

Incorrect Answer Choices Analysis:

ServiceNow Docs – Business Rules Overview???? Display Business Rules

ServiceNow Docs – g_scratchpad Usage???? Using g_scratchpad in Display Business Rules

Official ServiceNow Documentation References:

To ensure data consistency across the entire ServiceNow platform, developers use Data Policies .

1. The Scope of Data Policies:

Data Policies enforce requirements on data payload at the database engine level (server-side). Because they operate at this deep layer, they act as a universal gatekeeper. It does not matter if a user types the data into a browser UI Form, if the data is bulk-loaded via an Import Set, or if it is pushed in via a REST/SOAP Web Service API—the Data Policy will evaluate the data. If the data fails the policy (for example, a mandatory field is missing), the database will reject the insert or update.

2. Comparison to UI Policies:

This is the critical distinction developers must know. UI Policies only run on the client-side (in the browser). If you make a field mandatory with a UI policy, a user on the form cannot submit it. However, an external API could easily bypass that UI Policy and insert a blank record. A Data Policy prevents that bypass.

3. Why the other options are incorrect:

B, C, and D: " Write Policies, " " Data Integrity Policies, " and " Data Submission Policies " are not standard ServiceNow platform features or terminology.

In ServiceNow,wildcardsare used to filter lists effectively. To search for records whereShort Description contains " email " , use theasterisk (*) wildcard.

Click the List Magnifier (???? ) to enable column search.

In the " Short Description " column search box, type:

Steps to Filter a List for " email " in Short Description:CopyEdit

*email

Press Enterto apply the filter.

*email→ Finds any record where " email " appearsanywherein theShort Description.

email*→ Finds records where " email " is at thebeginningof theShort Description.

*email*→ Also works but is redundant, as*emailalready searches within the text.

A. Click List Magnifier, on Short Description, type “email”, click enter →Incorrect

Typing just " email " only searches for an exact match, not occurrenceswithinthe text.

C. Click List Magnifier, on Short Description, type email, click enter →Incorrect

Same issue as (A) – it doesnotuse a wildcard, so it only returns exact matches.

D. On Search box, select text, type email, click enter →Incorrect

Theglobal search barisnot column-specific, meaning it searches across multiple tables, not justShort Description.

Using List Filters and Wildcards

ServiceNow Search Wildcards

Why Wildcards Matter?Why Other Options Are Incorrect?Official ServiceNow Documentation Reference:

✔Update Setsare the primary method formoving customizationsfrom one ServiceNow instance to another. An Update Set records changes made to an instance, including modifications to:

Forms, fields, and tables

Business rules, scripts, and workflows

UI policies and ACLs

How Update Sets Work:

When youmodify configurations, the changes arecapturedin an active Update Set.

The Update Set is thenexported from the development instanceandimported into the target instance(e.g.,from Dev to Test to Production).

Once imported, the Update Set iscommitted, applying the changes.

Option A (Table Templates)is incorrect because these definedefault field structuresfor tables but do not move customizations.

Option B (Application Files)is incorrect because individual application files exist within Update Sets but do not serve as a transport mechanism.

Option C (UI Script Includes)is incorrect because script includes are reusable scripts, not a method for transferring configurations.

???? Reference:ServiceNow Administration – Update Sets & Instance Migration