Skip to content
Tutorials Center
My learning

Topics

Lesson 2 of 39 ยท Getting Started

Your Personal Developer Instance

Get a free ServiceNow Personal Developer Instance, sign in as admin, understand hibernation and releases, and set up a safe practice routine for this course.

To learn ServiceNow you need an instance you are allowed to break. ServiceNow offers a free Personal Developer Instance (PDI) to anyone who signs up on the Developer Program site. It is a full, small instance with the platform, sample data and the ITSM applications, intended for learning and building, not for production.

The steps below describe the usual flow. The vendor's pages and wording change over time, so if a screen differs, follow what the site shows; the ideas stay the same.

Requesting an instance

  1. Create a free account on the ServiceNow Developer site (developer.servicenow.com).
  2. Sign in and choose to request an instance. You pick a release family (the newest is usual; pick an older one only if your job uses it).
  3. Wait a few minutes while the instance is built.
  4. Open the Manage instance password option once to see the generated admin password. Copy it into a password manager.
  5. Use the instance URL, which looks like https://dev12345.service-now.com, with user name admin.

The password shown for a PDI belongs to your throwaway instance. Do not reuse a password from any real account, and never share the instance with other people's data in it.

Hibernation and reclaiming

PDIs are free, so they are not kept running forever:

  • After a period without use the instance hibernates. Visiting the developer site wakes it, which takes a few minutes.
  • An instance that stays unused for long enough may be reclaimed: its data is lost and you request a new one.
  • You can release (delete) the instance yourself and request a fresh one, which is the quickest way to reset a messy practice environment.

Because of this, keep anything valuable (scripts, update sets, notes) outside the instance too, for example in a Git repository or exported XML files. Later chapters show update sets and source control for that.

What is in a fresh instance?

A new PDI already has:

  • The admin user plus demo users (for example, names like Abel Tuter or Fred Luddy) so you can test roles and assignments.
  • The ITSM applications: Incident, Problem, Change, Service Catalog, Knowledge.
  • Dozens of sample records, so lists are not empty.
  • The Studio and App Engine Studio tools for building applications.

Plugin and application availability depends on the release and on what the Developer Program enables. Some paid products are missing or limited on a PDI. When this course mentions such a product, it says so.

First sign-in checklist

After signing in as admin:

  1. Note the banner area: the instance name, your user menu and the global search box.
  2. Open the user menu in the header and choose Elevate role if offered; security_admin is needed for some changes to access rules (covered in the next chapters).
  3. Use the All menu and type incident in the filter to find the Incident application.
  4. Open System Properties > System and look at the instance name and version details, or use System Diagnostics pages to see the build.
  5. Create a second user to test as, then use Impersonate user (under the user menu) to see what an ordinary user sees. Impersonation only changes your view; stop when done.
Python A tidy habit: a practice-log checker (stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Naming your work

Good habits begin on day one, because the same habits matter in a company instance:

  • Name an update set after the task, for example PRACTICE_Lesson 12 UI policies.
  • Prefix custom tables with u_ (global) or use a scoped application, and give custom fields clear labels.
  • Keep a notebook of URLs you use often, like incident.list and sys_user.list.
  • When you break something, note what you did; it is the best way to learn how to fix it.
Python Instance URL anatomy (stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Check your understanding

Quick check ยท 3 questions

of 3 answered You scored / 3 ยท perfect!

  1. 1. What is a Personal Developer Instance for?

    A PDI is a free personal instance for learning and building; it is not meant for production.
  2. 2. What happens to a PDI that nobody uses for a long time?

    Free instances hibernate when idle, and an instance left unused for long enough can be reclaimed.
  3. 3. Why keep copies of important work outside the instance?

    Update sets, exported XML and Git give you a way to restore work after a reset.

Summary

  • A free PDI from the Developer Program is your practice environment.
  • Sign in as admin with the generated password; store it safely.
  • PDIs hibernate when idle and can be reclaimed, so keep backups of your work.
  • Use demo users and impersonation to test roles.
  • Build good habits: named update sets, clear names, a notebook.

Next: The Now Platform Architecture