Saviynt unveils its cutting-edge Intelligence Suite products to revolutionize Identity Security!
Click HERE to see how Saviynt Intelligence is transforming the industry.
Saviynt Copilot Icon

Unable to pass user attributes in UPDATEUSERJSON

shibinvpkvr
Regular Contributor II
Regular Contributor II

Hi,

I have a requirement to create JIRA ticket based on a user attribute update in Saviynt. I have created a REST connection to create the ticket when UPDATE USER task is completed. Please find below my UPDATEUSERJSON. Task is completed and Ticket is getting created as well. However it does not pass the actual values of user attributes, instead passing the variables as is. can you please advise if I am missing anything here?

{
"actions": {
"Update Login": {
"call": [
{
"callOrder": 0,
"connection": "acctAuth",
"httpContentType": "application/json",
"httpHeaders": {
"Authorization": "${access_token}"
},
"httpMethod": "POST",
"httpParams": "{\"serviceDeskId\":\"5\",\"requestTypeId\":\"1793\",\"requestFieldValues\":{\"summary\":\"Contractor Verification ${user?.username}\"},\"form\":{\"answers\":{\"1\":{\"text\":\"${user?.displayname}\"},\"2\":{\"text\":\"${user?.employeeid}\"},\"3\":{\"text\":\"${userManager?.displayname}\"},\"4\":{\"choices\":[\"${user?.customproperty60.split(',')[1].split(':')[1]}\"]},\"5\":{\"text\":\"${user?.customproperty60.split(',')[2].split(':')[1]}\"},\"8\":{\"date\":\"2024-05-15\"},\"9\":{\"date\":\"2024-05-15\"}}}}",
"name": "Update Login",
"successResponses": {
"statusCode": [
200,
201
]
},
"unsuccessResponses": {
"statusCode": [
400,
500,
401,
403,
404
]
},
"url": "https://URL/rest/servicedeskapi/request"
}
]
}
}
}

shibinvpkvr_0-1726528974690.png

 

 

 

5 REPLIES 5

rushikeshvartak
All-Star
All-Star

If one of the value failed to evaluate then it will cause issue. I believe this is due to userManager Object. Limit the variables and validate 


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

shibinvpkvr
Regular Contributor II
Regular Contributor II

Actually yes. I figured that later. There are some inconsistencies with the binding variable in this version.  

${usersManagerObj?.displayname} works >> userManager.displayname does not work. 

${usersObj?.customproperty60}  works >>  user?.customproperty60 does not work, where as user.username, user.displayname etc. still works.

  • xxxsObj are latest variables are latest one and includes all table columns

Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

stalluri
Valued Contributor II
Valued Contributor II

@shibinvpkvr 

For Release v23.10  you can use these binding variables. 

usersObj${usersObj?.username}

usersManagerObj

${usersManagerObj?.username}


Best Regards,
Sam Talluri
If you find this a helpful response, kindly consider selecting Accept As Solution and clicking on the kudos button.

shibinvpkvr
Regular Contributor II
Regular Contributor II

I am aware of the new binding variables xxxsObj. However thought we can still use the old ones. I believe user.customproperty60 was working before. Anyway will use the new binding object variables going forward to avoid any discrepancies and compatibility issues. 
thanks everyone.