A common use case for HR drivers is to create identities in the Identity Vault prior to the person actually starting work. This allows preprovisioning of the access the person will need on the day the person starts.

The recurring polling of the driver polls as of the current date. This means the Get_Workers_Request will be as of the current date. The results returned will not include critical data such as job code, department, title, etc. that are needed for preprovisioning because that data is not yet effective.

For future dated hires and re-hires, the driver needs to return the data as of the start date as well as an attribute with the start date. This will provide the information needed for the downstream drivers to preprovision access.

The current driver CAN process future dated hires, BUT this requires requerying Workday with the effective date of the hire. The future effective date is stored in some driver scope local variables set by the default configuration's input transform policy, but subsequent policies have to be careful to not do a query that does not return the hire dates before the requery is done. This is because a query return without the hire date will set the driver scope local variable for hire date back to the current date and the driver scope local variable for "future hire" to false.

It would be better to have future dated hire functionality built in and not require additional logic to be built in the Publisher channel policies to get the future-dated data.

by: Warren A. | over a year ago | Other