Have you ever wondered if UI Pages in ServiceNow are captured in Update Sets? It’s a common question and, honestly, a fun one to answer. Let’s break it down step by step with short explanations that are easy to follow. Buckle up—you’re about to learn something cool!
What Are Update Sets in ServiceNow?
First things first. Update Sets are like suitcases in ServiceNow. You use them to pack changes you’ve made (like scripts, business rules, or workflows) and move those changes between environments, such as from development to production. They’re extremely useful!
But here’s the catch—not everything can fit into these suitcases. Some things, like certain data records, stay behind. That brings us to the question of the day: what about UI Pages? Do they make the cut?
What Are UI Pages?
UI Pages are custom web pages you can create in ServiceNow. They let you design nice-looking interfaces for users. You can build dashboards, form-like interfaces, or even something fancy like a customer-facing portal. Think of them as customizable canvases where you can use HTML, CSS, and ServiceNow’s Glide Scripting to create magic.
If you’re building these pages, you might wonder how to move them to another environment. Can you just toss them into your Update Set? Let’s dive into that.
Are They Captured in Update Sets?
The short answer is: yes, but there are some gotchas you need to know about. UI Pages are configuration records in ServiceNow, and configuration records typically go into Update Sets. So, when you make changes to a UI Page, those changes are captured automatically. Pretty simple, right?
But don’t celebrate just yet! Here’s where it gets interesting. The UI Macros tied to your UI Pages—or if your page references script includes—might not be included in the same Update Set. This can break your functionality if they don’t come along for the ride.

Tips to Avoid Surprises
Want to make sure your UI Pages move smoothly between instances? Here are some tips:
- Check dependencies: If your page uses UI Macros or Script Includes, make sure you’ve added those to your Update Set too.
- Verify before deploying: Always test in a sub-production environment before sending it to the big leagues of production.
- Use Scoped Applications: If you’re using a custom application, packaging everything into a Scoped App can simplify migrating custom work like UI Pages.
These tips can save you a lot of headaches in the future. Trust me!
When Are UI Pages NOT Captured?
This part is rare but worth mentioning. Sometimes, depending on specific configurations, UI Pages might not be added to your Update Set automatically. This can happen if someone accidentally marked your Update Set as “completed” or if there’s an issue with how your instance is tracking changes.
If your UI Page doesn’t seem to show up in the Update Set, don’t panic. You can manually add it by finding it in the application navigator, opening it, and clicking the magical “Add to Update Set” button. Problem solved!
You can also use the System Diagnostics tool to troubleshoot if something seems off.
Think Like a Detective
Here’s a fun way to think about this. Imagine you’re a detective. Your job is to ensure nothing important gets left behind when you move your Update Set. Ask yourself:
- Did I check for all the dependencies?
- Are all my related components packed?
- Have I tested my changes in the new environment?

When you think like this, you’ll catch issues before they turn into big problems.
The Final Word
Yes, UI Pages are captured in Update Sets, but you have to be careful. Always make sure everything your page relies on is captured too. Dependencies are key! Follow the tips here, and you’ll be moving UI Pages between environments like a pro.
Remember: ServiceNow is customizable and flexible, but it requires a little attention to detail. Keep an eye on those dependencies, test your Update Sets, and don’t be afraid to ask questions if something doesn’t work as expected.

Now go forth and conquer ServiceNow, one UI Page at a time!