Insights & updates from our experts
Another improvement of the UI Extension functionality has been released. This one significantly improves the presentation of the fields that organizations have added to their requests.
In the past, the additional fields were presented in the Notes section of the requests.
Going forward they are presented in their own section, which is formatted just like the rest of the request.
In Edit mode, the formatting of the UI extension fields is now also consistent with the rest of the Request form.
This does not just make the information look better. If that was the only benefit, we would not have spent 2 months of development effort on this enhancement. This actually provides some valuable benefits:
- The section titles, field labels and field options are displayed in the user’s preferred language,
- Dates are displayed in the date format associated with the user’s language preference, and
- Dates and times are displayed in the user’s timezone.
These preferences are now also taken into account in Self Service. The same goes for when a Change Summary PDF file is generated for the approvers of a change that includes a request with a UI extension.

An AI SRE that knows your incidents
Most AI SREs are pattern matchers trained on public data. They know what a memory leak looks like in the abstract. They don't know that your payments-api has a flaky liveness probe everyone ignores, that the checkout team owns the retry policy, or that the last three "database incidents" were actually cache misconfigurations. That knowledge lives in your postmortems, your Slack channels, and the heads of two senior engineers.

How Long Should ITSM Implementation Really Take in 2026?
Most vendors will tell you ITSM implementation takes six months to a year — but modern, configuration-first platforms have rewritten the math entirely. See what real implementations look like in 2026, and why a long rollout is now a choice, not a given.















.webp)
.webp)


.webp)











