I've done this a few times when AD is up to date and is the source or some other identity management data set. This has a manager field in it so for each person you know who their manager is. There is a bit of faffing about with SQL to turn the value that AD uses to store someones manager into a LANDESK user, but once done you can then refer to someones manager in calculations, in assignments and reminders etc. In a couple of cases we also used this to refer to a managers, manager. It does require AD to be up to date or for you to do this manually (which will probably never happen). What out for data areas where someones manager isn't filled in or it out of date. Here the process needs to take care of exceptions and pass the information to someone to handle those manually.
↧