Book Image

Learning ServiceNow - Second Edition

By : Tim Woodruff
5 (1)
Book Image

Learning ServiceNow - Second Edition

5 (1)
By: Tim Woodruff

Overview of this book

This book is an updated version of Learning ServiceNow, that will cover the new and updated features of the ServiceNow platform. It will show you how to put important ServiceNow features to work in the real world, while introducing key concepts via examples of managing and automating IT services. It'll help you build a solid foundation of knowledge, and will demonstrate how to effectively implement and configure modules within ServiceNow. We'll show you how to configure and administer your instance, and then move on to building strong user interfaces and creating powerful workflows. We also cover other key elements of ServiceNow, such as notifications, security, reporting, and custom development. You will learn how to improve and automate your business' workflow and processes. By the end of this book, you will be able to successfully configure and manage ServiceNow like a pro.
Table of Contents (19 chapters)
Learning ServiceNow Second Edition
Contributors
Preface
Index

URLs in the service portal


Many widgets dynamically pull information from the portal URL. There is a generalized standard for URI parameter names, though you can change some of them depending on your needs. However, you cannot change the parameters that OOB (Out of the box / system default) widgets use without creating custom variations of those widgets.

The most common parameters used in service portal URIs are:

  • id: The ID of the portal page

  • table: The table related to what's being displayed. For example, the form page accepts a sys_id and table, which translates to a specific record.

  • sys_id: The sys_id of a specific record.

  • view: Which view (such as a form view) to display

Example: https://<instance>.service-now.com/sp? id =form& table =incident& sys_id =<sys_id>& view =sp

This link points to the portal with the URL suffix sp. Within that service portal it points to the form page, and loads a record on the incident table with the specified sys_id, and the service...