Blog
Insights & updates from our experts
.webp)
.webp)
When importing records into Xurrent, the Source and SourceID fields are checked to see if a record already exists. This is also true when importing automation rules, which is done to transfer them between Xurrent environments, for example. When exporting automation rules, multiple export files are created; one for each automation rule type (request, request template, problem, etc.). When filling in the Source field, a unique SourceID must be chosen as well.
Until now, these SourceID values had to be unique across all the automation rule export files. If not, a Request Template automation rule may be overwritten by a Task Template automation rule, for example. To avoid such problems, the combination of Source and SourceID for automation rule imports do no longer have to be unique for different automation rule types.
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.
5 Mins
September 10, 2026
Incident Management
Service Management
News
Enterprise
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.
8 Mins
May 30, 2026
Service Management
Enterprise
Integrations