ServiceNow recently released the Zurich version, and among others, there is one significant game changer for UI Builder – a Component Builder. We can now create reusable components directly in UI Builder, without leaving the environment and without coding. Let’s take a look.

Today, let’s learn how to connect Modals and parent Pages in UI Builder using Dispatched and Handled events, including a tested workaround for a Page Collection bug. This guide walks you through event setup, payload handling, and fixing broken connections so your events fire reliably even across complex UIB structures.

Let’s continue with second part. It will be short, but important. Input properties 👇

Handling Modals in Configurable Workspaces could look straightforward for Single Page Apps, but not evetrything is so clear when handling advanced scenarios especially in read-only situations like in Service Operation Workspace.

Let’s explore all the options, nicely step by step.

When you need to gather some data from the backend, you can either use in-built Data Resources (preferred) or you can create your own.

Let’s take a look at creating a Transform Data Resource. You’ll probably use it the most because, first, it’s basically a server script, and second, the documentation for the others is poor, so you end up in Transform anyway.

From now on, you can see and check the source code of the extension on GitHub here. It will take a couple of days to fully sync the version in the Chrome Web Store (1.0.5 live, 1.0.6 waiting for approval) and GitHub (1.0.6), but afterward, feel free to compare the checksums. 🚀

I believe this will enable the use of the extension even where the security limits for extensions are stricter.

But I think such an audit should be possible for all the extensions, tbh. No one ever knows what developers hide in their apps 🤡

Until the code gets opened. 💪

Enjoy!

Jan

I have already met multiple times a requirement to open an attachment in a separate tab so it can be easily printed (by default, the attachment is downloaded / opened in an overlay).

Well, here’s how 👇

I found myself struggling to navigate effectively across the most-used locations in ServiceNow during my workday; slash commands of SN Utils are not always a solution for me, and favorites in the backend are not always accessible with a few clicks.

So I decided to solve this in the extension.

While scripting in UIB, you don’t always have to repeat yourself (and we know that in Data Binding, we sometimes have to repeat ourselves..).

But for Client Scripts, you can write your utilities once and then reuse them across as you like.

Lets see how.

Action Bar is where the workspace buttons sit and where agents interact with the record. Whether UI Actions or Declarative Actions, it’s still the Action Bar that holds them.

One of the bad UX (from my point of view) is that those buttons are available even when the record is not valid (mandatory fields not filled in).

I think buttons should disappear in such situation and I think it should be OOB behavior.

This post is about how to accomplish it via customization 🧑‍💻