• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 62 subscribers
  • Views 4837 views
  • Users 0 members are here
Options
Related
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

How to use a Search Activity for managed or owned resources?

J. Wimmer
over 6 years ago

I'm currently in the midst of building a triggered workflow for accounts that are being deprovisioned. The goal of this workflow is to send a warning email when a user that's being deprovisioned is still listed as the manager of a group, computer, or other object.

The documentation on the activity options isn't clear, so I'm making the assumption that the search activity already knows to search object ownership fields for the object identity passed to the workflow. 

Based on my screenshot below, does anyone have any ideas as to what I'm doing wrong? Observing data from the AR Server event logs, I can confirm that deprovisioing a user calls this workflow. However, the logs also show that the search returns no results (even though I've confirmed that at least one result should be returned.)

 

Screenshot:

Event Log Data:

Workflow activity for searching for objects ("Search" activity) completed.
Activity name: Find objects owned by user
Workflow name: Triggered Workflow - Abandoned Objects
Workflow GUID: fe87eca4-9e18-4f66-945b-26c40a9f11b7
Workflow instance GUID: 5e39fed4-69e8-49fd-92ac-089278cf964c
Operation ID: 1-13603
Operation GUID: f4a4ff7d-b26a-457f-af15-90ae347528b7
Search in: fakedomain.int 
Search filter: (&(&(managedBy=CN=FakeUserCN,OU=FakeLocation,OU=Users,OU=FakeBrandOU,OU=FakeOU,DC=fakedomain,DC=int))(objectClass=*))
Maximum number of objects to return: 100
Number of objects found: 0
Elapsed time (seconds): 0
Initiator: FAKEDOMAIN\FAKEUSER 
Activity run as: Administration Service (internal connection)

Parents
  • 0 over 6 years ago
    I'm working on this in my lab, and having some issues with obtaining results from these searches as well.

    A simple workaround for Users who are managers is possible: you don't need the search activity. Simply set a filter on the Workflow Options and Start Conditions so that the Workflow is triggered when a deprovioned User account has a managedObject attribute value which is not empty.

    A similar workaround does not exist for Secondary Owners, unfortunately, at least out of the box. You could create a virtual attribute which contained the DN of a resource managed as a secondary owner, and keep it updated using a Workflow, and then trigger off of that.
Reply
  • 0 over 6 years ago
    I'm working on this in my lab, and having some issues with obtaining results from these searches as well.

    A simple workaround for Users who are managers is possible: you don't need the search activity. Simply set a filter on the Workflow Options and Start Conditions so that the Workflow is triggered when a deprovioned User account has a managedObject attribute value which is not empty.

    A similar workaround does not exist for Secondary Owners, unfortunately, at least out of the box. You could create a virtual attribute which contained the DN of a resource managed as a secondary owner, and keep it updated using a Workflow, and then trigger off of that.
Children
No Data