Skip to main content

What is the most efficient means of assigning a task to someone based on their job description in AD, as opposed to the actual person?  In other words:

I do not want to hard-code anyone into a workflow.  For instance, the CFO and CEO dictate that they see every position authorization request.  I want the notification to be sent to the AD attribute "job description", so that when one or the other person in the role is no longer there, it will go to the new CIO and CFO.

OK, more than a few words, and the objective is low/no maintenance.

The original issue was that the action LDAP Query was not returning a person's name based on their job title.  The property name has to be exactly as the AD user attribute LDAP naming convention dictates.  It sounds simple enough, but there are false clues.  For instance, in AD Users and Computers when looking at the properties of a user, the label 'Job Title' equates to 'title'.

This is hugely important, and my thanks go to Justin Tang, of Nintex support fame.

For a list of attributes: http://www.kouti.com/tables/userattributes.htm


Reply