Share all details about your problem, including any error messages you may have received.
Hello everyone. We are facing an issue with back-dated terminations in Workday. We have our Past_Termination_Offset value set to “30” as we would like Workday accounts to fall out of IIQ 30 days after termination. However, if someone is terminated in Workday and their termination date is dated more than 30 days in the past, the terminated user will NOT EVEN show up on Workday aggregation in IIQ. Instead, the terminated user is simply dropped and the related Workday account in IIQ is deleted. This is a problem as we rely upon the TERMINATION_DATE attribute from Workday to kick off our termination workflow in IIQ.
Does anyone have any insight into how this situation can be rectified? We realize that we can increase the offset to something like 90 days, but the possibility of a back-dated termination that is more than 90 days in the past is still there. If we miss a termination because the user simply stopped showing up on aggregation, then we will have an auditing/security issue.
I worked a lot on workday connector and I managed the same case.
yes this is the behavior of IIQ, if set the offset to 30, all the accounts with termination date < today-30 will not aggregate on IIQ, but they actually still exist in workday. Also, if you set 0 to offset, you can read all terminate accounts wituot limit on the date.
About me, you 2 possible solution:
you can set the offset to 0 (or 31 for example), use a custom rule where you find all the account with termination date 30 days to past and execute what you need.
you can use rapid setup configuration on application. With it you can configure an action will be execute after a number of days:
for example you disable or delete an account 30 days after the leaver event.
This is action will generate a plan and you can modify it or make everything you want in before\after prov. rule
I came up with another idea today that may work. I have an identity attribute of isTermed that is set to “false” for everyone until they have a termination date – then the value is set to “true”. I’m thinking that if a user falls off of the Workday aggregation, they will go from “false” to null. If that happens, then I’ll catch any back-dated termination and start the term workflow for them.
