Civil pro version 10.65.1.64 will be released 10/6/19 for selected users. For those on version 10, this will be an automatic update if you are using the web installer by the 17/6/19.

PLEASE NOTE: This update requires a small database update from version 10.64.1.xx. This is a very quick update, but means users who have not updated will not be able to access the database once the update is run. As always, backup first!

As any databases updated to version 10 are permanent, cannot be reverted and are not compatible with version 9, the update is on a different update path and auto updating will not occur between major versions 9 and 10. All subscribers are entitled to version 10 free of charge, just email us for the new download.

Changelog from previous version 10.64.1.51

New features

• Approval numbers are now project specific. Refer to the blog post on Approval numbering is now project specific

Changes/Improvements

• Support multiple ‘Auto CC’ email addresses
• Email processes now wait for completion (async/await) rather than failing to a log.
• Email addresses are ‘deduped’ before adding CC and auto CC. e.g. cc and auto CC will be discarded if the email is already used for an addressee
• Improved logging on email functions in cases of errors
• Claims no longer round to 3 decimal places when compiling effqty from lot quantity
• Project templates (for approvals, responses etc) can now be deleted and renamed.

Bugs

• BUGFIX: Checklist open date was not being set
• BUGFIX: Custom status caused exception on NCR approval request
• BUGFIX: Permissions incorrectly handled in some cases on project data transfer
• BUGFIX: Project statistics had exception on receipts and receipt details
• BUGFIX: Report title incorrect with custom reports
• BUGFIX: Daycost Notes or Docketref causes issue when compacting daycosts for sitediarycost comparison on site diary review.
• BUGFIX: Too many decimal places in schedule item selector since quantity scale change

Since the introduction of the Approval system in version 9, the approval ID has been used for approval numbering. The approval ID is unique across each database, meaning if you have a project that is assigned approval id 1125, another project may well raise the next two IDs (1126 and 1127), and then your next number would be 1128. This works perfectly well, and conceptually there is no need for the approval numbers to be consecutive – just unique. This is why this design decision was made in the first place. It is easier, and technically more robust.

But human beings can be funny creatures, and several users have reported clients who take issue with their approval numbers not being consecutive. Given that this has happened more than once with some users, we have made the decision to implement project specific numbering.

The new behaviour is that each approval will get the next consecutive number in the context of the project, not the database. In the example above, after creating ID 1125, the next number for the project would be 1126, regardless of what other projects in the system were doing. This is more complicated, and more things can go wrong – e.g. what is called a race condition when more than one user on a project needs a new approval number, but this essentially works the same as numbers for NCRs and Test Requests.

How does this affect existing Approval Numbers?

Existing approvals in the system will not be renumbered. The upgrade to v 10.65.xx will copy the existing ID to the new Approval Number field. You should notice no difference.

What happens if I need to change the Number?

In the approval view form, you can invoke the “Allow Editing Protected” option that will allow you to type a new approval number. The only requirement is that the approval number is unique. Be careful though, because if you put a new approval number that is the largest number for the project, then this will be the new starting point for the automatic numbering. E.g. if your largest approval number is 25, and you change a number to be 1000, the next approval number automatically generated will be 1001.

What if I don’t get an approval number?

The system should always give you an approval number automatically. Just in case it doesn’t there is a menu option in the approval view context menu that will only be displayed where the approval number is 0 – Get Approval No.  The most likely use for this function is if you manually change the approval number, but then decide you want to revert to the auto numbering. In this case you can just make the approval number 0, then use this function to get the next approval number.