We actually have a non production 8.1 env and I was able to reproduce it in there as well. Seems like something not patched yet. When I saved the record, in the database it is stored correctly in the epoch format and the workflow is triggering as normal. Seems like a glitch at display level only.
On Monday, May 6, 2013 12:21:51 PM UTC-5, Longwing, Lj wrote: > > ** > That is hilarious...no, I have NEVER seen this before, but I highly > recommend upgrading to Patch 3 of 8.0 for all components...it may be fixed > in one of the patches. > > > On Mon, May 6, 2013 at 11:09 AM, patchsk <[email protected] > <javascript:>>wrote: > >> ** >> I have a ticket with BMC but thought checking with the arslist as well. >> Has any one seen this kind of Date/Time display issue before? >> We are on ARS 8.0 with midtier 8.0. Seems like the issue is not browser >> dependent. >> We are seeing this consistently for users in a different timezone from >> the ARSServer Timezone. >> Our ARS is in PST and users complaining are from CST and EST. >> Also seems like this is happening only to the last day and last min of >> every month. >> For Ex: >> 5/31/2013 10:00PM will display as 6/0/2013 10:00PM >> 6/30/2013 10:00PM will display as 7/0/2013 10:00PM >> >> Where as 5/31/2013 9:59PM will display as normal. >> This is even before we save the record, just when we select the data/time >> on the screen. >> >> >> >> >> <https://lh6.googleusercontent.com/-p_NPEbNtGEg/UYfe2ZfNUMI/AAAAAAAAFKM/SzGYsH22aIY/s1600/DateTimeDisplayIssue.jpg> >> >> _ARSlist: "Where the Answers Are" and have been for 20 years_ > > > _ARSlist: "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"
