Insights & updates from our experts
More and more, organizations are using UI extensions to ask their users to define their requirements by filling out some required fields. That can dramatically improve the efficiency with which standard service requests get processed.
When a standard service request triggers a workflow, the specialists will not work on the original requests, however. They will receive tasks. To make it easy for them to get to the change requirements, they no longer need to first open the change in which the workflow is managed. They can now open the request directly from the task. And because the change requirements are often defined in the custom fields of a UI extension, the UI extension has been added to the preview of requests.
For change managers, we have also made it a little easier. When they open a change, the Relations section is already expanded so they can immediately access the related requests and problems.

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)











