Note
We've packed up and moved from Confluence to Discourse to bring you a better, more interactive space. Out of courtesy we didn't migrate your user account so - you will have to signup again
The Exalate team will be on holiday for the coming days - returning Jan 4
Enjoy & stay safe
I am setting up a sync between ADO and serviceNow. I want to sync the following:
bug == incident
enhancement == enhancement
demand == demand
The demand and enhancement items in ADO are custom work items but I don't think that maters. How can I determine in my incoming sync for SNow what type of ADO record it is so it creates the correct record on the SNow side? I've Googled a bit and not found this but I assume it's quite common.
TIA
Hi Jack,
This should help!
ADO Outgoing script:
ADO Incoming script:
Servicenow Outgoing Script:
Servicenow Incoming script:
Let me know if that works for you. Just make sure to use the correct issue type names when adding them. For more reference, you can take a look at: https://docs.idalko.com/exalate/x/gIYrAQ
Kind regards,
Ariel
Looks like I'm getting closer. When I try to sync from SNOW my outgoing replica looks like this:
I've tried a couple different methods to give it a default value that works but the only thing that works is
workItem.typeName = nodeHelper.getIssueType(replica.type?.name, issue.projectKey)?.name ?: "Bug"
which just makes every new item a bug regardless of what I send across.
I'm sure I'm missing something simple here.
To clarify, this works with any valid workitem type but tattoos all new items as that thing regardless of what they are on the SNow side; which suggests it's not getting valid data that it can extract the workItem type from.
workItem.typeName = nodeHelper.getIssueType(replica.type?.name, issue.projectKey)?.name ?: <AnyValidWorkitemType>
We can suggest to do a slight change on the Azure Incoming script to be:
Kind regards,
Ariel
I was able to come up with a way to solve this. I imagine it's not very elegant but it works for now. Later I will come up with a more economical way to do this but in the meantime here its is:
Outgoing sync from the SNow side. Very basic at this point. Just making it work.
Incoming sync on the Azure side.
I did attempt you updated method but I still couldn't get it to work. Not sure what I was doing wrong..