The escalation processes through all the records in the form, and completes it's tasks where a record matches the qualification.
Your timestamp is when the workflow hit that record and populated the time at that moment, and the createdate is when the push was committed to the database. In-between those times, there is the time that other workflow will get triggered and run. For example, turn on logging and push to bmc_computersystem, You will see work flow hit all the classes between it and base_element. The time adds up by the time it's done. Turn on filter and SQL logging just before escalation runs and then off when done. Load the logs and trace through one record. You will see why there is a difference. Brent... Sent from my iPhone On Jun 7, 2011, at 7:58 AM, "[email protected]" <[email protected]> wrote: > 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" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
