1 of 1 people found this helpful
other might have a better Idea, but I would think of a bespoke web service who handles the communication with AD.
This web service then can be called by your action to send the user details and receive the nessary data back from the AD.
Another way could be the use of a bespoke calculation.
Calculations can use .NET libraries including Using System.DirectoryServices to Search the Active Directory .
Please see Calculation Writing Tutorial - 5. Boo language features versus .NET classes on how to use different classes of .NET in your calculations.
The Alternative would be to import the data into SD and use the data directly (e.g. reference pointing to the approver).
This would be the easier way to set up, but as the data is been static in SD and only updated in intervals, it is not actually real time.
Thanks you for the information. I just have a small confusion regarding the tool which i shall use to call the web service. Right now what i cannot figure out is how to call the web service on Action. Is there any specific method or tool to perform the same.
SD can call any web Service which is using SOAP and is based on .NET.
See https://help.landesk.com/docs/help/en_US/LDSD/10.0/Default.htm#../Subsystems/Designer/Content/Object Designer/LinkingToWebServices.htm for details the Web Service Behaviour.
The web service you call from SD needs to be provided by you if you choose to go down this route.