The following describes how to properly handle time zones for date/time fields.
It is important to understand when the mapping engine parses a value configured as date/time, it converts it to a special internal date format that looks like this:
This internal format does not contain a timezone offset. The implied timezone is that of the server on which the atom, molecule, or cloud is running. If the source value and date mask does not contain an offset, the value will be processed assuming the atom server's timezone. However, if the source value and date mask does contain an offset, it will automatically adjust the time value (see table below) for the atom's timezone.
One special example that is fairly common is converting from some timezone to UTC time (0 hour offset). If the source value contains offset information and the source profile element's input mask is configured with the appropriate date mask, the mapping engine can perform this transformation automatically.
The following table demonstrates how date values are converted from source to destination given slightly different date masks. In this example the atom is running on a server configured as Eastern Time.
No offset specified, no adjustment
Pacific to atom time (Eastern), value adjusted
Pacific to atom time (Eastern), valued adjusted, common web services format
For more about date formats, see Date/Time data type.