JacksonK.52224 (Customer) asked a question.
Hi, does anyone have a tip for a workflow I'm trying to accomplish?
I'm trying to create a simple workflow:
When a new user is actrivated, I want Okta to be able to read the "organization" I entered for the new user, and then assign them to the (1) appropriate group automatically.
I'm trying to piece it all together in a flow, I thought I would created a table that has the Organization that should tie with the group assignment I want to put people in:
And then this is my workflow, I tried my best to take what I learned from the template "Manage Group Membership based on Profile Attributes," and make it my own, just some I thought would be a simple workflow.
I'm kind of out of my depth, and the workflow won't work when I activate a test account. Am I missing something or doing something wrong?
Hello,
There are a bunch of reasons this flow will not work. I will go over them from left to right explaining each card.
#1 - This card is going to receive an event hook payload each time a user is activated. Assuming the "ID" value is gathered from the "Okta User" section then this card is being used properly
#2 Read User will allow you to pull down custom attributes. Since Event Hook payloads will likely not have the attribute you need this is the correct method.
#3 Searching rows has a filter. You directly dragged the output "organization" into the filter field. It isn't actually trying to match anything. You need to click on filter which will give you a field allowing you to indicate "Which column" (the evaluation such as Equals) "The dynamic dragged in value for Organization" When set correctly it would look something like this: { "organization" = "Organization" }
Next, You are returning "ALL" rows which means the result is going to be an (array/list) even if it only ever returns one row. Any time you are dealing with a list you will need to pass it down to a helper flow to process EACH item in the list. (Typically using a For Each card)
Finally, your table should have the GroupID values. Lookup organization, return the groupID. Since "Assigning users to groups" requires the userID and GroupID. You have the UserID from the first card but the GroupID isn't anywhere in your flow or table.
#4 Everything from this card to the right just isn't going to work based on your setup.
Instead you should create a Helper flow that has 2 inputs. One will be a "Dynamic" input to process each item in the table results. The second will be a static input to contain the UserID from the first card.
Helper Flow:
In the Helper flow you would take the GroupID and the UserID and add the user to the group.
Here are screenshot examples: