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.
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.