In more "complex" applications I disabled it with workflow like you're describing. The problem was always that the copy to new feature would copy status flags to the new request and produce squirrelly results.
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Robert Dalton Sent: Thursday, September 03, 2009 8:37 AM To: [email protected] Subject: Copy to New - Disable or Use - Which do you Prefer? Good Morning List, A have a question which is not specific to any platform or version. Just curious how others handle the "Copy to New" functionality that's been in the client User Tool for many years. Do you prefer to create an active link which fires an error message to prevent people from using the copy to new functionality or do you let people use it??? In previous projects I worked on we always ran the error message preventing people from using it and then we created our own button, menu item, etc which performs an open window action and pushes only the fields we selected over instead. Is this how you are dealing with this -OR- do you have any better ideas??? Thanks, Robert Dalton _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
