architectural structure

Wherefore Architecture?

If ServiceNow is built to support Citizen developers, why do we need ServiceNow architects? “Thinking about design is hard, but not thinking about it can be disastrous.” - Ralph Caplan Introduction For almost 14 years in the ServiceNow space, and across a rapid expansion of the exosystem, it has been interesting to observe and analyze various organization’s approaches to developing and maintaining their ServiceNow environment. Specifically, how do organizations manage the inflow of business needs, the distribution and velocity of development, configuration and administrative work, and the ongoing maintenance of the platform? As the footprint of ServiceNow has expanded conjunctionally…
core strength

Building Core Strength

Why good core data is both the roots and the flowers of your ServiceNow tree "A tree with a rotten core cannot stand." — Aleksandr Solzhenitsyn In the fitness world, and in fact the physical human world, your core is the central part of your body. It includes the pelvis, lower back, hips and stomach. Exercises that build core strength lead to better balance and steadiness, also called stability. Stability is important whether you're on the playing field or doing regular activities. In fact, most sports and other physical activities depend on stable core muscles. As ServiceNow has moved further…
architecture

Building The Perfect Architect – Part 2

What makes a good ServiceNow architect? And what makes “architect” a misnomer? In part one, we discussed what an architect is within the ServiceNow and the larger IT ecosystems. Now, we’ll delve into design documentation - a key part of an architect’s deliverables, and some of the behaviors of folks who may have the title architect but whose actions belie the title. Documenting designs and implementations A good architect understands the value of documentation, and both creates and enforces documentation. My rules of thumb for documentation are: Any custom development that includes creating new tables needs design documentation. This does…
architecture

Building the Perfect Architect – Part 1

What makes a good ServiceNow architect? And what makes “architect” a misnomer? “Architecture is not an inspirational business, it's a rational procedure to do sensible and hopefully beautiful things; that's all.” - Harry Seidler If you’re here and reading this, you probably have a concept of what a ServiceNow architect is. (In this context, “architect” means a ServiceNow technical architect.) And you’ve likely worked with folks who have the title “architect”, whether on implementation projects or as part of a larger IT ecosystem. But what does this mean, and what should it mean? I’ll spend the rest of this article…
New Release

Starting Your “EPA” (Environment Proficiency Activities)

Tips for Optimizing your ServiceNow Instance Management Having been in the ServiceNow business for over 12 years, you begin to take certain things for granted. At least until you see someone doing something that you don’t expect and it makes you say, “hmm, maybe this isn’t common knowledge”. One such area where I’ve noticed this in recent years is the management of an overall ServiceNow environment - that which encompasses all your ServiceNow instances, and the processes and techniques by which configuration, code and data is built, moved and shared between them. In my experience, if done properly, this should…
Where, When and Why

The Three Ws of Development

Where, When and Why you should do your development In journalism, there’s the concept of the Five W questions whose answers are fundamental to getting the information needed: Who What When Where Why I want to talk about what I call the “Three Ws of Development” in the ServiceNow realm. These three are: When, Where and Why. We’re going to skip the questions “Who” and “What”. Why? Because “who” is a question for hiring managers, recruiting, and resource vetting. And “what” is (too often) the focus of most if not all training and documentation. Do you need to get the…
To Scope or Not to Scope

To Scope or Not to Scope

ServiceNow introduced the concept of Scoped Applications in the Fuji release. From their documentation: Application scoping protects applications by identifying and restricting access to application files and data. By default, all custom applications have a private scope that uniquely identifies them and their associated artifacts with a namespace identifier. The application scope prevents naming conflicts and allows the contextual development environment to determine what changes, if any, are permitted. Source: Application scope Each ServiceNow application has an application scope that determines which of its resources are available to other parts of the system. Application scoping ensures that one application does…