AndyC.64975 (Customer) asked a question.
'User Added to Group'
I have a flow (flow A) which is triggered by a users being added to a group. I have several related flows (flow B, C, D etc) that are also triggered by users being added groups, however these require completion of flow A before they can run without error. I can of course stick some waits in these flows but feel there is a better way to do this. Is this best acheived via a temporary table which is populated by Flow A and on which a schedule flow runs?
Hello @AndyC.64975 (Customer),
Thanks for posting.
Usually, this is caused by missing attributes. Required are first name, last name, email address, UPN, login name, etc.
Please take a look at this article:
https://support.okta.com/help/s/article/AD-user-is-not-imported-into-Okta?language=en_US
See also: https://help.okta.com/en/prod/Content/Topics/Directory/Directory_AD_Field_Mappings.htm
Please let us know if this helps.
Regards,
Natalia
Okta Inc.
Andrew,
Assuming the the data in flow "a" (from the group add hook event) is the same input data for b,c,d etc flows you may want to restructure your flows to be "helpers" of flow "a". Flow "a" gets the input. As it performs / completes its actions it can call the helper flows and pass the data they require. This will allow you contiguous movement from step to step in a controlled and repeatable manner.
I would go with the solution that Tim LaBorn mentioned but your idea of a Workflow Table would work as well.
Something to keep in mind when dealing with Okta event triggered Workflows like "user added to group", Okta told me that each one impacts API usage limits. Having one main Workflow that watches for all of a given event type that then calls child Workflows is a way to lower API usage and may help avoid hitting limits. I've been thinking about suggesting Okta force all their event trigger actions be set up more like inline hooks. With inline hooks you identify what apps you want it applied to and my idea would be that for each event trigger you could identify one or many Child Workflows so development is forced to use the best practice.
Thanks, I wasn't aware of the usuage limit. So you call the child workflows based of the group being added. How do you go about this? - i am thinking of If Else cards but that would get unweidy.
I'll look into the Helper Flows. The data are the same
Create a parent Workflow that watches for all user assigned to any group and then make "async" calls to each child flow. Either have if statements in the parent to limit the calls to each child based on a given group id/name or just send each request to each child and have a "continue if" card first thing in each child to evaluates for a specific group.
Here is an example of how my parent card is set up and calls the first child. I'm blindly sending each request to the child regardless of the group but for subsequent child calls that I'm not showing, I do restrict what ones I pass to the child based on "if" statements. Passing each record to each child does not impact limits so whichever you choose is fine or do a mix like I'm doing.
Might be nice if these sorts of Okta Event Cards worked like Inline Hooks where you just assign them to child workflows like Hooks are assign to specific apps.
That's really helpful. Thank you Matthew