Clients; Web Access; "Test Login" button could lock Client's web access and would update the last login details

Previously when using the "Test Login" button on the "Web Access" page of a Client it was possible to lock the Client's web access which would cause the last login information to be updated. This also meant that after a successful Test Login, the Client's last login date would be updated. This was misleading - as it would look like the Client had logged in when they hadn't.

The "Test Login" button has been updated so that it no longer will lock the Client out of their web access after multiple consecutive failed login attempts. Additionally, the "Test Login" button will no longer commit any details to the database.

In the Business Layer, the finClientFunctions.WebLoginValidate function has been updated with a new optional parameter, testMode. If this parameter is True then the login will be validated and attempted, however nothing will be committed to the database, however note that Audits will still be created if the audit parameter is True). If testMode is False then the login will be fully validated, attempted, and committed to the database.