Issue 1) Story created in Servicenow using any script will not reflect in Azure DevOps.
Resolution: Remove the Condition: gs.getSession().isInteractive(); from "Synch Story with Azure DevOps" Business Rule.
Issue 2) Infinite looping with [code] [/code] when a Azure DevOps Work Item field is mapped with ServiceNow Story Work Notes or Additional Comments.
Resolution: Replace the Condition: gs.getSession().isInteractive(); with current.sys_updated_by!="system";
in "Synch Story with Azure DevOps" Business Rule.
Issue 3) Sometimes more than one story will get created in Azure DevOps if script not written correctly.
Resolution: Add some buffer in BR using gs.sleep(30000); and gather all information you want to prepopulate in Story one BR and ensure createStory.insert(); is at last of BR.
Note: Using createStory.update(); may create more than 1 story.
Some External Field Name for field maps:
System.Title
Microsoft.VSTS.Common.AcceptanceCriteria
Microsoft.VSTS.Common.Priority
Microsoft.VSTS.CMMI.Blocked
Custom.CallerName --- for custom fields remove the spaces
You can try using the above to get field names.
Issue 4) After cloning we need to Deregister the Prod DevOps Project and Register the Non-Prod DevOps Project. But the Register Webhook will not work in cloned instances .
When we check the logs, we will get the below error:
Instance : XYZ Project ABC, Action : Register Webhooks, Message : Error on Register Service hook to Azure DevOps: Error occurred while trying to: SYMMETRIC_UNWRAPPING, Cause : Cannot construct KMFOutputString from nil string
Resolution:
- Go to Prod instance: https://prod.service-now.com/token_verification_list.do
- Open the auth-token record.
- Unlock the token
- Copy the token
- Go to Non-Prod Instances: https://nonprod.service-now.com/token_verification_list.do
- Delete all the existing auth-token records
- Create a new auth-token record with the same token which was copied from Prod
- Bring the Auth Token column in List View and link the newly created auth-token with the Azure DevOps Instance
- Now Register Webhook will work in cloned instances.
Issue 5) When multiple Azure DevOps Work Item Types are mapped to a single ServiceNow table, then Export and
Import of work items works based on the first created table and Field mappings records.
Ex: Suppose Incident and User Story table of Azure DevOps are mapped with rm_story table of ServiceNow.
Resolution:
Step 1) Modify the OOB Subflow "Create Azure DevOps WorkItem and process"
Create a flow variable "wrktype" and assign it what type of work item needs to created in Azure DevOps based on the Work Title.
Use the same flow variable in Work Item Type of Create Work Item action.
Note: You will not be able to modify the OOB Create Work Item action mapping step, as you will get the below error and will not be able to save the Subflow.
So create a new action for Create Work Item in new step and map the fields accordingly as shown below and then delete the OOB Create Work Item action step.
Modified Subflow:
Step 2) Map all the fields of both the tables, no matter whether those fields are present in Azure DevOps Work Item or not.
Ex: In this case the Resolution Notes field is only available in Incident work item but not in User Story work item, but we need to have the exact same field mapping for both the tables, so we mapped it for User Story also.
Story <-> Incident field mapping:
Story <-> User Story field mapping:
