IBM® FileNet® Content Federation Services for Image Services translates dates between FileNet P8 and FileNet Image Services during bidirectional replication. Because FileNet Image Services and FileNet P8 handle dates differently, discrepancies might occur when the FileNet P8 client and FileNet P8 are in different time zones.
For example, the FileNet P8 system is in New York, which is UTC-5 Eastern Standard Time (EST). The FileNet P8 UTC date is converted to the local time zone of the FileNet P8 server and the time part is dropped when it is transferred to FileNet Image Services.
The FileNet Image Services user must be warned that the date of record might be off by one day and must adjust the date to conduct business with California-based FileNet P8 users and customers. This situation applies to all FileNet Image Services users around the world .
The German FileNet P8 user must be warned that either or both date of entry and date of record might be off by one day.
All California FileNet P8 users can be confident that both the date of entry and date of record is accurate.
All other FileNet P8 users run an increasing risk of having either or both of date of entry and date of record off by one day as a measure of the time zone difference between the location of the document originator and their location. In this case, consider standardizing the UTC date and time across the company.
If all the business is conducted in one time zone, it is preferred to set the FileNet P8 clients and servers to that time zone, regardless of the CE/AE server location, so that both FileNet Image Services and FileNet P8 users can be confident that dates are accurate.