It seems to me that this would be one of those great times to make your escalations multi-threaded in the ways of Lenny Warren. That way it only fires once and the escalation table only has a handful of records to traverse. Of course, you can kill your system if you aren't cognizant of how many records you might be updating.
Create a form for escalations. A record for each escalation that maintains the rules for when they fire and identifying information. One escalation that runs against the table and updates the escalation record that is due. A filter for each old escalation that updates all the records as the escalation would. This would allow you to modify all matching records at one time. This would cut down on the amount of records that need to walked each time the escalations run. As well as allowing the escalations to run more quickly. Just another way to look at it. Brian Goralczyk Phone 574-643-1144 Email [email protected] On Wed, Dec 3, 2014 at 12:27 PM, Grooms, Frederick W < [email protected]> wrote: > One thing to note is that TIMESTAMP (in Filters and Escalations) is the > start of the transaction, not the current time. Normally this is not an > issue except when a process takes a long time (or an escalation has a large > number of records to go thru). > > You might want to consider changing it to SERVERTIMESTAMP > > Fred > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > [email protected]] On Behalf Of ddussie > Sent: Wednesday, December 03, 2014 10:35 AM > To: [email protected] > Subject: Re: Filters actions are firing wierd or correctly .. > > That is correct. > > This business time is adding 1 minute (so technically timestamp could have > been used), this time is being used by the escalation that runs every 4 > mins, that then sets that time field to null. I will change to Business > time2 or timestamp. > > Agree also, this loop was not being closed; which i have rewritten and is > now closed. > > But why all of a sudden this is working as written (looping) which is > incorrect but working. > > This is happen sporadically with other filters in the environment, so a > things go berserk, I rewrite. > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
