RELEASE NOTES

                        

Release Date: 22nd March 2023

Frontend: 1.6.7

Backend: 1.6.23

    

[DB-120,  DB-144 & DB-165] Enforce Two-Factor Authentication (All Users) 

This change is only relevant to customers who do not use Single Sign On (SSO) to log in to CasparCloud. If SSO is used authentication is carried out by your organisation. 

Due to changes in legislation, all cloud providers must ensure that their services are only available by using additional security verification. The change means that all CasparCloud users will be required to use Two-Factor Authentication (2FA) where SSO is not utilised. 

Users who have not enabled 2FA on their CasparCloud account will be presented with the 2FA set-up page each time they log in to the application. This page will display at login until such time as 2FA is enabled.

The grace period for users to enable 2FA is as follows:

2. Existing User: 30 days 
3. New User: 14 days 

The 2FA setup page confirms how many days remain before the grace period expires. Once the expired users will not be able to move past the 2FA setup page and will be prevented from logging in until such time as 2FA is enabled. 

IMPROVEMENTS

[DB-114-13] Report Generator – Selected Data Fields

Previously, users had to manually expand the report tree in the Selected Data Fields section when writing reports using the Report Generator to see the data added to a report. We have now made changes so that the report tree automatically expands when a field is added, making it easier for users to see the report data at a glance. 

[DB-114-14] Report Generator – ‘Entered By’ from Client Transactions 

Previously, the 'Entered By' fields from the Client Transactions table were not available to be added to a report created using the Report Generator. However, we have made updates to allow the inclusion of these fields in reports as needed. This enhancement will provide users with more flexibility and better access to important transaction information.

[DB-145] Notes – Date & Date Created

Now, when adding a new note, the ‘Date’ field will automatically default to the current date. An extra read-only field labelled ‘Date Created’ has also been included in the note popup. This new feature will allow users to view the date a note was created on the system.

Please note,  for customers who have migrated from the on-premise version of Caspar, historic notes will have a ‘Created Date’ equivalent to the date the data was transferred to the cloud.

[DB-152] Statistics Report – Display Records with No Dat Assigned 

The Statistics Report grid view has been updated,  users will now be able to see the number of records that do not have data assigned when filtering by Case Worker, Care Manager, Team, Category, Care Type, and Location. Records without associated data will be identified as N/A.  This new feature will provide users with a clearer understanding of the breakdown of client data available in the grid view.

[DB-163] Diary Export - Add the client name to the Diary Export 

The Diary Excel output has been improved to now include the client name as well as the code, making it easier for users to identify the client associated with a diary task.

[DB-167 – 1, 2, 3, 4]  Automatic Reconciliation - Performance Improvements

We have refactored the code for the Reconcile Bank Transactions page to optimise system performance when switching between green, amber, and red statuses, resulting in significantly faster transaction loading times. Additionally, the improvements made will also enhance the loading time when changing case worker and client filtering, providing an overall better user experience.

FIXES 

[DB-114-15] Report Generator - Filter Issue

Previously, when removing filters from a Report Generator report, the front end displayed the removal of the wrong filter entry, even though the actual filter being removed was correct in the data. We have made an update to address this issue and ensure that users can see the correct filter being removed from the report. 

[DB-138] Automatic Rec. - DWP transactions not grouped in some cases

Some customers experienced an issue where DWP combined transactions were correctly matched to a bank transaction, but the system identified them as "amber". This was due to the database tolerances using different scales. We have addressed this issue for all customers in the current update to prevent it from occurring in the future.

[DB-143] Prepaid Cards - Card Number Validation

Previously, the system would not allow a Prepaid Card record to be saved if a user entered spaces in the 'Card Number' field. However, we have made changes to allow the record to be saved even if spaces are present in the 'Card Number' field. This change will improve user experience and streamline the data entry process. 

[DB-147] Unbatched Postings – Excel Output

The Unbatched Postings Excel report has been updated. Previously, the report would output all unreconciled unbatched transactions. Now, it has been updated to output only the filtered results displayed on the Unbatched Postings screen. 

[DB-148] Document Library – Folder Deletion

The Document Library has been updated to allow Super Admin and Manager users to delete folders if required. Please note that deletion will also include the folder contents where present. 

[DB-149] Fees – User Interface Updates

This update brings several changes to the Fees user interface, aimed at improving usability when calculating fees by a caseworker. These changes include:

1. When the Fees page loads, the ‘Fees’ radio button is now set as the default focus.
2. The case worker's name will now remain selected in the ‘Case Worker’ drop-down when the fees are calculated and confirmed, ensuring users are clear about which case worker’s fees are being worked on.
3. The case worker's 'Confirmed' status in the Filter will now immediately update when fees are confirmed or unconfirmed by a user without needing to manually refresh the page. 

[DB-150] Account Type Drop-down List – Include Bank Name 

The Account Type drop-down has been updated on all financial pages (Financial Plan, Manual Reconciliation and Account Enquiry) to help users distinguish between accounts when clients have multiple accounts on record. Now, the drop-down includes both the Bank Name and Account Type, making it easier to identify the correct account.

[DB-151] Automatic Reconciliation - Best Match Report for Red Transactions

Previously, the  Red Best Match report available on the  Reconcile Bank Transactions page included transactions that had been matched as green or amber but had not yet been reconciled. The report has been updated to only include transactions from the red 'On Bank File but Not Found' section (users must filter on Red before outputting the Best Match Report to see these results) 

[DB-155] Diary  - Pagination & Actioned by Ordering

We've made some updates to the Diary to improve its functionality. Firstly, we've added pagination when the number of diary tasks displayed exceeds 20, which makes it easier to navigate through a large number of tasks. Additionally, we've updated the Diary ‘To Be Actioned By’ drop-down list so that Case Workers display in alphabetical order of Surname in both the filter and the Add/Edit Diary Entry popups. This enhancement will help users quickly locate the correct Case Worker when assigning diary actions.

[DB-160] OPG Reports - Replace Master Document Permission & Validation

Previously, Full Users had access to ‘Replace Document’ via the Reports>OPG Reports page, this has now been updated so that only Super Admin and Manager can upload master OPG Report Templates. 

[DB-161] Report Generator - Plan Type (Income/Expense) does not save in the filter 

The Report Generator has been updated to correct an issue where the Plan Type (Income/Expense) could not be added to the filter. This has been updated and the filter now correctly retains the criteria.

[DB-162] Full User - Permission Changes Required on Admin>Data Maintenance

Previously, Full Users had permission to replace and delete PDF document templates via Admin>Data Maintenance>Templates>Document Templates, this has now been updated so that only Super Admin and Manager can action this type of change. Full user permission has also been restricted to read-only on Admin>Data Maintenance>Templates>Visit Template. 

[DB-170] Client Account Statement - Output client name as Forename + Surname 

The issue with the client's name appearing on the Bank Statement in the format of Surname followed by Forename instead of Forename followed by Surname has been resolved in the latest release.

SECURITY UPDATES

[DB-157] Security Updates 

For further information please contact support@trojanconsultants.com

TROJAN INFRASTRUCTURE UPDATES 

The following Trojan Administration tasks have also been deployed as part of this release. These are not visible in customer systems and do not affect system functionality for our end users. 

[DB-153], [DB-154] , [DB-158]

PLANNED FIXES AND IMPROVEMENTS IN THE DEVELOPMENT PIPELINE

The top 5 fixes for inclusion in future updates to CasparCloud.  

Workflows – Administration 

Users have reported an error when typing a date into the ‘Date Completed’ field on the Client>Workflows>Administration page. This will be corrected in a future release however in the meantime users can add a date using the calendar function rather than typing into the field. 

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.

Court of Protection Forms

Where a private contact that is marked as an Interested Party or Respondent has a 7-character postcode, the system is including the space when merging the data to the COP14 and COP15, the system needs to ignore the space to ensure all characters of the postcode are merged to the respective document. Users can work around this issue by removing the space in the postcode on the client’s private contact before generating a COP14 or COP15. 

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.

Issue with date format in reports generated by the report generator

We have identified an issue with the report generator that affects the formatting of dates in reports. The dates are currently formatted as YYYY-MM-DD, which can make it difficult for users to sort the report by date. Our development team is actively working on a solution for this issue, which will be included in a future update. 

In the meantime, we recommend a simple workaround for users to make sorting by date easier. By highlighting the date column and performing a find and replace operation, users can replace the dash with a slash. This will update the date format to UK DD/MM/YYYY, which should make sorting the report by date much easier.