This time there is a small, but significant enhancement: search now caches the search results. It means when you leave the extension and need to perform the same search again some time in the future, you don’t have to actually search again. The previous results stay available there for you (until the next search of course).

Jan

I had some time to work on the extension this weekend, so here we go. There is only one visible change: Data resources now show Input properties and Usage. Especially the Usage feature is another gap in UIB that had to be filled. 🤷‍♂️

Available in the Chrome Web Store already.

Enjoy 😎

Jan

I covered modals on custom pages in previous posts, but what if you want to implement a modal within any existing implementation, like the Service Operations Workspace (SOW)?

Lets take a look at that in this post.

One more version will be out soon, and there are a few new features 😎 There is a short walkthrough in the video below; take a look 👇

New version of the UIB Dock has been published. Here is what’s new 👇

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.