Limiting processing / utilization costs in a transform

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

I have seen hints or guidance to be careful on transforms that you don’t update IDN values based on other IDN values changing.

On a transform, is there a way to stop an evaluation from evaluating?
Example, if source attribute and IDN attribute are the same, break the given transform from evaluating and leave the current IDN value as is.

Or is IDN doing a blob type update where it gets all Identity Profile mappings and write out everything to IDN regardless if there is a change or not?

Example: If an IDN value is for the most part only needs to be written once and it shouldn’t be updated unless a certain condition happens. Can a transform help facilitate this? Or are we limited to only a rule handling such an operation?

2

You can utilize requiresPeriodicRefresh flag in the transform to restrict nightly refresh.

requiresPeriodicRefresh - This is a true or false value indicating whether the transform logic must be reevaluated every evening as part of the identity refresh process.

3 Likes
3

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.