I reviewed the technical bulleting as it relates to Remedy ARS 6.1 and
DST.
I read the following "defects":
* SW00256859 -Web services do not recognize the new DST schedule.
If any date related data that occurs between the "old" DST window and
the "new" DST window (for example, between March 11 and April 1, 2007
and between October 28 and November 4, 2007) is processed through web
services, the time will be off by 1 hour.
* Comment- Adjust workflow accordingly?
* SW00256860 Exporting an application (including data) does not
save new 2007 DST date/time values correctly. If any date-related data
that occurs between the "old" DST window and the "new" DST window is
exported as part of an application, then imported, the time will be off
by 1 hour.
* Comment - N/A
* SW00256085 "Server Time" in BMC Remedy Administrator on the
Server Information tab shows a one-hour difference between DST 2007
Start and End date.
* Comment - Not concerned about this.
* SW00256266 BMC Remedy User shows a one-hour difference in time
for date and time fields if the time zone locale is set through the BMC
Remedy User Preference form and if an operating-system-level DST patch
is installed on the system. Workaround: Users should use the BMC Remedy
User
* Comment - N/A-
Since there is no patch for ARS 6.1, our current server version, we
would need to upgrade to 6.3 patch 20. This is a time/resource issue for
us at the moment. Am I missing something or can we not just manually
adjust workflow to match the server time? Can't I offset business time?
Can we not build workarounds in time-based workflow affected by DST
until we have the time to upgrade? What are the caveats and/or what am I
missing if we choose not to patch for DST?
Thanks,
Richard
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
