Includes DB changes you need to log all terminals out during upgrade

Not yet released. In a few days to a week

C9 Locks

This version includes significant changes to how locks are managed. The expectation is the dreaded 'deal Y is locked on terminal X messages' when in fact the terminal hasn't locked the deal should all but disappear.

The previous system relied on robust network connectivity between terminals and servers; as 'locks' were linked to the connection. If anything interfered with connection such as computers falling off network in a way the server didn't detect the disconnect then locks would stay in place until you restarted server.

The new architecture is functionally the same but is alot more resilient with network issues.  In event of a stuck/stale lock it will only remain stuck for 5 minutes; after which the new terimal will gain the lock. If the prior computer which held the lock somehow gets unstuck (.e.g. the computer was just in sleep mode), c9 will see that the lock was taken by some other terminal and will force the c9 to close.

Expectation is that this architecture will be alot more resilient and much less disruptive in handling edge cases and hardware niggles around deals and job cards. Network issues will not trigger perma-locks which can only be cleared with a database restart. The new behaviour of killing stale c9s which woke up to found their locks where taken is anticipated to be both rare and minimally disruptive.

PayDay Super

Some ongoing refinements and fixes

• Certain system or network errors could permanently locks a stream upload in c9 as finished but failed. Some refinements here
  • wait for 5 consequetive system errors before flagging a payday upload as perma failed
  • Add a button : force refresh to allow a finished payday upload to forcefully reevaluate payday super result
• Manual payday : was not working as expected. Was not correctly detecting payment due and advising operator and instead was flagging as an error. Now fixed.
• pending payday block backup verify. Still wasn't 100% fixed and was still pausing backup verify. Hopefully now is sorted.

 

Other Tweaks and fixes

Low level changes

• Messenger location is no longer sensitive to primary /secondary terminal installation when 'Restrict messenger setting is in play'. In this case check the messenger setting to assess whether or not to wake up messenger on a given terminal.