If you can express your timezone as an offset from GMT then the calculation is easy: epoch + 3600 * offset
If you start to deal with all the fun nuances that come with timezones expressed as a geographic region it gets much more complicated and Remedy workflow is not a good way to deal with the conversion. See http://www.worldtimezone.com/daylight.html. DST makes this complicated. Java provides classes to deal with this and I would suggest using the filter plugin framework to deal with it in that case. Also, if you want to express the resulting date/time value in a localized format (e.g., m/d/y h:m:s vs. y/d/m h:m:s, etc.) then Remedy workflow is a poor choice for your solution. Go for something that has already done the legwork (e.g., Java). See http://en.wikipedia.org/wiki/Date_format_by_country for possible formats. Axton Grams On Fri, Oct 7, 2011 at 12:49 PM, Christianne <[email protected]> wrote: > Hi Listers, > > Has anybody done timezone conversion before via workflow? I need to convert > a date/time field to specific timezones. > > I've created an integer field that contains this epoch time value: > "1317877200" (Thu, 6 Oct 2011 05:00:00 UTC) > > I'd like to solicit feedback on how to do the conversion of this integer > value (workflow driven manipulations) to display the appropriate timezones > below: > > CST - > GMT +10:00 - Australia, Sydney > GMT +00:00 - Europe/London > > Thanks in advance for your help. > > Regards, > Christianne > > > _______________________________________________________________________________ > 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"
