I don't remember right but it was fixed in Patch 1497 for 6.0.1 or the one before it.

From: Mike White <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Subject: Re: Archiving Data in Remedy
Date: Mon, 4 Dec 2006 10:08:13 -0500

Hmmmm.  We're running 6.0.1, patch 1497 and didn't have this issue.  I just
double-checked our default values - none were disturbed.  It's an active
archive that's been running for months.

We have other archive issues, but don't seem to have this one.

To paraphrase (for clarity) - you're saying that if you enable archive on a
form, Remedy removes default values on the main/source form.

Mike White
Office:  813-978-2192
E-mail:  [EMAIL PROTECTED]



                      "Lucero, Michelle
- IST contractor" To: [email protected]
                      <Michelle.Lucero@        cc:
MKCORP.COM> Subject: Re: Archiving Data in Remedy
                      Sent by: "Action
                      Request System
                      discussion
                      list(ARSList)"
                      <[EMAIL PROTECTED]
                      ORG>


                      12/04/2006 09:45
                      Please respond to
                      arslist






Much to our surprise that bug also exists in ARS 6.3 at least up to
patch 13.  We're now on patch 18.  Somewhere between 13 and 18 it was
fixed.

Michelle

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of msb *****
Sent: Monday, December 04, 2006 12:13 AM
To: [email protected]
Subject: Re: Archiving Data in Remedy

There is a big bug in ARS 6.0.1 archiving.
As soon as you enable archiving on a form and the archive form is
generated
by ARS, all the default values on all fields of the original form are
blanked out permanently !!!

I think it was fixed in Patch 1491...

Regards,
Murtuza.


>From: Richard Crosby <[EMAIL PROTECTED]>
>Reply-To: [email protected]
>To: [email protected]
>Subject: Re: Archiving Data in Remedy
>Date: Fri, 1 Dec 2006 08:07:53 -0800
>
>To me, the biggest pitfall is that there is only one thread for
>escalations. This is problematic if you use escalations for other
>processes (such as notifications, record clean-up/deletion, etc) that
>fight for an open escalation thread. In this case, proper table
>indexing, archiving/record deletion time staggering and database
>performance tweaks will all help alleviate some pain.
>
>
>
>Thank you,
>
>
>
>Richard Crosby
>
>Starbucks Coffee Company | Information Technology
>
>| [EMAIL PROTECTED] | (206) 318-4614
>
>
>
>One day your ship will come in, but you'll be at the airport.
>
>
>
>
>_______________________________________________________________________
________
>UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
ARSlist:"Where
>the Answers Are"

_________________________________________________________________
Don't just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/

________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where
the Answers Are"

_______________________________________________________________________________

UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where
the Answers Are"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers 
Are"

Reply via email to