on Dec 27, 2017Is is possible to dynamically assign a manual fulfillment to an AD group member based on Lightest load first logic ?
This can be achieved by static assignment but I wanted to know if this can be done with a dynamic group name (Workflow variable)
Is is possible to dynamically assign a manual fulfillment to an AD group member based on Lightest load first logic ?
This can be achieved by static assignment but I wanted to know if this can be done with a dynamic group name (Workflow variable)
One possible approach I can think of is to query (SQL) the group members into a workflow variable and then use that variable in the manual fulfillment node configuration
Yes, I have been using this approach to query the group membership but was hoping to use this out of box feature with dynamic groups. This would have been way simpler
Yeah i concur with Boris, I believe you'll have to explode out the group members first, and then use the "lightest load first" option.
Just for future reference, one thing I really like to do in "team fulfillment" cases like this is to actually assign the task to a generic identity, and then use monitoring policies to provide access to the members of the group.
So imagine you have a generic identity (through a small CSV IDC) called: Fulfillment Team, Active Directory.
You'd have this generic identity be the technical owner of the application, and assign the provisioning task as such.
Then what you do is your create a monitoring policy that will provide members of the "domain admins group" (as an exmaple) access to fulfill items assigned to the "Fulfillment Team, Active Directory" identity. This allows workflows to be very simple- since it's a singular assignment- but the work queue is completely dynamic, and as people come and go from the group they are allowed to see/not see the fulfillment tasks.
One possible approach I can think of is to query (SQL) the group members into a workflow variable and then use that variable in the manual fulfillment node configuration