Book Image

Mastering ServiceNow - Second Edition

Book Image

Mastering ServiceNow - Second Edition

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. The book steps through the main aspects of the ServiceNow platform, from the ground up. It starts by exploring the core architecture of ServiceNow, including building the right data structure. To add business logic and control data, and interactivity to user interaction, you will be shown how to code on both server and the client. You will then learn more about the power of tasks, events and notifications. The book will then focus on using web services and other mechanisms to integrate ServiceNow with other systems. Furthermore, you will learn how to secure applications and data, and understand how ServiceNow performs logging and error reporting. You will then be shown how to package your applications and changes, so they can be installed elsewhere and ways to maintain them easily. If you wish to create an alternative simple interface, then explore ways to make ServiceNow beautiful using Service Portal. By the end of the book, you will know the fundamentals of the ServiceNow platform, helping you be a better ServiceNow System Administrator or developer.
Table of Contents (18 chapters)
Mastering ServiceNow Second Edition
Credits
Notice
About the Author
About the Reviewer
www.PacktPub.com
Preface

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...