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

Workday Connector: Writeback User Id and Email to Workday

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on November 24 2020 at 11:25 UTC

Hello All,


We are working on requirement wherein we want to update the System User Name and Email Id value from Saviynt to Workday. Currently we have Workday is configured as a trusted source of users. Using the user update rules we were able to generate the User Update Tasks. However we have question on how does these tasks will be processed?


As per documentation we have configured the UPDATEUSERJSON with the SOAP API payload to update User Id in Workday. Which job to be used to process the 'Update User' tasks generated for Workday.


Update User Task Screenshot:


image




Thanks,

Pallavi

This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.
7 REPLIES 7

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on November 26 2020 at 13:56 UTC

I got the solution

This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on April 22 2021 at 04:14 UTC

Hi Pallavi, can you please share the solution?

This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on August 3 2021 at 12:40 UTC

Hello Pallavi,


Can you please share the details about the solution that you have implemented?


We have similar requirement to Writeback email address to workday.


This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on August 17 2021 at 20:35 UTC

Hello Arjun, We have configured workday writeback API calls as a part of updateuserdatajson parameter in Workday connection. You can configure user update rules to invoke update user task based on user profile updates. Specify the workday connection to be used to invoke writeback rules in a user update rule. Thanks, Pallavi Chaudhari
This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on August 18 2021 at 01:21 UTC

Hello Pallavi,


Thanks for the reply.


We are following the same steps as mentioned above. Only challenge which we are facing is that task which is created for update user is not picked by WSRETRY Job.


We have kept the Security system name as blank and added update user under task type in Provisioning Job, still don't see any action happening on the update user task under pending list.


Is it possible for you to share the updateuserdatajson? Currently we are using the one available under workday 1.0 document.


It would be a great help if you can share the updateuserdatajson by removing the customer specific details.


Thank you!


Regards,

Arjun Gadgul

This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on January 25 2022 at 15:56 UTC

Hi Arjun,

how did that update user task not picking up issue got resolved ?

This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on February 23 2022 at 09:00 UTC

Hello Vaibhav,


We had discussion with Saviynt engineering team and it was identified as bug for 5.5 SP3 version. Issue was resolved after moving to SP3.9 Version.


Please find the UPDATEUSERJSON :


[{

  "REQUESTXML": "${user.email != null && user.email != '' ? '<soapenv:Envelope xmlns:soapenv=\"http://schemas.xmlsoap.org/soap/envelope/\" xmlns:bsvc=\"urn:com.workday/bsvc\"> <soapenv:Header> <wsse:Security soapenv:mustUnderstand=\"1\" xmlns:wsse=\"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd\" xmlns:wsu=\"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd\"> <wsse:UsernameToken> <wsse:Username>'+USERNAME+'</wsse:Username> <wsse:Password Type=\"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText\">'+...> </wsse:UsernameToken> </wsse:Security> </soapenv:Header> <soapenv:Body><bsvc:Maintain_Contact_Information_for_Person_Event_Request xmlns:wd=\"urn:com.workday/bsvc\" bsvc:Add_Only=\"true\" bsvc:version=\"v36.0\"> <bsvc:Business_Process_Parameters> <bsvc:Auto_Complete>true</bsvc:Auto_Complete> <bsvc:Run_Now>true</bsvc:Run_Now> </bsvc:Business_Process_Parameters> <bsvc:Maintain_Contact_Information_Data> <bsvc:Worker_Reference> <bsvc:ID bsvc:type=\"'+(user.customproperty29 != 'Employee'?('Contingent_Worker_ID') : 'Employee_ID')+'\">'+user?.username+'</bsvc:ID> </bsvc:Worker_Reference> <bsvc:Effective_Date>'+new Date().format('yyyy-MM-dd')+'</bsvc:Effective_Date> <bsvc:Worker_Contact_Information_Data> <bsvc:Email_Address_Data bsvc:Delete=\"false\" bsvc:Do_Not_Replace_All=\"true\"> <bsvc:Email_Address>'+user?.email+'</bsvc:Email_Address> <bsvc:Usage_Data bsvc:Public=\"true\"> <bsvc:Type_Data bsvc:Primary=\"true\"> <bsvc:Type_Reference> <bsvc:ID bsvc:type=\"Communication_Usage_Type_ID\">WORK</bsvc:ID> </bsvc:Type_Reference> </bsvc:Type_Data> </bsvc:Usage_Data> </bsvc:Email_Address_Data> </bsvc:Worker_Contact_Information_Data> </bsvc:Maintain_Contact_Information_Data></bsvc:Maintain_Contact_Information_for_Person_Event_Request></soapenv:Body> </soapenv:Envelope>' : ''}"

 }

]


Regards,

Arjun Gadgul


This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.