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

Using Scoped Administration


The System Administrator is generally responsible for a ServiceNow instance. With the addition of the security_admin role, an admin user can change security settings, alter logic in Business Rules and see all data elements. Because all admins have all roles, adding a security rule that says that only users who have the x_hotel.team_leader won't restrict an admin.

Note

You may try to script an access control rule to stop admins from carrying out certain functions, or perhaps using the nobody role to disallow everyone. But just as an admin can create these rules, they can delete or change them!

Sometimes however, this is not desirable. Scoped Administration changes this premise by stopping admin users from inheriting a particular role, and disabling their access to edit the scope. Only those users who have been specifically allowed to work with a particular application can get access (either administratively, via Delegated Development, or as a fullfiler or requester...