Hi, When the AR Escalation tries to update the record - there is an error that says the Login ID can only be deleted by members of the Contact Organization Admin or Contact Support Admin group - which is preventing this from modifying the record to LOWERCASE. AR Escalator is Admin. Did you experience this error - perhaps this can be fixed by changing the permission on the login field?. In a message dated 5/14/2008 10:58:03 A.M. Pacific Daylight Time, [EMAIL PROTECTED] writes:
** That is the way I did it, including defaulting some NULL fields that Remedy requires. I have an escalation that pulls the AD data (via a vendor form) into a staging table, which then uses filters to do validations and auto-population of some data, then if it passes all the validations, passes it into the CTM:People form and all the related forms that need populated. It sounds like you already have that, but need to use a LOWER() function in your Push Fields that passes the Remedy Login Name field. Something else that will be useful for you is to set up another filter to find users to automatically disable too. In my filter to do that, I have: (( 'userAccountControl' = 514) OR ( 'userAccountControl' = 546) OR ( 'userAccountControl' = 65538) OR ( 'userAccountControl' = 66050)) The userAccountControl field are set to those values when a person is de-activated, so you can create a filter to set them to “Obsolete” in CTM:People as well as set Support Staff? To No and remove all their permissions. This helps quite a bit in keeping license costs down because you’re not wasting licenses by maintaining them for people that are no longer with the company. Shawn Pierson From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Kathy Morris Sent: Wednesday, May 14, 2008 11:37 AM To: arslist@ARSLIST.ORG Subject: AD and CTM:People ** Hi, AR System: 7.0.1 Thru workflow, data is passed from Active Directory into Remedy vendor tables then thru escalations into Remedy CTM:People. We have users that sometimes enter the field values in upper/lower case. Whenever they enter uppercase/lower case or leave certain fields BLANK, the record does not get into the CTM:People form. I would like to build workflow that changes the case to LOWERCASE and does error-checking on records that come from AD that don't make it into the CTM:People form. Am I approaching this correctly, or is there a better way? ____________________________________ Wondering what's for Dinner Tonight? _Get new twists on family favorites at AOL Food_ (http://food.aol.com/dinner-tonight?NCID=aolfod00030000000001) . __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ 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: www.rmsportal.com ARSlist: "Where the Answers Are" html___ **************Wondering what's for Dinner Tonight? Get new twists on family favorites at AOL Food. (http://food.aol.com/dinner-tonight?NCID=aolfod00030000000001) _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
