Comment 5 for bug 1775719

Fix to previously noted error pushed to same branch.

The issue was the login page wants to report when any pending offline transactions exist. However, the new code only initializes the offline transaction and block tables in the offline UI to minimize the speed/load issues noted in bug #1727557.

My solution was to maintain an entry to the object date cache table indicating the time of the most recent offline transaction entry. This data is used on the login page to determine if offline transactions exist, so the staff logging in can be notified.

As a bonus, since we know the last transaction add time, the date of the most recent transaction is now displayed in the login page offline xact alert panel.

When offline transactions are cleared, the last xact date is removed as well.