Well, it had to happen sooner or later. This extension has been in production for over a year, with 16 versions under its belt, and there’s never been a need for a hotfix or a rollback.

Actually, it’s not even a hotfix in the true sense of the word this time—nothing in the application itself broke. ServiceNow just changed the structure of custom components. Previously, custom components created via UI Builder were wrapped in a special sys_cb_metadata record; now, the sys_id you see in the URL is a direct link to the sys_ux_macroponent.

At the same time, it seems it’s no longer that easy to distinguish between a custom component created in UI Builder and one created via the UI Framework based on the data alone.

In the previous version of the extension, I identified them precisely by whether the macroponent had a linked sys_cb_metadata record. That no longer seems to be the case; the only clue (AFAIK) is whether a Root component is implemented or not.

• If a sys_ux_macroponent has a root_component implemented, it’s a UX Framework component.
• If it doesn’t, it’s a UI Builder component.

We’ll see; I’ll keep an eye on it.

So, now I just hope I didn’t break anything else with that hotfix 😎

v1.0.17 s currently being deployed; you can expect it shortly.

Jan