Michelle, Thanks, and yes there are other criteria. I was just trying to confirm my understanding of Status-History fields. You know everything is moving along well; then smack, something you thought should have worked, didn't. I thought the status-history.*.TIME values would be stored as seconds just like $TIMESTAMP$, and would thus be available for calculation. But if that value is in a different table (H?), then...
rp Lucero, Michelle - IST contractor wrote: > Hi, Rick: > > It's better to perform the operation on the timestamp keyword then the > actual field value. Try this. > > 'Status' >="Closed" AND 'Status-History.Closed.TIME' <= ($TIMESTAMP$ - > (7*86400)) > > Hopefully there's some other criteria or some flag that's being set. > As, this will return all closed tickets older than 7 days, every time > the escalation is run. > > Hope this helps. > > Michelle > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of Rick Phillips > Sent: Friday, August 25, 2006 7:43 PM > To: arslist@ARSLIST.ORG > Subject: Status-History values and general operations... > > ARS 5.1.2 > HD 5.5 > Ora 9i > > I need an escalation to fire when a ticket has been closed for 7 days. > But when I compare $TIMESTAMP$ > Status-History.Closed.TIME + > 60*60*24*7 , I find errors in my escalation and arerror.log. Is it > possible to perform operations against Status-History.*.* values? > (apparently not!) > > rp > > ________________________________________________________________________ > _______ > UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
