I currently have a workflow in place where, once AD account provisioning is completed, the user receives an email notification with instructions username and password. When the user logs in it will updates the Login Date attribute.
We now need to add a reminder notification process for users who have not logged in
Requirement:
If a user has not logged in within 7 days (based on the Last Login Date identity attribute), set a flag to True.
Trigger a reminder email notification to those users.
I would like to incorporate this logic into the existing workflow and include it in a reminder notification loop.
Could you please advise on the best way to implement this within the current workflow design?
Hi @gayare - I would advise against adding a 7 day wait within that loop. You stand to have a lot of executions sitting in a suspended wait state. You could add a second workflow and use the Scheduled Search trigger to look at the account create date and compare to last login and use that to send the reminder. You would need to construct a search that returned what you needed for that. Something along the lines of created:<=now-7d AND attributes.loginDate:ISNULL
You can use scheduled trigger for 1 or 2 time a day which will check attribute change (login date) and next have the conditional check() if true you can get identity details to send mail and end else end.
Hello Gayathri. You can extend the existing workflow like this:
Provisioning Completed → Initial Email → Wait For 7 Days → Get Identity → Verify Data Type on Last Login Date
If Last Login Date is empty, send the reminder.
If it has a value, end the workflow.
For Get Identity, use $.trigger.recipient.id.
Use Verify Data Type for the login check and test with a real never-logged-in identity, since the value may be null, missing, or empty depending on the mapping.
You do not need a separate flag just for the reminder decision. If flag=True must be stored as an identity attribute, it should come from a mapped source attribute or identity-profile logic rather than a direct workflow update.
If reminders need to repeat until login, I would use a separate Scheduled Trigger workflow.
As you suggested, I added the change. However, in the workflow step below, I need to compare the identity attribute with today’s date and the last login date. If the user has logged in within the last 7 days, the value should be set to true; otherwise, it should be set to false.
At the moment, the step is not working as expected, and I believe there may be an issue with the logic or configuration.
Could you please take a look and let me know what might be causing the problem?
You can define a variable with today’s date initially when the workflow starts using $.now() and then you can compare it last login timestamp using compare timestamps value to see whether it is in last 7 days.
Hello Gayathri. The issue is that IsPresent only checks whether LastLogin has a value. It does not check whether the login was within the last 7 days.
I would suggest this flow:
Get Identity Recheck → Is null → Is timestamp → Compare Timestamps
Is null on $.getIdentityRecheck.attributes.LastLogin
True → send reminder
False → continue
Is timestamp
True → continue to Compare Timestamps
False → check the attribute format/mapping
Compare Timestamps
Value 1: $.getIdentityRecheck.attributes.LastLogin
Operator: Is On or After X Days Ago
Value 2: 7
True means the user logged in within the last 7 days, so end the workflow. False means the login is older than 7 days, so send the reminder. Enter 7, not 7 days; the comparison is relative to the workflow execution date.
Also, your Wait 1 is currently set to 1 day. If that is only for testing, that is fine; otherwise change it to 7 days.
For the flag, the comparison only controls the workflow branch. If the flag is only for deciding whether to send the reminder, I would not store a separate attribute.
