This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Workflow to add new user to a group based on department - what am I missing?

Hi,

 

 I'm relatively new to ARS (We're running 7.0 in our env). I've been tasked to create / test some workflows based on new user creation. One that I'm attempting to create now is departmental.

 

 

I've created a "change workflow" with the following parameters - 

Workflow options and start conditions:

Operation that starts this workflow: Create

Target object type: User

Initiation Conditions - 

Any User / Container is "Active Directory"

 

Filtering Conditions -

 

Department of Workflow Target equals "test-department"

 

I've dragged the "Add object to groups" activity and set the appropriate group in the "Groups" tab within that activity (global group, does not require approval from owner). The activity target is set to "workflow target". 

 

Doesn't look like I've got any errors (no exclamation points).

 

I've attempted to create a few users, specifically setting the department during created to the "test-department" - however, once the user is created, they are not being added to the group. 

 

What am I missing?

 

 

Thanks,

 

 

Jim

Parents
  • Presumably, when you configured the add-member-to-group activity, you specified your target group?

    Thinking ahead - this is going to be a bit trickier for more than just your test group as you are going to have to calculate the name of the target group based on the department name. Not difficult - just something to think about as you go forward with your implementation.

    I like Terrence's suggestion of Group Family as they are not as processor-intensive as Dynamic Groups.

    There is yet another option and this is group membership auto provisioning in user provisioning policies. This could work well IF your OU structure is divided up by department, if not, perhaps not as practical.
Reply
  • Presumably, when you configured the add-member-to-group activity, you specified your target group?

    Thinking ahead - this is going to be a bit trickier for more than just your test group as you are going to have to calculate the name of the target group based on the department name. Not difficult - just something to think about as you go forward with your implementation.

    I like Terrence's suggestion of Group Family as they are not as processor-intensive as Dynamic Groups.

    There is yet another option and this is group membership auto provisioning in user provisioning policies. This could work well IF your OU structure is divided up by department, if not, perhaps not as practical.
Children
No Data