Transforms: requiresPeriodicRefresh (default value, multiple uses)

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

Hi there,

The existing transforms (e.g. Random Numeric | SailPoint Developer Community) have an optional attribute requiresPeriodicRefresh.

requiresPeriodicRefresh - This true or false value indicates whether the transform logic should be reevaluated every evening as part of the identity refresh process.

What is the default value of this attribute? Where is this documented?

If there are multiple transforms used, which requiresPeriodicRefresh is taken into consideration? Only the most external one? Where is this documented?

{
    "id": "2a9cf173-e9be-4b7a-9055-2431d0ddccfa",
    "name": "test requiresPeriodicRefresh",
    "type": "static",
    "attributes": {
        "x": {
            "attributes": {
                "length": "3"
            },
            "type": "randomNumeric",
            "requiresPeriodicRefresh": "true|false"
        },
        "y": {
            "attributes": {
                "length": "3"
            },
            "type": "randomNumeric",
            "requiresPeriodicRefresh": "true|false"
        },
        "value": "$x $y",
        "requiresPeriodicRefresh": "true|false"
    },
    "internal": false
}

How do the 3 requiresPeriodicRefresh attributes influence each other?

whether the transform logic should be reevaluated every evening as part of the identity refresh process

Does this attribute have no influence for the 8 AM scheduled identity refresh?

Thanks in advance for any information helping me understand this attribute.

Best regards,
Andrei

2

Hi @adamian

You can find that information in Account Attribute Transform

image
image1000×236 32.4 KB

Thanks
Krish

3

Hi @MVKR7T, this is the information that I’ve already posted and from what I can see doesn’t answer any of my questions. Please elaborate.

4

Hi Andrei,

Even I had the same doubt. As per my experience the default value of requiresPeriodicRefresh is true. If you dont want to evaluate the logic again you need to explicitly add false when declaring the transform.

Thanks
Rakesh Bhati

5

Hi @colin_mckibben, is this the right place to ask such such a question?
I think that in the end someone from SailPoint will have to answer the question, as only the employees would definitely know the answer, right?

6

My bad, I was rushing. So couldn’t read your question completely.

Here is my understanding, can be wrong even. Need to replicate the scenario.

By default requirePeriodicRefresh will be false.

As the name indicates, Transform need to be re-evaluated again and again. But why do you need that ?

We read data from Accounts (HR Source mainly) for identity attributes, apply transform if data needs to be transformed. When you run HR source aggregation, user data might changed in HR system, so Identity Profile gets refreshed, Transforms gets executed automatically.

Once HR source aggregation is completed, what is the point of evaluating Transforms again ? What change can happen.

So the Transforms might not need to be executed unless there is an aggregation.

In the evening scheduled refresh task, Transforms do not need to evaluated. Do you need for some reason, for example you built Transforms based on dates like LifeCycleState, which can be re-evaluated.

This is my theory, I never tested this even. We can replicate and test.

Yes. Let SailPoint confirm the answer and update the documentation.

Thanks
Krish

1 Like
7

The description provided by @MVKR7T mirrors my understanding. I’ll just add that the flag is only valid in the top level of the transform. If it needs to be re-evaluated, then the whole transform will be re-evaluated. If the top level does not need to be re-evaluated, then the subsequent steps will not be processed and re-evaluated anyway.

2 Likes
9

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