At our customer we have the requirement to create Identities based on JobData. So we need for the same employee which has multiple Poslitions (Worker_Job_Date → Primary, multiple non primary).
So in some cases the user needs to store the information in one Identity. But when the user works in different Units within the United State, in some cases for the first job they need an indentity, for the second job another identity.
We like to write a csv connector which extract the information from the aggregated EmploymentData and the the effective Identities are created to support that regulatory requirement.
But now we do not know how to configure the workday (or workday saas) connector, that the content of the Employment_Data in form of the xml. Is anyone has a similar requirement and did already stored it that way.
Or is it possible to get the worker_job_data as primary Object from Workday and searching afterwards the employee to read the data about the personal data from it.
If you are able to pull the position id via XML you could possibly reference this as the Schema account ID rather than the FILENUMBER. It may be worth considering an alternative connector such as Web Services for the RaaS reports API to get the data as you need.
Considerations would be on how to do write backs. There are a lot of unknows with this approach from my perspective. Hopefully someone has done something similar. An Expert Services call or ask an architect call is advised to aid in understanding the full scope and use cases.
If not already considered, it may be worth to understand how many extra identities will be generated. How many positions are across the organization as a whole. Is it intended that someone receive multiple licenses for each position, such as an O365 Mailbox?
Hi Fred,
we are currently discussing internally how to solve the issue. Thanks a lot for your response, I think the usage of the WebService Connector should be our preferred solution (2 connectors –> One read the primary job-profiles to write back data, one to use the job-data web-service).
We already handled the requirement in IIQ with csv export in Workday and import into a database-layer application at our customer. So we know we do that for around 50 employees. So we are already aware about the additional license cost.
Great to hear. We are moving forward with a RaaS API connection. We have the potential for active positions and historical positions and including a rule criteria to allow an active to be considered x number of days prior to effective date and possibly x number of days after a position end date.