Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

TicketStatusJSON does not fetch ticket status

RV
Regular Contributor
Regular Contributor

We have onboarded ServiceNow as a Ticketing System and created REQ through CreateTicketJSON.   and are looking to reconcile the Ticket status back to Saviynt.    We see the Ticket Status API call working in Postman, but the same call does not get the status back. 

ARS Task Key has the REQ0511267 populated under Ticket ID.

Below are the details 

TicketStatusJSON :

{
"call": [
{
"name": "call1",
"connection": "userAuth",
"url": "https://xxxxxxxxxxx.com/api/now/table/sc_request?sysparm_query=number=${ticketID}&sysparm_limit=1&sy...",
"httpMethod": "GET",
"httpHeaders": {
"Authorization": "${access_token}" },
"httpContentType": "application/json",
"ticketStatusPath": "result[0].state",
"ticketStatusValue":[
"Closed Complete",
"closed",
"CLOSED",
"Closed"
],
"disContinueStatusValue":[
"Closed Incomplete",
"closed incomplete",
"CLOSED INCOMPLETE"
],
"successResponses": [
{}
]
}
]
}

 

Logs : 

2023-05-22 17:14:46,787 [quartzScheduler_Worker-11] DEBUG services.ArsTaskService - ticketId=[REQ0511267] for SERVICEDESKCONNECTION=28

....

2023-05-22 17:14:46,834 [quartzScheduler_Worker-11] DEBUG rest.RestProvisioningService - response of getNewStatusForTicketIDs: null
2023-05-22 17:14:46,834 [quartzScheduler_Worker-11] DEBUG rest.RestProvisioningService - disContinueStatusList : null
2023-05-22 17:14:46,835 [quartzScheduler_Worker-11] ERROR rest.RestProvisioningService - Error in closing ticket...response: null
2023-05-22 17:14:46,835 [quartzScheduler_Worker-11] ERROR rest.RestProvisioningService - Error in closing ticket...response: null
2023-05-22 17:14:46,835 [quartzScheduler_Worker-11] DEBUG rest.RestProvisioningService - ticketsToBeClosed.size=0
2023-05-22 17:14:46,835 [quartzScheduler_Worker-11] DEBUG services.ArsTaskService - completedArsTaskKeySet size= 0
2023-05-22 17:14:46,835 [quartzScheduler_Worker-11] DEBUG services.ArsTaskService - rejectedArsTaskKeySet size= 0
2023-05-22 17:14:46,835 [quartzScheduler_Worker-11] DEBUG services.ArsTaskService - End Check Status And Close Tickets
2023-05-22 17:14:46,835 [quartzScheduler_Worker-11] DEBUG services.ArsTaskService - Found List of Tasks[]
2023-05-22 17:14:46,836 [quartzScheduler_Worker-11] DEBUG services.ArsTaskService - Exiting processServiceTickets
4 REPLIES 4

RV
Regular Contributor
Regular Contributor

Figured it out.   I was using the connection name incorrectly.

Diego
New Contributor II
New Contributor II

I am getting a similar error. What specifically did you change in the ticketStatusJSON to fix the issue?

RV
Regular Contributor
Regular Contributor

Connection Name in the connectionJson should match the connection name in the TicketStatusJSON.  Please verify if they are same in your case or not.

Diego
New Contributor II
New Contributor II

Are you referring to ensuring that ["connection": "userAuth"] in TicketStatus matches ["userAuth"] in the connectionJSON?