I have the below USERUPDATE JSON configured on the REST connector to write email changes back to Workday from Saviynt. This uses a REST connection because the attribute that needs to be updated on Workday is a custom object and cannot be done via SOAP (according to Workday team).
{
"actions": {
"Update Login": {
"call": [{
"name": "Update Login",
"connection": "userAuth",
"url": "https://xxxx.xxxx.com/ccx/api/v1/xxx/customObjects/upn/upn?updateIfExists=true",
"httpMethod": "POST",
"httpParams": "{\"worker\":{\"id\": \"${user.customproperty41}\"}, \"upn\":\"${user.email}\"}",
"httpHeaders": {
"Authorization": "${access_token}"
},
"httpContentType": "application/json",
"successResponses": {
"statusCode": [200, 201, 204]
},
"unsuccessResponses": {
"statusCode": [400, 401, 500, 503, 404, 403, 409]
}
}]
}
}
}
When I changed the email ID, the Update User pending task is successfully created however, it is not getting picked by the WS-RETRY job.
The task configuration is as follows:
I tried the user update rule with and without Update Login and made similar changes to the USERUPDATE JSON but still was unsuccessful in getting the pending task processed.
Note - For writing the network ID back to workday, the update rule with Update Login (and the same action configured in the USERUPDATE JSON) resulted in a successful update of the Login ID in Workday (again a custom object).
Any thoughts on how this issue can be resolved would be helpful.
Below is the postman screenshot showing the return response is 200 OK.
WSRETRY for Update user task job history run time:
Below is the UPDATEUSER JSON screenshot
Question - In the user update rule, while configuring CREATE UPDATE USER TASK, do any of the 3 options have to be selected - Update Login, Disable User, Enable User? I had to use Update Login to be able to successfully writeback the network ID to Workday. I tried with and without the option for email updates, but neither of the options have worked for me.
