I've worked with the ServiceNow system for about 3 years now.  ServiceNow is a combination of a SaaS and IaaS sytem that provides out-of-box functionality for ITIL and general service management functionality.

I've worked on development frameworks in older systems of the past.  The Glide framework underneath the ServiceNow platform is truly revolutionary for bringing software development into the 21st century.  It is well thought out where the developer can concentrate mostly on process rather than re-invent rudimentary code to support application aspects such as navigation and UI form presentation.  This is all supplied as part of the core framework.  The customer/developer facing elements are stored as configuration elements, including data definition.  The customer/developer has no direct access to the backend database.  All data definition is stored as meta data using the same semantics into the database as any application developed on top of the platform itself.

Database records are displayed in one of two formats:  "list view" where a number of records are viewed in a column/row format and "UI view" where fields on a single record is displayed and possibly a list of related records displayed in the parent record's view.

Other backend features include a job scheduler, mail server, event handler, integrations using SOAP, REST, incoming email parser, and "runbook".  


In a nutshell, the Service Catalog is a framework that was originally built to simplify creating and presenting products (whether a service or a physical product) from a catalog and attach an execution workflow behind the individual product.  The framework mimics the e-commerce "shopping cart" experience such as Amazon.  At a company that I used to work for, I was thrown into the aftermath of the initial installation projects that included the Service Catalog to organize and clean up the hurried installation as well as standardize and manage the growth over the ServiceNow service management solution.  I saw first hand how not to implement the Service Catalog.  So when should you leverage the Service Catalog or roll your own by extending the Task table?

Subflows are separate workflow activities defined to be executed out of a primary workflow. ServiceNow's documentation gives the basics on how to create the subflow, but lacks on how to link a subflow to a primary workflow and pass data and return codes back and forth.  This article attempts to fill in the gaps you can't get from SN documentation.

One would think that the date/time data type would be cut and dry in terms of computing.  After all, programming around date/time has been a feature since the early days of digital computer systems. ServiceNow has to provide backend utilities to perform this translation since the developer cannot reach into the web server backend.  Though SN has a collection of date/time utilities, they are scant on formatting and calculation options.  You have to roll your own to compensate using the Glide library functions that SN makes available to the developer for translating a system or database stored time into a constant, generic format.  This article provides an example for how to create your own date/time utility utilizing the Glide library date/time functions.

This article is a reference that lists articles by other people that I have found who provide innovative solutions developing over ServiceNow.

Friday 6th of December 2019 -  Copyright 2016 Allan Wolfe