| Id: | 17807 |
| Product: | finPOWER Connect |
| Type: | FIX |
| Version: | 3.03.05 |
| Opened: | 28/01/2021 |
| Closed: | 28/01/2021 |
| Released: | 25/02/2021 |
| Job: | J025852 |
 High Importance |
|
Business Layer; finAccountLog and other Log objects; Do not validate that an Action Time Zone is specified
When saving an Account Log and an Action Date is set but the Action Time Zone had been cleared, no save error was occurring.
This was different behaviour to the finAccountApp, finClientLog object which would fail to save with a "Action Time Zone not specified." error.
This was not typically an issue in the User Interface since, even though the Time Zone was not displayed, it was still set correctly (i.e., not blanked) on the business layer objects.
The following Log objects would have caused errors if the Time Zone was blank (for the Log, Action and Publish dates):
- finAccountLog
- finUserLog
- finSecurityStmtLog
- finSecurityStmtItemLog
To prevent breaking any existing code by enforcing these checks when saving a Log record, the Time Zones will instead by defaulted if they are blank at the point at which the record is saved.