Re: Remedy enhancements/Customizations best ones for the buck?

[Hardy, Patrick]

** We have a nice little support search feature that has been added to all of our applications that our users love.  Being as we have several applications, 150 distinct support teams, and an enormous CTI structure, finding the correct assignment combination can be daunting.  I'm not sure how others handle this, here's what we did.   We created a display only form with a couple of tables.  There's a selection box to define what kind of search you want to perform, resource (person) or CTI.  It performs a search and displays relative information in a table, from there you can pass the information back to the originating record.  It's helped our level one people a great deal.  If you'd like a def file to look at just let me know. From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Dan Caissie Sent: Thursday, November 09, 2006 8:39 AM To: arslist@ARSLIST.ORG Subject: Remedy enhancements/Customizations best ones for the buck? ** We are planning on doing some more updates and customizing of Remedy 6.3. I would like to know what are the best customizations you have seen that really get the most bang for the buck. I’m trying to get everything I can in this project while I have the chance. Thanks everyone,   Dan Caissie Remedy Administrator / Developer United Natural Foods, Inc   __20060125_______________________This posting was submitted with HTML in it___ This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email. __20060125_______________________This posting was submitted with HTML in it___