Examples or Use cases of Different Scripts in Servicenow:

Access Control: Any further restrictions or any additional access for a particular
Application or a module. It can also be given for a particular field.
Business Rule: A server side script that runs when records are displayed, inserted,
deleted, queried or updated.
Business Rules run on an incident or any other form before or after the form is filled.
A field can be made bold or flashing with the business rules help.
Import Sets: Any raw data which is either in the form of CSV or EXCEL sheets in
columns representation can be imported into Servicenow. Users, Roles or details of
any organization can be imported.
AJAX Scripts:
1. Login forms With Ajax a user can directly type their log in and password on
the original page.
2. Auto Complete forms.
3. Updating with user contents.
4. Helps form submissions and validations.
Script Includes: Servicenow has a class system like JAVA or Dotnet that is called as
script includes.
UI Actions:
1. Any buttons, links, context menu items on any list choices can be placed on
form or an application menu.
2. Submit/ Update/Delete buttons on a form.
3. On the header of the application menu New or go to
4. Can be buttons at the bottom of list which selects a record.
5. Buttons which can do bulk actions such as deleting many records or
approving records in bulk.
UI Policies: Fields can be set to mandatory, visible or read only by UI policies.
1. When a field is set to mandatory, unless it is filled the form doesnt get
submitted.
2. Visible field lets the fields to be vanished from the form if it is set to false.
3. Read only is customized so that the form doesnt allow to write anything in
that field.
Client Scripts:
1. Colored buttons are created with the client scripts so that they are easier to
notice.
2. On change client script can create alert on the screen.
3. Enables removing options from choice list.
UI Macros: These are only available for reference fields.
1. Icons which appear next to input elements for a field.

2. Shows related incident macros next to caller field on an incident form, shows
CI map next to configuration item field.
3. With the help of Onload script (client Script), a lock icon next to category field
can be created. This can either/hide the subcategory field on a form.
Validation Scripts: Verifies any data issues before submitting a form.
1. Verify the impact field value with the priority field value. Low impact is not
allowed with high priority.
2. Date/Time format must match the instances date/time format else an error
message is shown by the validation script.
3. If any user is not created already but used on the incident form, a red dashed
line is shown below the name of the user by the validation script.
Impact: The effect that an incident has on business.
Priority: How quickly the incident should be address.
UI Pages: Any pages, forms (incidents), lists (when incidents are opened lists
appear) these are the ways of displaying UI pages in servicenow. Scripts which run
on server are HTML, XML, JAVASCRIPT, Jelly etc. Webpages being displayed or
servicenow welcome page can be taken as examples.
Catalog UI policies: Defines the display of variable set or a catalog item.
1. Displaying a mandatory field of all items to be moved when a user schedules
a move from one location of office to another. Variable Sets are used to ask
questions or give choices of which catalog items to be moved.
2. A catalog condition is set to mandatory for any IT technician role to add
mobile phone number when ordering a business card.
Workflows:
1. Along with a catalog item a workflow item is created.
2. It tells the users when the task is due.
3. Can be used for knowledge approvals, any change request.
UI Scripts:
1.
2.
3.
4.

Different background color in the title bar using CSS.

Change a link location or remove it completely in the UI.
Change feedback link so it is points to an internal forum or help desk.
Removing or hiding charts from a page.

UI properties:
Default values for color and font attributes of text can be defined.