Book Image

ServiceNow: Building Powerful Workflows

By : Tim Woodruff, Martin Wood, Ashish Rudra Srivastava
Book Image

ServiceNow: Building Powerful Workflows

By: Tim Woodruff, Martin Wood, Ashish Rudra Srivastava

Overview of this book

ServiceNow is a SaaS application that provides workflow form-based applications. It is an ideal platform for creating enterprise-level applications, giving requesters and fulfillers improved visibility and access to a process. ServiceNow-based applications often replace email by providing a better way to get work done. This course will show 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. You will then learn more about the power of tasks, events, and notifications. We’ll then focus on using web services and other mechanisms to integrate ServiceNow with other systems. Further on, you’ll learn how to secure applications and data, and understand how ServiceNow performs logging and error reporting. At the end of this course, you will acquire immediately applicable skills to rectify everyday problems encountered on the ServiceNow platform. The course provides you with highly practical content explaining ServiceNow from the following Packt books: 1. Learning ServiceNow 2. ServiceNow Cookbook 3. Mastering ServiceNow, Second Edition
Table of Contents (39 chapters)
Title Page
Credits
Preface
Free Chapter
1
Module 1
36
Bibliography

Data Policies


Data Policies, unlike UI Policies, execute on the server. They are closely linked to UI Policies in terms of behavior and functionality. They can even be "used as" UI Policies on the client, when implemented (however, with limited functionality). Strangely, Data Policies reside in the sys_data_policy2 table. That 2 is not a typo; it has been that way at least as far back as Eureka.

Data Policies allow you to prevent certain changes on the server, by rejecting database updates that don't fit the criteria laid out in the data policy. You can either prevent edits by making a field read only, or you can require a field value by making a field Mandatory, using a Data Policy rule.

While Data Policies can be used as UI Policies on the form, they do not have the exact same functionality as a UI Policy. You cannot, for example, make a field visible or hidden using data policies, because there is no server-side equivalent of a contextually hidden field. There is also no Advanced view,...