Please also refer to the section on Enterprise for other relevant new and updated features in v12 for an Enterprise database configuration.
Warn users if their client time zone does not match from the connected database
As Impact does not yet store internal date/times for database records as Coordinated Universal Time (UTC) values, all Impact clients connected to the same database should be located within the same time zone as the database, and each other. If Impact clients need to routinely operate from a different time zone, a separate database would be required to avoid record synchronisation conflicts and any confusion.
However, as it’s not uncommon for Impact clients to connect to a database remotely, e.g. via VPN, there is always a risk that this rule may be forgotten. We have therefore introduced a new mechanism to warn users if their client’s current time zone does not match the time zone configured in the database installation option.
