Wilson,

What component are you using to try an map the manager?

So baiscally the Manger info is another array of data.  I don't think it works when you are using the Create user component (At least it's never worked for me).

In AD, the Manager field is simply the DN (DistinguishedName) in AD of the user's manager.  So if you know the Manager's DN, you can use the Additional Attributes to specify it, or you can use the Assign Manager to User Component. For that component, you only need the samAccoutName of the user.

rob

I have added an Assign Manager component to my workflow and hard wired the managers name on the Input tabs "Manager Name" but its not adding the mangers name(not Found) to the Active Directory for the new user.

What name are putting in there?

I am looking to create a new hire process as well. The example on workflow swat is out of date and for the 6.5 workflow with HD 6. Would you mind sharing an image or some examples of what you are creating? Are you doing any parallel processes?

Hi Chris,

So our new hire process is a bit more complicated in that we don't own the process from end to end. Our recruitment and new hire process starts in our HR system, which is a hosted Oracle application . They have created a table for us to read from containing all the needed new hire information.

We take that data, and create a WF process from it, which sends the new hire's manager an email with a link to a WF asking for information about the new guy, specifically what type of computer he needs, where he's going to sit, etc... Once the manager completes that form, it spawns tickets in the HelpDesk to the appropriate groups. Once those groups have completed their actions, the WF process moves on and notifies the Manager the new hire is complete etc...

Separate from that, we have an Active Directory Update process that updates employee information with data from the HR system. In our company, we each have a unique employee ID - which we populate into AD. Every update from then on is keyed to that ID, so a person can change names (like marriage or divorce, sex change, whatever) and we won't really have to modify our process. We've decided the only 2 items that are AUTHORITATIVE in our AD are the login name (samaccount and UPN), and the email address (since that is where we host Exchange). For all other data, we assume that the HR system has the authoritative data (correct name spelling, office location, phone, Manager info, Department, title, etc…). A user updates their information in the HR system, which then feeds into AD. We in turn feed the HR system with the users valid email address (we generate a file with 2 fields, EmployeeID and email) and they update that into the HR system.

We also have an auto-email process that ties into the new hire process. When a new hire is created in AD, and an email account is established, the auto process detects this and sends a series of introductory emails to the mailbox (Welcome to the company, Compliance and Ethics, How to's, etc). 

All these processes encompass some portion of the new hire process. It's an ever evolving thing as more and more groups within the company get on board with this unified system.

If you'd like some more into, feel free to contact me!

rob
 

What ADUserInfo Property should be passed as inputs to the User Name and Manager Name parameters in the Assign Manager to User component? I see mention of a property "samAccountName" but I do not see this listed as an option when expanding my ADUserInfo Variables. I have tried CommonName, LoginName, DistinguishedName, and DisplayName to no avail.

Did not like the terminology used by Microsoft!

The samAccountName in workflow is: UserLogonNamePreWindows2000

The UPN (Universal Principal Name) is: UserLogonName

rob