Update: In addition to the tickets originally mentioned in the release notes below we are also including the following ticket in the upcoming maintenance release:
DEV-1196 – Logged in customers payments time out occasionally (#23224 & #23197)
Resolved an intermittent issue that caused Sagepay payments to take a payment without changing the status of the record. This was happening when a user on a direct Scheme would wait on the page over 1 hour causing the payment tokens to timeout
We have already identified any policies that would have been affected and have contacted all sites with the relevant case number to check already.
Possibly affected areas – [Payments, Direct Schemes, Cases]
The next SchemeServe maintenance release is now ready. The date for this release will be Monday 15th June 2020 at approximately 22:00.
The LABS environment has been updated and we ask that all clients please check over their own schemes prior to the release.
Please note there is a new labs URL: https://*yoursite*.labs.schemeserve.com
In this release:
DEV-1190 - One off payments show the amount due as zero
When using the ‘One off Payment’ option on the Money tab, the payment amount defaulted to zero rather than the outstanding balance due. This has been resolved and instead defaults to the outstanding balance, but can still be overwritten if required.
Possibly affected areas – [Payments]
DEV-1039 - Document cutting off at 200 pages (#22754)
We've resolved an issue that prevented documents that had over 200 pages from generating correctly.
Possibly affected areas – [Document generation, Cases]
DEV-1149 - Client details not visible to agents
Creating a case in the Admin area via the Case Importer and assigning the case to an Agent did not give that Agent access to the Client details or Notes. This was a bug in the case importer but has now been resolved, restoring the Agent's access to these sections.
Possibly affected areas – [Case Importer, Cases, Agents]
DEV-632- Stop incorrect validation on document templates
This is a performance related update which stop excessive validation on every possible token for every scheme available on a site while saving document templates.
Possibly affected areas – [Documents, Documents Editor, Performance]
DEV-1021- When signing in as a client or agent to report a claim, calender to select date of loss is not functioning correctly (#21828)
When reporting a claim as an Agent or Client and selecting a date of loss on a calendar, you could only select the current or a future date. This has been fixed so that Agents and Clients will now be able to correctly select dates in the past.
Possibly affected areas – [Claims]
DEV-1073- Actioning ‘Do Not Auto Renew’ on the ‘Batch Renewal Invites’ page with no cases selected leads to an error
Selecting 'Clear Do Not Auto Renew' or 'Set Do Not Auto Renew' on the 'Batch Renewal Invite' page with no cases selected previously resulted in an error message but now shows a warning to inform the client they've not selected any cases.
Possibly affected areas – [Batch Renewals]
DEV-1070- Fix activity log to use eventDescription as it’s currently using the masterAccount.Name
This is an update to the Auditing log to display the eventDescription instead of the masterAccount.Name for password resets.
Possibly affected areas – [Password Resets, Users, Audit log]
DEV-1124- Case upload is failing
We've updated the Case Importer to now accept Client.CompanyName so clients with no surname can also be imported.
Possibly affected areas – [Case Importer, Cases]
Despite extensive manual and automated testing from SchemeServe, we are not currently able to test every scheme. If you do encounter an issue that you believe may be related to the update then please contact our obsessive support team who will be happy to help.