Auto-Mapping in Account Sync
Since the original introduction of Xurrent Account Sync earlier this year, many record types, including the most relevant ones such as request and task templates and UI extensions, have been added to this feature. It was also made possible to select a distinct set of records of a certain record type to be synchronized with an other environment. Now, in certain situations, it is even possible to map people and organizations automatically during the sync process. This is the case when Xurrent detects that both the source and the target account have the same account ID. This is true for wdc.Xurrent.com and wdc.Xurrent.qa, for example.

After importing the sync set in the target environment in the example above, 18 people needed to be mapped. For QA to production synchronizations, this is no longer needed. Users still have the option to manually change the automatic mapping, if they want. People and organizations that cannot be found in the target environment must still be mapped manually.

A Letter From Our CEO: What I've Learned, What I Believe, and Where We're Headed Together
When I joined Xurrent as CEO in February, I made a commitment to myself before I made any commitments publicly: I would listen before I led. I would get in front of customers, sit down with our partners, and spend real time with the incredible team that built this platform — before I said a word about where I thought we were going.

Xurrent named a Market Leader in Research In Action’s Vendor Selection Matrix™ for IT & Enterprise Service Management Solutions
Xurrent earns #1 rankings in customer satisfaction, price vs value, and recommendation index in Research In Action's global ITSM/ESM Vendor Selection Matrix report.

