I agree. It is a deal breaker without it.
Best regards, Rich �x �x 你 。 GIS-ISS-SEM Service Technology Development Manager ITIL Practisioner Certified: Support and Restore Princeton, NJ (: 609-580-5802 Cell (: 617-756-4626 Information Classification: Limited Access From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Robert Molenda Sent: Saturday, July 24, 2010 10:19 AM To: [email protected] Subject: Re: Statement of Direction regarding EOL of Remedy User client has been amended. ** Just my 2 cents here - yes "Copy to New" is "Broken in ITSM" - create a P1 ticket with BMC on the errors - per module... The CNTL-T function is utilized A BUNCH for other reasons... Robert On Sat, Jul 24, 2010 at 4:29 AM, Kelly Deaver <[email protected]> wrote: ** Please DON'T add copy to new as an AR enhancement. With the way hidden fields work in ITSM, it is an evil we fight daily. I end up with all kinds of bad results from people using copy to new on Incident and People records. The applications should have a standard copy to new function like the one implemented in Change to assure that the RIGHT fields get copied to new! Also, the ability to restrict who can create a macro would be helpful along the same line. We have problems with the average Joe creating a macro that ends up doing bad mojo when run. Macro should be a programmers tool, not an end user tool in this day and time. The apps and AR have much more elegant ways to do the things that macro users once had to do on their own. Kelly Deaver L-3 Stratis / FAA Contractor [email protected] (ARSlist mail) [email protected] (Business mail) -------- Original Message -------- Subject: Re: Statement of Direction regarding EOL of Remedy User client has been amended. From: David Sanders <[email protected]> Date: Fri, July 23, 2010 10:46 am To: [email protected] ** Hi Shawn The Copy-to-New functionality is not intelligent �C it does not know what fields you may or may not need clearing out to avoid problems with your application data. However, it is easy to add this intelligence by creating an active link that fires on the event Copy-to-New for each form that sets the appropriate fields to $NULL$. If these active links do not exist in the application you are using, you should put in an enhancement request. Regards David Sanders Solution Architect Enterprise Service Suite @ Work ========================== tel +44 1494 468980 mobile +44 7710 377761 email [email protected] <mailto:[email protected]> web http://www.westoverconsulting.co.uk <http://www.westoverconsulting.co.uk/> ________________________________ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Pierson, Shawn Sent: Friday, July 23, 2010 3:57 PM To: [email protected] Subject: Re: Statement of Direction regarding EOL of Remedy User client has been amended. David, I’m aware of that, however, the last time I tried to use Copy to New on something like an Incident from the Windows User Tool, it copied over some fields that it shouldn’t have (I think a GUID or something) and it didn’t work. It’s been a while since I tried that, but at least it didn’t used to work consistently for ITSM. I think that’s why the “Copy Change” item exists in Change Management as well. Thanks, Shawn Pierson Remedy Developer | Southern Union _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ -- _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
