If someone asks “What is one of the most significant functionalities of ServiceNow?” I believe many will answer “Forms”.
Form is a the most fundamental component of the platform that allows you to define input fields and collect data.
Once you create a form you can use it for data collection everywhere: ServiceNow native UI16, Service Portal and UI builder.
Using forms in UI builder is a bit tricky because it requires wiring up multiple items, but it is a straightforward process. Once you get it — you will be able to build advanced form interactions and functionality.
It’s being just a month since the full scoped Now Experience UI Framework has been released, and the exciting news for ServiceNow developers coming out almost every day.
Once you start digging through development concepts you will realize that it’s a very structured approach: page/component state, events, client scripts, and data brokers — those are your basic lego blocks.
The true power of the Now Experience UI Framework belongs to custom components. That is where you have limitless possibilities and can use all of the available web development technics, frameworks and libraries to build ServiceNow functionality.
You hear me right…
There are some basic concepts developers have to understand before building web applications with the Now Experience Framework. Two of them are the most important and play a fundamental role for all of the apps: App Shell and Routing.
App Shell defines an environment where your UX pages will be rendered. It provides general look & feel for your application (header, footer, navigation menu and a content area):
Now Experience app is an SPA (Single-page application) which means the only content area will be reloaded while you’re navigating between pages, header/footer, and a navigation menu loaded once and never reloaded…
Now Experience framework was originally introduced in 2020 as a new tool for building ServiceNow custom UI/UX and web applications. At that time we did not have a chance to dig deep into the architecture since the initial rollout was very limited, but everything changed with a Quebec release.
Quebec release introduced a complete toolset for building modern web applications on the ServiceNow platform — starting from a low-code UI Builder to a fully updated CLI for creating custom web components.
Now Experience Framework is a set of tools, concepts, and architecture principles that developers are going to use for…
Most of ServiceNow apps do not have the ability to interactively reach out to online users when something happens. Real-time notifications and alerts like this can be very hard to implement:
Today we can do that in 2 minutes and support up to 10K online users out of the box.
Here you can download a simple update set that includes just three items:
Today we live in a fast-paced world. The ability to monitor and timely react to important events is crucial. Implementing those capabilities for your business/web applications can be truly challenging, especially when you develop applications on PaaS platforms like ServiceNow, Salesforce and Appian.
Just take a very simple use-case that all of us facing every day — an important event occurs (security alert, critical approval request etc.) and we need immediately display in-app notification for online users:
Well, this kind of interactive real-time communication simply not supported by some of the PaaS platforms and web applications. That is because it…
PaaS and low code platforms rule the business application development today. The platforms like ServiceNow, Salesforce and Appian score high against custom software development in terms of cost-efficiency and time-to-value.
However, there is a price to pay — we have to deal with UI and functional limits, platform-specific tools, custom API etc. That often leads to improper functional architecture and therefore hidden risks and future maintenance costs.
One of the most underestimated features that unfortunately lacks PaaS support is real-time interactivity — the ability for online users to get notified and be able to react to important events instantly, right…
ServiceNow recently made a gift for a development community by releasing UI Framework which enables you to build custom web components. It is a very powerful web development tool, and it comes with a number of out-of-the-box components. With no doubts, eventually, it is going to change the way you build ServiceNow applications.
Currently (April 2020) UI framework has some limitations you should be aware of. We don’t know for sure why ServiceNow impose those limitations, but unfortunately, they may seem like a showstopper for many developers and can significantly affect the adoption of the framework. …
There is a number of use cases and business processes where we need to capture the user’s signature. It may sound like a trivial development task, but it still takes time to design(UI/UX), implement and integrate it into your ServiceNow applications.
We’ve just released a free Service Portal widget — Signature Pad, which takes care of everything:
About a year ago I posted an article about building a ServiceNow reference field with React. That is a good proof of concept how to use React components to implement the most complex ServiceNow field type.
Today, I have a new version of that component available, which is a bit simpler, more efficient and robust:
./webpack/servicenow.config.jswith the ServiceNow instance name, user name and password - this…