In this week’s UI Builder Bytes, we’re going to take a closer look at the list components: List and List - Simple. These list components are among the more popular components in UI Builder, and I’ve seen similar questions a few times on the Now Experience community and in the sndevs slack around them. They’re questions that I also had when I first started working with UI Builder and the list components.
This week in our UI Builder Bytes series we’re going to take a closer look at client scripting. We did touch on and do a quick demo around client scripting in the UI Builder - Client state parameters, Client Scripts, and Events post, but I wanted to look at it a little deeper and call out some of the more common methods and properties you might need to use.
This week in our UI Builder Bytes series we’re going to take a look at modals. You can access past posts at the UI Builder Bytes tag. So What is a Modal? A modal (also called a modal window or lightbox) is a web page element that displays in front of and deactivates all other page content. To return to the main content, the user must engage with the modal by completing an action or by closing it.
So far in our Now Experience UI Builder series we’ve looked at creating pages, adding components to pages, using data sources to return data from the platform, and then binding that data to our components. As we continue this week we’re going to take a look at client state parameters, client scripts, and events. These are the tools that are going to allow the components on our UI Builder pages to communicate and share data with each other and ultimately make these pages more powerful.
It’s Now Experience week on the developer blog, and the Now Experience UI Framework had some significant enhancements and new capabilities in the Quebec release. UI Builder The biggest and most obvious of these new capabilities is the new version of UI Builder in Quebec. UI Builder is a WYSIWYG web user interface builder that enables developers to build new pages or customize existing pages for web-based workspace and portal experiences using ServiceNow Experience Components and custom web components.
Last week we dove into creating and using data resources in UI Builder by binding the output from a data resource to component properties in order to make our components more dynamic. This week we’ll continue our UI Builder series by looking at the Entity View Action Mapper (EVAM) type of data source. What if you want to show a data element as a card in a row, list, or a grid view, rather than one of the list components?
It is ServiceNow’s new release season! With the Quebec release in Early Access, we will show some enhancements targeted around being more effective and efficient as a developer. To get access to these new things, you have to upgrade! This article will be about three new features in Analytics, Reporting, and Intelligence. To view the whole list, check out the release docs. AI Search New search! I am so excited about the new search capabilities released in Quebec.
We are releasing some UI Builder related content every week during the Quebec Early Availability period. So far we’ve covered how to get started and a quick overview, and all about pages in UI Builder. This week we’ll be focusing on Data Resources. A Data Resource in UI Builder allows you to fetch data from the instance to the page and then consume that data from a component. Previous to the Quebec release, component authors had to hard code REST or GraphQL queries as well as any data transformations into their components.
Quebec continues to enhance the mobile client features with some really cool stuff that will increase adoption to your end users. Here are a few of my favorites (and what I am most looking forward to when GA becomes available.) Advanced Search (AI Search) AI Search provides a more consumer-like experience across the platform. It is available on the instance as well as the mobile platform to produce more accurate search results than the traditional (Zing) keyword based search.
As we learned last week, the first thing you’ll do when working with experiences in UI Builder is create or open an experience and create a new page. When you create a new page you’ll be able to add containers, components, data resources, and more to the page. This week, we’ll look at pages a little more closely and explore pages and their settings, parameters, templates, and variants. Page Templates When you create a new page in UI Builder, you’ll have the option to create a blank page or a page from a template.