Export the Escalations to a definition file and save it as xml (not .def). Edit the contents to disable the Escalations and then use those to create filter objects with new names. This should work.. You would need to look at what an xml definition of a filter would look like in order to do this and then replicate that..
So while this is doable, it may not be entirely supported by BMC Support, in case you do something wrong. So I would choose this option carefully..... Joe From: Shellman, David Sent: Tuesday, March 20, 2012 8:16 PM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Subject: Re: Convert multiple escalations to filters for use in a filter guide ** You could define one escalation that fires and creates a record in a temporary work form. That temporary form would be the trigger to fire the filters. The bigger question is how much data, (number of records) is pulled from AD? There might be a possibility of tying your system up for some time. Dave On Mar 20, 2012, at 6:54 PM, "Benz, Michael" <michael.b...@holcim.com> wrote: ** Hi All Does anyone know of an easy way of converting escalations into filters? I have about 10 escalations that copy information from LDAP into remedy (10 because they are different OU’s in active directory) and for testing purposes, I was going to create a filter guide to push information from LDAP to CTM:People (and my active directory form which sits in between) Thanks Regards, Michael Benz Remedy Programer www.holcim.com.au _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
