I tried putting $SERVERTIMESTAMP$ into one of the text fields, and it basically comes back with the same value as $TIMESTAMP$. The catch there is that pushing the value for $SERVERTIMESTAMP$ into a text field resulted in the time based in BST, not GMT - and our systems stick in GMT, we just don't bother with BST.
Which is strange .... Ran through some more on test, looking at the escalations log for the first and last records matching the criteria. First : Create Time : 10:29:30 $TIMESTAMP$ : 10:25:40 $SERVERTIMESTAMP$ : 11:25:40 Last Create Date : 11:02:05 $TIMESTAMP$ : 10:25:40 $SERVERTIMESTAMP$ : 11:25:40 So the create date is the actual transaction time, but unsure what $TIMESTAMP$ is actually representing. Its not the time when the escalation started (if it were, then the first records create date and timestamp values would be closer), and it seems unlikely that the database (Oracle 10/Solaris) will take 4 minutes to push through a transaction. I think that the escalations process identifies the records matching its criteria in advance, then runs through them - not quite the behaviour I was expecting. I've tried "deferring" the process - putting the processing into a filter, and triggering that from the escalation, but it seems to make no difference in the times presented. Trying to figure out how escalations actually work is quite a challenge. On 7 June 2011 16:30, Grooms, Frederick W <[email protected]> wrote: > I believe $TIMESTAMP$ is the transaction start time (which on large > escalations can be off as the transaction grows) > > Change over to using $SERVERTIMESTAMP$ (which should be the current date > and time from the server) > > Fred > > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > [email protected]] On Behalf Of [email protected] > Sent: Tuesday, June 07, 2011 9:58 AM > To: [email protected] > Subject: Escalations - question over create time and timestamps > > I have an escalation that is almost working fine, but appears to be > generating some inconsistent date/time values. > > Within the escalation, it has a push fields creating an audit record of an > sla failure, and putting $timestamp$ in an event date time field. > > The problem appears to be that the system generated create date, that i > would normally assume to be close to the timestamp value, very definitely > isn't. We're seeing some large discrepancies. > > For example : > create date 6/6/2011 at 19.23:29 > timestamp 6/6/2011 at 19.12:55 > > any suggestions as to what could be causing such a large discrepancy in > what should be identical values? > > > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
