CasparCloud Release Notes 17-04-2023 Hot Fix

CasparCloud Release Notes 17-04-2023 Hot Fix


    

RELEASE NOTES


                        

Release Date: 17th April 2023

Frontend: 1.6.8

Backend: 1.6.27



FIXES 

[DB-203] Unbatched Postings – Error where no bank transactions are present 

Customers who manually reconciled client accounts rather than using bank files may have experienced an issue when attempting to save an unbatched posting. Although the unbatched posting was successfully saved, the error message that appeared during the process prevented the Add New Unbatched Posting popup from closing. This issue has now been resolved and the error message has been corrected.


[DB-204] Map sort code and client name to an uploaded transaction during bank account matching

Under specific circumstances some bank files would fail to load, this issue has now been addressed. 




PLANNED FIXES AND IMPROVEMENTS IN THE DEVELOPMENT PIPELINE

The top fixesimprovements for inclusion in future updates to CasparCloud.  


Report Generator - Add the ‘Date Last Reconciled as a reportable field 

Currently, the system does not have the capability to generate a report on the "Date Last Reconciled" because this information is not stored in the database as a reportable field. Instead, the system calculates this information in real-time when a user accesses the "Account Enquiry" page. If the "Date Last Reconciled" field is added to the database, it will enable customers to easily report across all clients to identify when accounts were last reconciled by a user.


OPG Report Start Date (Admin>OPG Reports)

We are aware of an issue where the OPG report start date may be one day less than the client's Final Order Anniversary in certain situations. Our team is working to resolve this issue, and in the meantime, we recommend creating a new report from Client>Reports>OPG Reports as a workaround. This will ensure that the OPG report start date matches the Final Order Anniversary of the client.


Full User – Amend Letter Description 

Currently, Full Users are not able to change the description on Letter History. This issue will be addressed in a future update. Until then, only Super Administrators and Managers have permission to amend the description.


Personal Details – Main Contact Address

Users have requested that the address of a client’s main contact (e.g. carer or family member) be displayed on the main personal details page, this change has been added to the development list and will be included in a future update.




    • Related Articles

    • CasparCloud Release Notes 09-06-2022 Hot Fix

      Release Date: 9th June 2022 Hot Fix ​ [CD-238] Private Contact Merge Fields for New Templates  Fixed: where a system administrator is creating a new letter template in the letter writer there was an issue where the address line 2 was repeated in the ...
    • CasparCloud Release Notes 02-02-2023 - Hotfix

      RELEASE NOTES Release Date: 3rd February 2023 Hot Fix Backend: 1.6.9 Frontend: 1.6.5 HOT FIX [DB-131-] Automatic Reconciliation – Transaction Cancel Fixed: A bug relating to the Cancel function in the Automatic Reconciliation caused transactions to ...
    • CasparCloud Release Notes 27-03-2024 (Hotfix)

      RELEASE NOTES HOTFIX Release Date: 27th March 2024 FIXES [DB-369] Financial Assets – Loading Fix Previously, users encountered an error and the page failed to load correctly when more than 20 financial assets were recorded for a client. This issue ...
    • CasparCloud Release Notes 20-03-2024 (Hotfix)

      RELEASE NOTES HOTFIX Release Date: 20th March 2024 FIXES [DB-367] Mitigation of Duplicate Subnote Saving We've addressed an issue where users with slower internet connections could unintentionally save a Subnote multiple times by double-clicking. To ...
    • CasparCloud Release Notes Hotfix 29-01-2024

      RELEASE NOTES Hotfix Release Date: 29th January 2024 FIXES The Hotfix release addresses the following reported issue following the recent Vue Frontend Update: [DB-343] CasparLaw - Resolution of Deputyship Page Freezing We have addressed an issue ...