Not sure if this helps, but I asked the same question with BMC and here is their answer: My question to them was:
When working in the 6.03.00 Patch 003 user tool, when the user clicks on a Date/Time field, it came up with the current date and current time. Now with 7.0.1 when a user clicks on a Date/Time field, the current date, but the time is 12:00 am. ------------------------------------------- Their response: The difference is for example the problem that can originate from a user making a date change only .... whereby when another user in a different time zone brings up the ticket..... The date itself can change. Take this scenario, I am in EST time zone and modify a ticket at 1:00 AM and only change the date to 07/12 /2007........ That will show as 07/11 at 10:00 PM on PST time zone.... whereas if the default of 12:00 AM is maintained.... the correct date of 07/12 is what would show regardless of time zone. The design changes have been done both ways in different versions with each time getting complaints and arguments being made pro and con. Engineering has determined the current changes as what to stick with going forward. Believe me, this approach is a much better approach and doesn't cause as much confusion and consternation among the user groups.... as the previous design did. ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of ARS List Sent: Thursday, October 04, 2007 3:28 AM To: [email protected] Subject: Re: Calendar Popup - default ** Sorry, Joe, perhaps I didn't clarify the problem correctly. That's not quite what I meant. Basically, what our client wants us to achieve, is that for EVERY date/time field, the calendar widget should default to TIMESTAMP, as opposed to DATE only. I could achieve the same thing by modifying each date/time field in the /Field Properties/Attributes Tab and set the Default Value to $TIMESTAMP$, which would result in the TIMESTAMP being correctly displayed in the calendar widget for each date/time field. But this would also mean that each and every date/time field in our system would then be saved to the DB with a default value set, which is obviously not what we want - for obvious reasons, some date/time fields should remain empty until e.g. certain state transitions have taken place etc. Does that make sense? Vanessa On 04/10/2007, Joe D'Souza <[EMAIL PROTECTED]> wrote: ** In your requirement, you seem to have a tough exception to an easy rule, your rule basically being that you want the timestamp to default to date/time fields on opening the calendar widget, exception being you do not want it for each and every date/time field. It may be possible to modify the widget to display the current CLIENT timestamp on a null date field on opening the calendar widget, but it would be hard to have it NOT to set that value for just certain fields. Might be almost impossible to define that exception for some fields. Setting the SERVER timestamp from a client action would be the next difficult task although this is at least not an impossible one. One way to fetch the current server time, if you do not mind a intermediate processing form, would be to create an entry in that intermediate form, and fetch the create or modify time of that ticket, which would give you the SERVER time. Joe D'Souza -----Original Message----- From: Action Request System discussion list(ARSList) [mailto: [email protected] <mailto:[email protected]> ]On Behalf Of ARS List Sent: Thursday, October 04, 2007 1:17 AM To: [email protected] Subject: Calendar Popup - default ** Hallo Listers, I have a question regarding the calendar popup: Currently, in both the User tool and the Mid-Tier, whenever you click on the calendar facility relating to a DATE/TIME field, the popup defaults to DATE, but the time section at the bottom is set to 00:00:00. Does anyone know if it's possible to make this default to TIMESTAMP instead of DATE, at a server level? I know that it is possible, for each field, to set a default value of TIMESTAMP, which will result in the calendar showing it correctly, but obviously this doesn't quite solve our problem, as it means that we would have to change each individual field in our system. Besides which, obviously not every date field in our application should have a default value. Our application is web-based, so perhaps there is even a CSS setting...? Any ideas..? Thanks, Vanessa *** Our environment: ARS 7.0 Patch 003 Mid-Tier Patch 001 Oracle 10 __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
