3dl5q (3dl5q) asked a question.
Workflow Delay on Trigger
Hi there,
I currently have a workflow setup that triggers on activation of new user. The issue I'm having is that the user attribute 'Title' is collected immediately at user activation but the actual data that populated the 'Title' attribute is coming from a different lifecycle management app at a delay.
Is there any way to add a delay either after the trigger or before the trigger to account for the delay for the attributes to be updated?
I found the Wait For function. https://help.okta.com/wf/en-us/content/topics/workflows/function-reference/flow-control/flocontrol_wait.htm
While I don't know your full use case in general I try to avoid waits unless you know it is going to solve the problem essentially all of the time. They can potentially cause unexpected behaviors (such as compounding wait times) depending on the cards you are using. With built-in Okta event cards this is especially true due to how event-hook payloads are processed.
Typically a better solution (if possible) would be to evaluate if the most current change would be the "correct" one from the secondary lifecycle process.
So for example you create a user and lets say title is updated but its not the final version. Later the other source comes in and updates it. Now lets say the "first" time it is triggered the value is never one of the values the secondary lifecycle process would ever use.
You could then create either a lookup table (in flow) or a Workflows table (to be called) to find if the current title value is one of the valid title values. If it is not continue if would stop the flow. If it is then it would meet the continue if evaluation and continue processing.
While you can add the "Flow Control - Wait Until" or "Flow Control - Wait For" action cards to add a delay your Workflow you might want to take a look at the "Okta - User Okta Profile Updated" trigger card and evaluate the "Changed Attributes" output for title changes.