That makes me think of another possibility. You could potentially have a form with a table on it that points to CTM:People. You could loop over the table and look up each person individually on the AD form. If the person isn't there, you can mark them as Obsolete. That wouldn't be terribly efficient, but it would save you from having to have another copy of the data.
Lyle From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Pierson, Shawn Sent: Friday, May 29, 2009 3:20 PM To: [email protected] Subject: Re: LDAP question ** I built a custom Vendor form on my own so I could pull in some fields that I wanted and leave out others. Anyway, if you set up an escalation or filter to modify People data (I use a filter, with the escalation pushing to a staging form where all the transformation and other filters take place) put something like this in the Run If Criteria: ( 'userAccountControl' = 514) OR ( 'userAccountControl' = 546) OR ( 'userAccountControl' = 65538) OR ( 'userAccountControl' = 66050) At least in my organization, this is sufficient to identify accounts that should be marked Obsolete. Shawn Pierson From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Shane Buchholz Sent: Friday, May 29, 2009 2:05 PM To: [email protected] Subject: LDAP question ** We are trying to configure Remedy to set the Profile Status to "Obsolete" in the CTM:People form when they have been deleted from Active Directory. The most logical approach is to use an escalation that will fire at regular intervals to keep the CTM:People form as up to date as possible, but the limitations of the workflow seem to make this impossible to do. We are using the inetorgperson form to pull data in from AD, and have an escalation that fires and creates new accounts in the CTM:People form. It recognizes new accounts, but we haven't been able to determine how to have it recognize that an account is no longer in AD. Please let me know if this is even possible, and if so what the best approach is. ARS 7.1 ITSM 7.1 SQL Server 2005 Windows Server 2003 Thanks, Shane Buchholz Information Security Specialist Account Services - Information Services ________________________________ Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ Private and confidential as detailed here<http://www.sug.com/disclaimers/default.htm#Mail>. If you cannot access hyperlink, please e-mail sender. _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
