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

Enforcing one-to-one relationships


 

On the topic of few things being impossible in ServiceNow, let's discuss one-to-one relationships.

 

Strictly speaking, a one-to-one relationship doesn't truly exist in ServiceNow. In database parlance, this would require that the right-hand table records have a primary key which matches the primary key of a record in the left table. Thus, you could have a left-hand record without a right-hand one, but could never have a right-hand record without the left-hand one.

 

That's interesting, but ServiceNow's Sys IDs are unique amongst all tables - and they have to be, because of the way ServiceNow's databases are structured on the back-end. Technically, ServiceNow has a flat database structure. In a sense, all records in the entire database are in one monster-sized table. This means that the primary key (Sys ID) for a given record really must be globally unique.

 

Okay, so we can't have one-to-one relationships in the usual way you might have them in an ordinary...