Skip to tutorial content
Rate module 4.0/5 (1)

Demo Data & Dependencies

3 min read
On this page

In this lesson, you will learn:

  • What demo data is, and when to use it
  • Why demo data doesn’t belong in Prod
  • What dependencies are and how ServiceNow handles them

1 What is demo data?

When you install an app, ServiceNow may ask: “Load demo data?” Demo data is a set of sample records that come with the app, like example users, tickets, and articles.

Key term: Demo data

Fake sample records that show how an app works. Great for learning and testing, but not real.

Remember Beth Anglin and Abel Tuter? They’re demo users that came with your PDI. 🙂

Two ideas side by side. Demo data: yes in a PDI or a Dev instance, where sample users and tickets help you learn and test; no in Prod, where fake records would mix with real ones and are hard to remove. Dependencies: installing App A also installs Plugin B and Plugin C that it needs, and ServiceNow lists them before you confirm.
Figure 1. Demo data is for practice. Dependencies come along automatically.

2 Demo data: yes or no?

Instance Load demo data? Why
PDI ✅ Yes You learn faster with example records
Dev / Test 👍 Often Helps you test before real data arrives
Prod ❌ No Fake records would mix with real ones

⚠️ Heads up: Demo data is hard to remove. There’s no “undo” button. If it lands in Prod, someone has to find and delete those records by hand. So think before you tick the box!

💡 Good to know: Forgot to load demo data in your PDI? It’s often possible to load it later. Search ServiceNow’s docs and support articles for “load demo data” for your app.

3 What are dependencies?

Some apps need other plugins or apps to work. These are called dependencies.

Key term: Dependency

Another plugin or app that must be installed for this one to work.

Think of a video game. 🎮 To play the new expansion pack, you first need the main game. The main game is a dependency.

  1. You choose to install App A.
  2. ServiceNow checks what App A needs.
  3. It shows you a list: App A also needs Plugin B and Plugin C.
  4. When you confirm, it installs all of them together. ✅

⭐ Remember: Always read the dependency list before you confirm. You’re installing everything on it, not just the app you picked.

4 Let’s try it: check an app

  1. Open System Applications > All Available Applications > All.
  2. Pick an app you haven’t installed, and open it.
  3. Find its dependencies. How many are there?
  4. Click Install, but stop at the confirmation window. Look for the demo data option, then cancel if you don’t want to install it.

5 Quick recap

  • Demo data = sample records that show how an app works
  • Load it in PDIs and often in Dev, never in Prod
  • Demo data is hard to remove
  • Dependencies are other plugins an app needs
  • ServiceNow lists and installs dependencies with the app

6 Check yourself

Think of your answer first. Then tap to check.

1 Should you load demo data when installing an app in SNWR’s Prod instance? Show answer

No. Fake records would mix with real ones, and they’re hard to remove.

2 What is a dependency? Show answer

Another plugin or app that must be installed for this one to work.

3 You install App A and see Plugin B in the list too. What happens when you confirm? Show answer

Both App A and Plugin B are installed.

Nice work! You finished this lesson. 🎉

Was this lesson helpful?

Have a question or doubt?

Ask here and get help from instructors and fellow learners.

0 / 300

Only logged-in learners can post.