Skip to main content

All hail the Manager functionality in Nintex Workflow for Office 365.  As with most of you, you're probably excited as I am about this little nugget.  Although there was a work around, using the Query User Profile action, this release now gives us 3 workflow context properties about the initiators manager, that will make life so much easier.  the Query User Profile is still useful, in that you can get the manager of other users, but if you want to deal with the initiators manager, which is most workflows, then these properties are perfect.

 

Here are the three properties:

Manager login name

Manager display name

Manager email address

 

First of all, in order to get this to work, you will need to request your system administrator to grant Nintex Workflow access to the User Profiles (this only needs to be done once per site, then it'll be in effect for all workflows created on the site thereafter - refer to the help for more details).

 

The System Administrator will need to click on the Administration Settings cog at the top right of the workflow designer.

SettingsButton.png

Then, click the Grant Access button:

GrantAccess.png

 

You'll be provided with a Trust pop up and once you trust it, you'll have the ability to use the above properties in your workflow.

 

So where do these properties come in useful?

 

The login and email address can be used for assigning tasks, using the Assign a Task action or the Start of a Task Process action.  If you're looking at building out a Leave Approval process, Expense Claim process, Travel Request... all of these will most likely have some sort of approval in them, and the first round is usually the initiators manager.

 

But what I like to do, is not just assign tasks, but customize the email notification so that it is personalized.

In this case, we'll be using the Manager display name property and the Initiator display name property.

RegExManagerFirstName.png

We're using a Regular Expression action to remove the whitespace and the last group of letters from the Display name, so that we are left with just the first name.  We do the same thing with the Initiators display name property.  I like to design my workflows so that they work and they are easier to maintain.  So I put the two regular expressions in a Parallel Branches action.

 

Now that we have the first names, we can assign a task to the manager.  Adding the Manager email address to a task is easy :

AssignTask.png

Don't forget to click the Insert button.

 

We can also update the Task Title:

TaskTitle.png

Finally, we want to customize the Email itself that goes out to the manager:

EmailNotification.png

Notice how to have started the email with a Hi and the managers first name, and also in the body, we specify who it was that requested the leave request.  Very easy to do, and makes for a better user experience with dealing with task notifications.

 

I've attached the workflow described here, so that you can see how easy it is to work with the new Manager properties.

 

If you have any questions, please add them as comments to this post.

Hey Ian, if you are looking where you want to set it up.. Head to the Exchange admin in the user properties you can set up the managers name for the user.. This then get sync'd by Sharepoint into the User Profile.


Great post re: manger lookup. Would this also work for an instance where you wanted to lookup all managers in someone's reporting structure (i.e. manager, sr. manager, vp, c-level, and so forth)? If so, how would you accomplish that?

Thanks!


Hi Mark,

if you want to go further up the chain, you'd be looking at using the Query User Profile actions.

Assigning a Task to an Office 365 Manager

cheers,

Vadim


Hi Vadim,

Thank you for this response. Is there documentation out there on how to work with “Query User Profile” actions in Nintex WF?

Thank you!

Mark -


Hi Emily,

The url provided posts:

Mark -


Hi Emily.

Thank you. One quick question: is it possible to add a nintex worklow to an existing list that already has a wf that was built using SPD2013? I am trying to do so now but notice that nintex Forms + Worklow are grayed out? Is it not possible to mix SPD worklfows and Nintex worklows on the same list or artifact?

Much appreciated.

Thanks.

Mark -


Thanks for the post Vadim.

Just my opinion, this is a function I recommend not using. Workflows fail (even more in O365 than On-prem ) and if anyone wants to restart the workflow on an item other than the person who created it, this function throws the process out completely.

Always user User Profile Query, using User Email Address of "Created By" not "Initiator login name". You'll need a simple regex before to strip claims details from Account(login) to get just the login email of created by. You can't trust Email address of any user as quite often Primary Email Address is different to Login Email address


Reply