Add the ability to do Date Format Transforms to the Workflow "Compare Timestamp" operator

[gmilunich (Geoff Milunich)]

Currently in IdentityNow there is an operator within the workflow engine that allows for “Compare Timestamps”, but this is limited to using timestamp values. This is a limitation because most systems do not have the data in the ISO8601 format that this operator requires, and as such, any dates that a company would like to use in a Date Compare for a workflow decision will need to be modified on the source to be in this format, which is not easy to impossible to do, or they will need to be pulled into an IdentityAttribute, which can lead to IdentityAttribute bloat, and can also lead to audit log noise if the field happens to be something like “lastLoginTime” for a source, which would show an attribute change log for each change.

Suggested Improvements:

• Add the ability to provide a string field for the date value and specify a format string in the same manner the Date Format Transform uses.
• Add the ability to specify ignore time value, to allow for the comparison to be on the date field only.
• Add the ability for a checkbox/menu selection (i.e. Enter Value, Choose Variable, Use Now) for now, rather than needing to provide the value from the Enter Value.

Currently there are several topics on the discussion forum that would be easily resolved by one or both of these suggestions:

Workflow Get Account Attribute

Hey everyone! We are looking to build a workflow that will check a user’s last login timestamp for their account and it will disable it if they haven’t logged in for 90+ days. This is for our Snowflake connector currently, but we would like the opportunity to apply this to other sources as well. The source does provide this attribute to us, so the data is there. Is there any way to get this attribute in a workflow to do a date compare? It looks like we can only use identity attributes, which c…

Workflow date compare issue

Hello Developer community, I am trying to use a Compare Timestamps bloc in a workflow to make a comparison between the current date (-1 day) and a startdate (coming from an identity attribute) Do you know how I can manage the variable $.now() (wich seems to return the current date on ISO 8601 format) to make that comparison in that bloc ?

Compare Timestamps operator displaying differently than expected in JSON

I am trying to create a termination workflow that sends a different email if the user had not signed in for 90+ days before termination. We have our last logon field formatted to ISO 8601 as required. My questions is shouldn’t the comparator display as something like “TimestampMoreThanXDay” in the JSON instead of “TimestampLessThanXDay”? It is not working as needed. [image] [image]

Workflow Trigger based on startDate

I am trying to build a workflow with trigger as “Identity Created”, currently we have one static “startDate” attribute and we have "actualStartDate" attribute which displays the currentdate and we have done this by using trasform with expression as now. [image] [image] I am using this below Identity Created trigger and its filter as below [image] [image] I see that startDate of the user will have to refresh and only when the refresh happens correctly at actualStartdate value, this workflo…

[zachm117 (Zach Mullins)]

Thanks Geoff for creating this feature request! I agree that this would be a very beneficial improvement.

[drosenbauer (Devin Rosenbauer)]

Additionally, if you choose to ignore the time component, make sure that you specify the time zone in which you want the comparison to take place. Timeless ISO dates are assumed to be at midnight UTC, but the other date might not be.

[gmilunich (Geoff Milunich)]

I have added 2 ideas to the Ideas section if people would like to vote on them:

This is the same as above: https://ideas.sailpoint.com/ideas/GOV-I-2948

This would be the minimal viable piece of this to allow for better use of dates in Workflows: https://ideas.sailpoint.com/ideas/GOV-I-2953