UI and Data Policies | Learning ServiceNow

Sign In Start Free Trial

Book Overview & Buying
Table Of Contents
Feedback & Rating

Learning ServiceNow

By : Hauser

4.9 (19)

Learning ServiceNow

4.9 (19)

By: Hauser

Overview of this book

This book shows you how to put important ServiceNow features to work in the real world. We will introduce key concepts and examples on managing and automating IT services, and help you build a solid foundation towards this new approach. We’ll demonstrate how to effectively implement various system configurations within ServiceNow. We’ll show you how to configure and administer your instance, and then move on to building strong user interfaces and creating powerful workflows. We also cover other key elements of ServiceNow, such as alerts and notifications, security, reporting, and custom development. You will learn how to improve your business’ workflow, processes, and operational efficiency. By the end of this book, you will be able to successfully configure and manage ServiceNow within your organization.

Free Chapter

The Interface

The Interface

Frames

Filter text box

Favorites

Important application menus and modules

Content frame

UI settings and personalization

Summary

Lists and Forms

Lists and Forms

List v2 versus List v3

Lists and Tables

Forms

Summary

UI Customization

UI Customization

UI15 versus UI16

Branding your instance

Custom themes

UI-Impacting system properties

Configuring service portal UI

Creating a custom homepage

Styling pages and widgets

Styling the CMS

Summary

Understanding Data and Relationships

Understanding Data and Relationships

One-to-many relationships in ServiceNow

Many-to-many relationships in ServiceNow

Enforcing one-to-one relationships

Defining custom relationships

Database table inheritance

Summary

Tasks and Workflows

Tasks and Workflows

Important task fields

Journals and the Activity formatter

Extending the task table

Workflows

Approvals

Assignment

Creating Task fields

Summary

UI and Data Policies

UI and Data Policies

UI Policies

Reverse if False

Scripting in UI Policies

UI Policy Order

Data Policies

Converting between Data and UI Policies

Data Policies versus ACLs

Summary

User Administration and Security

User Administration and Security

Groups and Roles

Emails and notifications

User preferences

ACLs - security rules

Summary

Introduction to Scripting

Introduction to Scripting

To script, or not to script?

Client side versus server side APIs

Where scripting is supported

Integrated development environment

Summary

The Server-side Glide API

The Server-side Glide API

The structure of an API class

Server-side APIs

GlideRecord

GlideElement

GlideDateTime

GlideSession

GlideSystem

GlideUser

Client-side APIs

GlideAjax

GlideForm (g_form)

Summary

The Client-side Glide API

The Client-side Glide API

Client-side APIs

GlideAjax

GlideForm (g_form)

GlideUser (g_user)

GlideRecord

Summary

Server-side Scripting

Server-side Scripting

Dot-walking and GlideElement

Script Includes

Business rules

Summary

Client-side Scripting

Client-side Scripting

Client Scripts

Security

Compatibility

Build for performance

UI scripts

Scripts files from the server

Summary

Debugging

Debugging

Logging

Client-side debugging

Server-side debugging

JavaScript debugger (Istanbul)

General Debugging

Summary

Pro Tips

Pro Tips

Admin Pro Tips

Scripting Pro Tips

What the pros wish they knew

Summary

Customer Reviews

4.9 (19)

5 star

89.5%

4 star

10.5%

3 star

0

2 star

0

1 star

0

UI Policies

UI Policies are a user-friendly way to control whether fields on a form are mandatory, read-only, or even whether they're visible. The UI Policy record itself, which resides in the UI Policy [sys_ui_policy] table, consists of a set of conditions, a short description, a relationship to another record or set of records, and a few other odds and ends. It does not however, contain information on the action to be performed:

UI Policy Actions are stored separately, in the UI Policy Action [sys_ui_policy_action] table. They are related to the UI Policy via a reference field, which - as we discussed in a previous chapter - means that they can (and by default, do) show up in a related list at the bottom of the UI Policy form:

These UI Policy Actions consist of a reference to the field to which the action applies, and drop-downs indicating whether the field should be Visible, Mandatory, or Read - Only . Each field has three options: True, False, and Leave Alone. As you might imagine...

Search

Your notes and bookmarks