We are using the Workday HCM SaaS Connector in SailPoint ISC and have enabled the Future Date Offset to retrieve future-dated worker changes.
However, we have observed that the configured Future Offset is being applied to all eligible future-dated events, including Future Hire Events and Future Termination Events. As a result, ISC is aggregating these events in advance whenever their effective dates fall within the configured offset window.
Our objective is to understand whether the Future Effective Date Offset can be selectively applied to specific event types only, rather than being universally applied to all future-dated events processed by the connector.
Hello Jaya, the Future Offset is a single source-level value, so there is no way to set separate offset days for hires vs terminations. That part isn’t supported as far as I know.
What you could try though is controlling the event lists under Aggregation Settings. The Future Hire Events and Future Termination Events fields decide which Workday business processes qualify for future aggregation. If you only want future hires, try removing the values from Future Termination Events and test it with a full aggregation. Terminated workers should still get picked up after their actual termination date based on the configured Termination Offset.
Now, if you still need the future termination data coming in early (for visibility or reporting) but just don’t want it to trigger deprovisioning yet, keep those events configured and handle the timing in your lifecycle state mapping instead. Check that FUTURE_ACTION represents a termination event first, then compare FUTURE_DATE or TERMINATION_DATE with the current date before moving the identity to inactive. That way ISC sees the future event without starting deprovisioning early.
So a different offset per event type isn’t available, but between the event lists and lifecycle state logic, either of these approaches should cover what you are trying to do.
