• Spare Parts
  • View what units a part can fit.  Works for stocked or unstocked items. Is able to query either local fiche diagram database or remote database if you are using the 'get diagrams from other c9 dealers' feature
  • Customer merge orders on pickup. Option under setup to merge all parts on identified orders, not just parts that have been received
•  Workshop
  • Do not send booking reminders for jobs where job is in received state
  • Re-invoice a cancelled pickup job : allow user to backdate the date that the job was previously invoiced to, or to todays date. Defaults to last date that was picked up. Useful for recovering from cancelling the wrong job.
• Contacts
  • Add new contact, system was not clearing contact type (Insurer/finance company?) flag. So on adding new contact it would pickup contact type from last record system was looking at, flipping customer as an account customer. Now fixed
• Business
  • Backdated transactions involving debtor accounts, under some circumstances General Ledger would post on todays date, not backdated date. Now fixed
• Low level Systems
  • Recent inclusion of ability to track which terminals are locking resources has broken ability for c9 to perform online backup verification.  Now fixed

A verification is a process where c9 verifies copy of data in online backup is same as local copy.  Verifications almost never fail because anomalies are rare to non-existent, so backup accuracy is not at any real risk but verification does provide assurance that backups are indeed correct, so is a high priority issue to fix to continue to provide this assurance.  One challenge with verification is that verification data takes a few minutes to prepare, if while verification is running a change to the database occurs, such as raising a new invoice, the verification statistics currently being created may be inaccurate so the verification must be abandoned and rescheduled. Recent changes to track terminals caused verification to fail all the time. The reason why is that verification monitors for any change on the database, not just changes relevant to backup. So changes to recording terminals caused verification to fail, unnecessarily because terminal tracking is not something that needs to be backed up.  Terminal tracking data is updated every few seconds.  Modified backup verification process so it only monitors and fails on changes to things that backup system actually backs up, not any change to the database.