Insights & updates from our experts
Account designers and administrators are now able to export and import custom views. This can be useful, for example, when custom views have been created in a QA environment. After these custom views have been tested successfully, they can now be exported and subsequently imported in the corresponding production account. Custom views are often used with custom collections in UI extensions, record types which could already be exported and imported.
To make use of this option, a designer or administrator can navigate to the ‘Custom Views’ section of the Settings console and either click on the Actions button in the toolbar, and selecting the ‘Export…’ option or use the ellipses menu. Alternatively, an export can be made or scheduled from the ‘Exports’ section of the Settings console.

Similarly, the ‘Import…’ option of the Actions menu makes it possible to import the data into the required environment, after the CSV file has been properly prepared for that.

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)












