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

Approving tasks


An important step in many applications is obtaining the approval to proceed. This may be due to a financial outlay, risk to the business, or simply getting the validation that you are doing the right thing.

There are several ways to get approval in ServiceNow. Workflow is the most powerful. For very simple scenarios, however, Approval Rules may be sufficient (available under System Policy > Rules > Approval). These allow you to hardcode a specific user or group or use a script to determine who will be asked to make a decision if the condition matches.

When an Approval record is generated, it is always associated with a single person. That person has two choices: to approve or reject. The decision of that person is taken into account when deciding what should happen next.

Note

It is common to want to customize the Approval activity to add options than such as Need more information or Defer decision. This may stem from the language of Reject, which is often taken to mean...