CCH Accounts Production 2022.2 Service Pack: Release Notes
Release Highlights
This release of CCH Accounts Production includes the following:
- Changes to saving accounts to PDF or Word
- CLR Strict Security for SQL2019 users
Prerequisites
Installing CCH Accounts Production 2022.2 Service Pack
This release is installed using the Central Suite Installer. This ensures that all prerequisites are in place and that all the products for which you are licenced are installed in the correct sequence. Click here to learn about the Central Suite Installer.
Software Enhancements
CCH Accounts Production
VSTS 242658 - SQL2019 Strict Security
This release is required for users running SQL Server 2019 with the setting made for Strict Security. Strict Security requires that certain programs held within SQL Server are signed by Wolters Kluwer to assure their authenticity. These programs are known as SQL CLR Assemblies. Accounts Production 2022.2 removed Accounts Production SQL CLR Assemblies from 2022.2. This Service Pack removes them from all earlier upgrades, ensuring that if a user does upgrade from an earlier version of Accounts Production to 2022.2 Service Pack, the upgrade will be able to run through. Other applications such as Corporation Tax still use SQL CLR Assemblies. So it is important to follow the CSI instructions that include signing the SQL CLR Assemblies for this release.
Quality Improvements
CCH Accounts Production
ADO 241367 - A pound sign in a paragraph could appear as a "<" when a page was being edited
The problem happened when RTF text containing a pound sign, e.g. text copied from a Word document into a Statutory Database paragraph, was accessed in an accounts page using a formula like =AP("#tr3"). When the page was opened for editing, the text could be seen and the pound sign appeared as a "<". The problem was not serious as the page still displayed the pound sign when the accounts were previewed or printed. After the fix it shows the number but without the pound sign on the page.
ADO 243464 - If accounts are saved to Word and a watermark is added, it appears incorrectly
Accounts Production 2022.2 places all the text in textboxes, rather than positioning characters individually. These textboxes by default are white. However some users like to save the accounts to Word and then, in Word, add a Watermark using Design > Watermarks. The watermarks appear but are broken up because the textboxes have a white background. This fix changes the background colour of the textboxes to be transparent to make the watermark show through more clearly. This change was also included in the 2022.2.1 service pack for SQL2019 strict security.
ADO 242658 - When a paragraph is fully justified, sometimes the last line of the paragraph was not left justified when saved to PDF
Even if the paragraph is fully justified, the last line should be left justified. However it was actually appearing fully justified on old paragraphs in the now-unsupported Sole Trader master pack which used a pipe character, "|", to insert line feeds. Also long URLs which were clickable were sometimes not wrapped when required. Both of these issues only appeared when accounts were saved to Word or PDF format.