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 🧑‍💻

New version was just released; check it out in the Chrome Web Store 😎

OK, it was faster than I expected; I had no experience with the Google Web Store and with the approval process there, so I submitted a sample version just to try what happens. And they approved it within a few days 🙂

During the waiting, I kept working on some small enhancements and sent new version for another approval.

It’s called “UI Builder Dock for ServiceNow,” and the upgraded version (1.0.2) is already available through standard Google Chrome Extensions.

I consider myself a person who values efficiency, and I always seek opportunities to simplify processes and enhance ease of use. With UIB, however, I think there is still considerable clicking involved, which can be cumbersome.

Well, I built something 🔮

Most frequent way to call Data Resources is probably after some client action (Button > Events > Button clicked event) or after some other action (Data Resource) finishes.

Anyway, Data Resources are callable from client scripts via the API object as well 👇

There are several ways in which you can show/hide pages in Configurable Workspaces: Roles, Inline Conditions, Audiences… But what if you need to make any advanced decision via scripting? Checking GlideRecords, calling Script Includes…?

Well, that’s why there are UX Screen Conditions for.

Lets have a look!

There is a nice article written by MGOPW here. I wanted to extend it a little bit, especially for those cases when you don’t have access to DEV Tools / NED Tools (I don’t; don’t ask me why 🤷‍♂️), and moreover, I wanted to take a look at it with practical examples.

So, let’s have a look.

So, I’ve been thinking about this for a while. Since I work with UI Builder pretty much every day and keep running into all sorts of tips, tricks, and problems, I figured it’d be cool to start sharing them. Not everything is in the official docs or on the community forums, and maybe this blog can help fill in some of those gaps.

I’m planning to share tips, tricks, and tutorials — especially those lesser-known features and workarounds that aren’t so obvious but might come in handy when building custom interfaces in ServiceNow. Let’s see where this goes!

So, stay tuned, you know — one trick at a time 😎