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

HEEELLLPP. Getting Added Member from Group Membership change workflow

This is driving me mad!!!

I have a workflow triggered from Group (Operation = Added Member To Group) and will have an equivalent workflow for removal.
I need to be able to identify the user that was added/removed as a member.  The username will be used within the workflow to do a lookup within a script so need to be able to pass through the workflow and also use in notification email.

I cannot see any way of capturing any user attributes within a script or by a search to pass into a script.

If I add an "Add Report Section" activity I can actually select (Logon Name) of Added Member, and see in the Change history workflow that the correct user is captured.  However there is no way of accessing the attribute (that I know of) so I can actually use it.  Added Member is available as a Target Object (alongside Initiator / Activity Target / Workflow Target / Requested Changes / Parameter Object) but not an option in other workflow basic activities or Object Management activities.

Is there a programmatic way to select the Added Member from the workflow within a script activity so that I can do other actions based on the user.  It's annoying that I can select it from the Add Report activity but not from other activities.

I've tried this on ARS7.3.1 in our Dev envt and ARS6.9 in our Live envt.

Parents
  • Targeting the newly added Group Members is not as easy as it should be. If you want to do this in a Workflow, this is what I usually do:

    Drag in a Search operation and configure it like this:

    The "Found Object" will be the newly added Group member.

    Enhancement Request 776463 has been created to possibly change this behaviour in a future version of Active Roles and make this easier to work with.

    Title: HOW TO: Updating Added Member attributes in a Change Workflow

    Solution: 259299

    URL: https://support.oneidentity.com/kb/259299

  • Great suggestion Terrance.

    One thing I would point out to @Phillip about Searches is that within the workflow UI, they are basically "loops" designed to act upon each object returned by the search. So, when placing workflow activity items within the (sometimes difficult to visually delineate) workspace of the Search, remember that those items will fire for each item returned by search individually.

Reply
  • Great suggestion Terrance.

    One thing I would point out to @Phillip about Searches is that within the workflow UI, they are basically "loops" designed to act upon each object returned by the search. So, when placing workflow activity items within the (sometimes difficult to visually delineate) workspace of the Search, remember that those items will fire for each item returned by search individually.

Children
No Data