The answer is reverse engineering the xml definitions in order to understand their structure... I have attempted things like that before.. What I do in order to do something like this is export a similar object, and see what its xml definition content would look like. In your case you would need to export filters having an If statement and Escalations.. You would need to see what element in the xml is used to enable or disable an Escalation and the structure of a filter with one If action..
Use that as a basis for your ‘reverse engineering’.. I’ve used this method successfully in instances where there were bugs with the new Dev Studio where it would not allow saving objects that had valid qualifications in the Menu definitions or in the Join form definitions.. There used to be a bug with adding a new active link to existing active link guides too, where the process on the Dev Studio would time out at the time of opening the dialog to add a new active link itself.. Editing these qualifications in the xml def files or the AL Guides in a xml def file and importing them would work around those bugs and allow the save – thus not impairing my ability to proceed with my development effort.. Joe From: Benz, Michael Sent: Tuesday, March 20, 2012 9:31 PM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Subject: Re: Convert multiple escalations to filters for use in a filter guide ** There’s about 500 records through to 2500 records (depending on the OU) so it’s a fairly sizeable operation, but this is for our test system, so long times aren’t an issue (and once everything is in place, the production system will only need to be run once) Modifying the XML of the definition file sounds like a good way, so If anyone’s done this before, examples would be great! Regards, Michael Benz Service Desk Analyst Holcim Australia Shared Services 18 Little Cribb Street, Milton QLD 4064 Phone: +61 7 3364 2752 For any IT Issues, please call 07 3364 2811 www.holcim.com.au From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Joe Martin D'Souza Sent: Wednesday, 21 March 2012 11:09 AM To: arslist@ARSLIST.ORG Subject: Re: Convert multiple escalations to filters for use in a filter guide ** 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"
