Rick,

On this new form you created, add a field called Escalation Name, and have a 
Status values of Active and Inactive.

This way, on your escalation, you can run it against this form where 
'Escalation Name' = "Name of the current escalation" AND 'Status' = "Active"

This allows you to use the form for multiple escalations in the future, and it 
also allows you to easily turn the escalation on and off without having to 
modify the escalation itself.

Thanks,

Gary Opela, Jr., RSP
Remedy Engineer
Leader Communications, Inc.
http://www.5pointleader.com
http://www.lcibest.com
Best Product, Best People, Best PriceTM
An ISO 9001:2000 Certified, CMMI(r) Level 3 Rated Company
________________________________
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] 
On Behalf Of Rick Cook
Sent: Friday, May 30, 2008 1:49 PM
To: [email protected]
Subject: Re: Application-Delete-Query-Entry gives errors

** RESOLVED.  Thanks to all who contributed to my now-enhanced knowledge level.

OK, here is what I've done to resolve this.

I created a small form with just the core fields, and created one record in 
that form.

I then restructured my escalation to go against that one-record form, running 
the Application-Query-Delete-Entry "SHR:NotificationMessages" ('Status' = 
"Sent") from there.

The escalation ran one time, and took 2.5 minutes to delete 62k records.  No 
302 errors.  Yay!

Rick
On Fri, May 30, 2008 at 10:17 AM, Misi Mladoniczky <[EMAIL 
PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote:
Hi,

Does your escalation run on SHR:TmpMessages?

I would run it on some "scheduler" form, and it should trigger once (one
record).

The normal way to find out what the problem is would be to turn on logging.

What happens when you try to delete one record from the user tool?

       Best Regards - Misi, RRR AB, http://www.rrr.se

Products from RRR Scandinavia:
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
* RRR|Translator - Manage and automate your language translations.
Find these products, and many free tools and utilities, at http://rrr.se.

> We are running an escalation nightly that runs this command:
> *Application-Query-Delete-Entry
> "SHR:TmpMessages" (( 'Status' = "Sent") AND ( 'Send Time' !=  $NULL$ ))*.
> The effect is to clear a form that contains records accumulated during the
> day, but which are no longer needed.
>
> Running this creates thousands of entries in the arerror.log file
> (roughly,
> but not exactly, equivalent to the number of records in the form) that say
> this:  *Thu May 29 10:31:45 2008  390603 : Entry does not exist in
> database
> (ARERR 302)*.
>
> There are no errors that show up in the api or sql logs, and the records
> DO
> get deleted.  Any idea why these errors appear?  I'm kinda stumped as to
> where else to look for a cause.
>
> Rick
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at 
> www.arslist.org<http://www.arslist.org>
> Platinum Sponsor: www.rmsportal.com<http://www.rmsportal.com> ARSlist: "Where 
> the Answers Are"
>
> --
> This message was scanned by ESVA and is believed to be clean.
>
>

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at 
www.arslist.org<http://www.arslist.org>
Platinum Sponsor: www.rmsportal.com<http://www.rmsportal.com> ARSlist: "Where 
the Answers Are"

__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___

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

Reply via email to