Click HERE to see how Saviynt Intelligence is transforming the industry. |
on 06/13/2023 08:59 PM - edited on 08/22/2023 07:00 AM by nimitdave
For any updates to Workday, you will have to use SOAP APIs. This is irrespective of whether you used SOAP API or RAAS for user import.
Please refer to Workday connector documentation for details of configuring the Workday SOAP connection and enabling email generation in Saviynt.
Below steps provide one way to accomplish this use case of updating back in Workday through user update.
This includes passing the current date as the effective date and Worker Reference (eg: Employee_ID, Contractor_ID) based on the type of user.
https://docs.saviyntcloud.com/bundle/WD2-v23x/page/Content/Workday-Integration-Overview.htm
Hi @sudeshjaiswal what is the function of the below format? what date does it generate with this logic?
<bsvc:Effective_Date>${(new java.text.SimpleDateFormat('yyyy-MM-dd').format(new Date()))}</bsvc:Effective_Date>
Hello @navneetv ,
The expression ${(new java.text.SimpleDateFormat('yyyy-MM-dd').format(new Date()))} would generate the current date in the format 'yyyy-MM-dd'. For example, if the code is executed on June 14, 2023, it would generate the output: 2023-06-14.
Hi @sudeshjaiswal last question, how it works for future hires, for example, if someone is hiring on 24th June and today we receive the record then how the email will be updated as we are passing the current date as an effective date but the hiring date is future Since hiring date is future then effective from the workday side would be same as hiring date. then wouldn't we encounter the error while updating
Hi @sudeshjaiswal could you please confirm, if this current date effective date will work on future hiring records as well? or email writeback will happen only after the hiring date pass
Hello @navneetv ,
The current effective date is not applicable to future hiring records, and email writebacks will only occur after the hiring date has passed.'
Thanks,
After email has been generated through Saviynt for one user what should be the Trigger Actions when in the UserUpdate Rule as the user has been already imported through Csv based Schema job?