When changes occur to identity data or access model configurations (identity profiles, roles, access profiles, or applications), corresponding access for your identities may also need to change. These changes happen through identity processing, which can be initiated in response to events, scheduled, or executed manually.
What is displayed here is not really a Transform that you can take and deploy to your tenant.
Most engineers will probably look at this and realize that this is pseudo code or an evaluation that came from somewhere with predefined variables, date format handling and other error handling placed somewhere “out of view”, but for ‘absolute’ beginners, this will be confusing.
I don’t want to make this section sound harder than it is, so maybe something like the below would be clearer:
For example, a Transform built to represent the logic below evaluates the startDate and endDate attributes and selects the earliest future date:
[ pseudo code here ]
If I had to link to one page of the Transforms documentation to support this, it would be the Static transform instead of the ‘generic’ Transforms Overview Documentation, as this seems to be most in line with the kind of evaluation from the ‘Transform’ above: Static | SailPoint Developer Community
Thanks, @J_Hauser! I’ve added that link to our ticket. I see one of our writers has picked it up and started investigating. Thank you for helping to improve the docs!