In Discovery: Time Based Refresh

Product Research In Discovery
, ,
1

Business Problem
Previously, Identity Security Cloud would leverage a pre-defined time for refreshing target identities. For global organizations supporting multiple time zones, this pre-determined timing was not flexible enough to effectively support their need to perform joiner-mover-leaver events on a specific local time that was applicable for that identity.
With the introduction of Time-Based Refresh, administrators can now control the desired local time of refresh for targeted identities based on a given time attribute (Next Processing Date), which means less identifies must be refreshed at one time. ISC can now support identity state changes in different local times.

How You Can Help
We are continuing to validate our understanding of the problem space and our solution. Our Product Management team is opening a closed preview for customers throughout the month of September to exercise the feature and give us direct feedback on improvements. If you are interested in joining the preview, please complete our closed preview form by September 6th, Time Based Refresh Closed Preview Form.

2

Hi Kristen,

With the proposed changes, will it still be possible to trigger refreshes based on account aggregation or will this scheduling functionality replace it?

Best Wishes

Ryan

1 Like
3

there is no change for manual refresh or refresh that runs from aggregation. This use case is specifically to enhance JML which runs as part of batch refresh (8am / 8pm)

1 Like
4

Hello everyone! Thank you to all of the people that signed up to join our closed preview! We look forward to your feedback. At this time, closed preview registration is now closed.