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

Is it possible to link a workflow to a managed unit so that it only acts on objects in the managed unit?

I have a manged unit that contains users that have not yet been synchronized to the O365 cloud. This based on a query of attributes 'vapso_associationstrguid_mailbox', 'vapso_cloudsyncstatus', 'vapso_cloudupdaterequired' & 'edsvaFirstEmailAddressUpdatedWorkday'. The purpose of the managed unit and Workflow/Script policy is to enable me to update the user's 'mail' attribute to the HR system once the user has been provisioned to the cloud or after a user request to change there email address.

I want to use a workflow (or other means) to inspect this managed unit and do the following:

1 For each user, set the 'edsvaFirstEmailAddress' attribute to the current value of the 'mail' attribute;

2 For each user, set the 'edsvaFirstEmailAddressUpdatedWorkday' to true. This is so that it then drops out of the managed unit.

I can mange the powershell script to carry out steps one and two above.

What I don't know is how I create a workflow and and then link it to the managed unit so that it only touches objects therein.

How do I do that please?

Or is it not possible to link a workflow to a managed unit?

Parents

0 Terrance.Crombie over 5 years ago

It is absolutely possible to scope a Workflow to only affect the results of a Managed Unit.

If it is a Change Workflow, set the "Workflow Options and Start Conditions" so that the Initiator Conditions are set to the "Any User" (or whatever is relevant) in the container of the Managed Unit.

If it is an Automation Workflow, set the Search scope to be the Managed Unit.
Cancel
Up 0 Down

Cancel

Reply

0 Terrance.Crombie over 5 years ago

It is absolutely possible to scope a Workflow to only affect the results of a Managed Unit.

If it is a Change Workflow, set the "Workflow Options and Start Conditions" so that the Initiator Conditions are set to the "Any User" (or whatever is relevant) in the container of the Managed Unit.

If it is an Automation Workflow, set the Search scope to be the Managed Unit.
Cancel
Up 0 Down

Cancel

Children

0 james.huddy_64575 over 5 years ago in reply to Terrance.Crombie

Just had a look and I can see the options that you outline for the Change Workflow re Initiator Conditions focused on a Managed Unit.

I can't see an option to set the Search Scope for an Automation Workflow. Could you detail that please?
Cancel
Up 0 Down

Cancel
0 JohnnyQuest over 5 years ago in reply to james.huddy_64575

I believe what Terrance is referring to is the scope of a search activity that you embed in the workflow itself to find the objects that you wish to process. The results of the search will be presented as a list of distinguished names and can be referenced in a PoSh script thus:

# Assumes Search Activity has been labelled 'MySearchActivity'

$ObjectLIst = $FoundObject("MySearchActivity").get("distinguishedName")

If you are already specifying your MU in your script as I suggested above, this is not required nor is the Search activity itself.
Cancel
Up 0 Down

Cancel
0 Terrance.Crombie over 5 years ago in reply to james.huddy_64575

JohnnyQuest is correct.

An Automation Workflow will need to retrieve an object to perform operations on. This is typically done using a Search Activity. If you drag in a Search Activity, you can set the scope of the search to a Managed Unit.
Cancel
Up 0 Down

Cancel
0 james.huddy_64575 over 5 years ago in reply to Terrance.Crombie

Thanks Terrance and Johnny.
Cancel
Up 0 Down

Cancel

Endpoint Privilege Management

Is it possible to link a workflow to a managed unit so that it only acts on objects in the managed unit?