Blog
Insights & updates from our experts
.webp)
.webp)
.webp)
It is no longer necessary for the value in the Employee ID field of a Person record to be unique. This extra flexibility is provided for large enterprises that have multiple legal entities in different countries.
In such environments, it is likely that the different legal entities use different HR systems, which introduces the possibility that there are multiple employees within the enterprise who have the same employee number. By allowing non-unique employee IDs, it becomes possible for these multinationals to register all their employees in a single Xurrent directory account and still use the Employee ID field. Even when all these employees are linked to the same Organization record in the directory account, it is still possible to use the Employee ID field without running into issues when the same employee number is used more than once.
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