SNow connector - SRQ when closed as Not solved task is not getting updated correctly

[JothiJayamani]

Hi Team,

When SRQ is closed with close notes such as Not Solved(Gone) or Not Solved(Unable) , the corresponding task in Saviynt should go Discontinued state. But its going to Completed state.

This issue was not occurring in V5.5. After upgrade to V2024.3 , we are noticing this issue. Any suggestions pls to fix the issue.

Tried both the Jsons attached. Kindly check

Thanks

[rushikeshvartak]

Please share postman screenshot and curl command [Refer https://codingnconcepts.com/postman/how-to-generate-curl-command-from-postman/ ]

⚠️‼️‼️Do not upload any attachments that contain sensitive information, such as IP Addresses, URLs, Company/Employee Names, Email Addresses, etc.‼️‼️⚠️

[JothiJayamani]

Hi @rushikeshvartak ,

Could you please let me know what status should be passed here in the json  for saviynt V2024.3 for capturing SRQ is that is not solved.

The below worked in V 5.5

"disContinueStatusValue": [
"Closed Incomplete"
],

Regards

Jothi

[JothiJayamani]

Please also find the curl command and postman screenshot that is requested

curl --location 'https://xyz.com/api/now/v1/table/incident?sysparm_query=number%3DSRQ05606188&sysparm_limit=1&sysparm...' \

--header 'Authorization: ••••••' \

--header 'Cookie: BIGipServerpool_pmivdev2=bebbeae6a617c8fc89fe2d7afcb71b4c; JSESSIONID=FAF0A11CBAAAD389516035FF9BDC505C; glide_session_store=2A37B8CA1B524E14D6C4DBD0B24BCBA1; glide_user_route=glide.c0d83dbcdc7ab2f969fb3607990843a2'

Regards

Jothi

[rushikeshvartak]

if SRQ completed then it works properly ?

[JothiJayamani]

Hi @rushikeshvartak ,

Yes when SRQ is solved successfully , it works fine as expected.

Regards

Jothi