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

Scoping out limits


Running multiple applications on the ServiceNow platform brings benefits of scale. You may have IT using it to organize production issues, HR may perform case management, while the maintenance team use it to track leaky taps-each using separate, specialist applications that are built for their use. Since you are using a single platform, it makes it possible to share some data.

The Users table is a great example of this. While each department will want to control the privileges that each person has (someone from the facilities team probably shouldn't have access to all the payroll data), sharing the core data means there is one place to go and update. If you change your name, isn't it nice to do it on one system, without relying on complex integrations to simulate a cohesive system?

The diagram below represents how many applications all need to reply upon shared resources, like the user table.

Also, you often want applications to talk to each other. Consider that a new employee...