YUP One filter, only on submit, no run if (always runs), and only the one set-field(s) action. Nothing else updates this field in the workflow. (it is 'read' from but not during submit)
>From the original post incase it got lost in the 'timestamp' thread :) >> I am wondering if someone else has stumbled across this issue. On a form, we created a "Create Date Copy" field and on Submit (no run-if) a Filter will simply do a "Set Fields = $TIMESTAMP$" to this field. This was done as a test to see how long the filters took to run, and was never removed. As you might expect, normally there is only a 0 or 1 second difference between the core field and this copy. However since 2003 (that would be ARS 4.5) through today (and we're on 6.3, with 5.1.2 in between) intermittently, this "Create Date Copy" value will differ by HOURS. The majority of time in the past (Create Date Copy < Create Date) but also a few in the future (Create Date Copy > Create Date) They are always HOURS (plus or minus one second, but that is close enough for me to say hour) and never anything else odd. (like 30 minutes, etc) Over the years we only have 252 entries that have this condition out of 966538 tickets, but it is very confusing. << So statically speaking that is akin to the "needle in the haystack" so to say... How we "stumbled" across this issue, is that very intermittently, our OLA / SLA calculations are completely wrong. Looking at the data and running the calculations that should have happened again, results in correct data! Again this is normally by an even amount of HOURS. Since all of the OLA / SLA filters use $TIMESTAMP$ it makes me really start to wonder. The type of wonder that puts a knot in the stomach.. Thanks again for everyone's input!!! This is what this list is for :) Thanks-n-advance; HDT Platform Incident / Problem Manager & Architect Robert Molenda IT OS PA Tel: +1 408 501 6310 Fax: +1 408 501 2410 Mobile: +1 408 472 8097 [EMAIL PROTECTED] Quality begins with your actions. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black Sent: Thursday, September 28, 2006 10:14 AM To: [email protected] Subject: Re: Server - Timestamp Issues generating random values Robert, RE: " > There are differences of up to 16 hours in these timestamps (system created -create_date- versus our set-fields of TIMESTAMP) so that would be a bunch of timeouts! " So your saying that you have a Date/Time field that is only set via a filter set field action to a value of $ TIMESTAMP $ and that during a single submit action that records 'Create Date' and this other field end up being HOURS apart? That seems very, very wrong to me. I have no explanation for how that might even be possible other than a BUG. I doubt that Filter Looping could be slow enough to not reach a configured max filter or max filter depth in 16 hours. Or are these TIMESTAMP values supplied by the client? Could it be that you have some Clients out there that are configured to be in a strange Time Zone? Are there any consistency about the $USER$ values for the records that are off by hours? -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
