All Systems Operational
🎩 SchemeServe ? Operational
🔗 API Operational
📈 Reports Operational
✉️ Emails Operational
☎️ Obsessive Support™️ Phone Operational
🎟️ Obsessive Support™️ Ticket Desk Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
Scheduled - The next SchemeServe maintenance release is now ready. The date for this release will be Monday 8th March 2021 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.

You can test the update by visiting the labs environment here:
https://*yoursite*.labs.schemeserve.com
You can follow updates of this release and any subsequent work required on our status page:
https://status.schemeserve.com/


In this release:

[DEV-90] - Switch Insurer at Renewal
Previously there was no way to automatically switch insurer at renewal in the event the insurer is in run-off. Now if any insurer is no longer able to provide a quotation for a case at renewal (by way of a decline) it will go through the standard quotation process and select the cheapest non referring insurers.
This will need to be turned on manually for each scheme that it is required for within the scheme settings under the advanced tab "Re-run set lowest rates at renewal if any of the current insurers decline."
To set an insurer in run-off, please add a rule to decline cover.


[DEV-1391] - Update help guide button to restrict access to help guide
The help guide has recently been updated to match the latest SchemeServe branding. Going forward access directly to the help guide will be restricted and a user will need to click on the help guide button at the top of the SchemeServe admin portal in order to access this. Once clicked it will retain access for you on that computer. 
This will allow links within the help guide to take users directly to the page within their own site when clicked.


[DEV-343] - Scheme.InceptionDateSelectedTimeZones set as blank string
When no time-zones are selected SchemeServe defaults to use GMT however because of this it made it seem to clients that there was no times zones chosen.
This has been adjusted so that when no time-zone is selected that GMT is shown to be selected by default.
This was a visual issue only and did not affect the functionality


[DEV-829] - Refer if attempt made to go on cover without main insurer
Previously in very rare circumstances, it has been possible for a case to be put on cover when there is no main insurer set.  This has now been rectified so that if no main insurer is set that the case will refer instead.


[DEV-1153] - Fix view agent button on case view
When viewing a case the button to link to the agent was instead linking through the black agent settings page. This has been rectified so that the correct agent is selected.
As part of this, the link will no longer be visible if the case is direct to client case.


[DEV-1286] - Renewal record showing as 3rd record even if it's the 2nd record
Previously when a renewal record was created on a re-quote the 2nd record label was skipped and stated it was the 3rd. This has been fixed so that it correctly displays the label count.


[DEV-1306] - Cases incorrectly showing under agent search
It was possible for cases to show under the wrong agent when searching agent 1's name which was part of agents 2's name eg:
A search for agent1 would include cases from
agent123
This has been corrected to use the agent ID rather than the agent name so that only the specific cases are visible under each agent search.
This only affected cases on a single site and no information that should not have been would have been possible to access from this.


[DEV-1333] - client name question is not retaining new client titles added by way of the options section of the question editor
Previously when using custom client name titles in the questionset these were reverting on submission. 
This has now been fixed so that custom titles entered will propagate throughout SchemeServe.


[DEV-1343] - Reports - 'Next month' date range is a day short
When running reports with the range of next month rather than selecting dates the results were returning a day short. This has been corrected so that the date range will now contain the correct number of days for next month.


[DEV-1353] - MTA - adding endorsements from different insurer
If a case was altered to use a different insurer from the one(s) selected on the original quotation, the endorsements from the original insurer were still being added. 
This has been fixed so that only endorsements from the currently selected insurer(s) are added.


[DEV-1384] - _CoverBefore and _ResultBefore selecting the wrong Renewal when there are multiple Renewals on Adjustment regardless of status.
Previously _CoverBefore and _ResultBefore were providing incorrect figures during renewal when there were draft caserecords on a case. Draft records have been removed from the calculation and as a result, the correct figures are now being returned.
We have checked all existing case records, and this will not have affected any cases at this time.
No remediation action will be required by any client. 


[DEV-1386] - Documents not showing 'None' where there are no MP endorsements
Previously on multipage schemes where there were no additional endorsements to add nothing was returned. This was not clear so has been adjusted to display none when no endorsements are returned.


[DEV-1389] - Key question on MP issue when the Key Question is a 'Dropdown' question type
Previously the value of dropdown question types could not be used as the key question in multi-pages.
This has been fixed so that the value of dropdowns can now be used correctly.


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.
Mar 2, 17:03 GMT
SchemeServe
Fetching
Past Incidents
Mar 8, 2021

No incidents reported today.

Mar 7, 2021

No incidents reported.

Mar 6, 2021

No incidents reported.

Mar 5, 2021

No incidents reported.

Mar 4, 2021

No incidents reported.

Mar 3, 2021

No incidents reported.

Mar 2, 2021

No incidents reported.

Mar 1, 2021

No incidents reported.

Feb 28, 2021

No incidents reported.

Feb 27, 2021

No incidents reported.

Feb 26, 2021

No incidents reported.

Feb 25, 2021

No incidents reported.

Feb 24, 2021

No incidents reported.

Feb 23, 2021

No incidents reported.

Feb 22, 2021
Completed - The scheduled maintenance has been completed.
Feb 22, 22:20 GMT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 22, 22:00 GMT
Scheduled - The next SchemeServe maintenance release is now ready. The date for this release will be Monday 22nd February 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.

You can test the update by visiting the labs environment here:
https://*yoursite*.labs.schemeserve.com

You can follow updates of this release and any subsequent work required here on our status page:
https://status.schemeserve.com/


In this release:

DEV-1390 Aggregator Page - Back button throws error
The back button on the aggregator was missing one of the properties required to return to the correct page. This has been amended so that the property has been added and will now go back to the correct page.

DEV-1392 Updated React frontend
We are beginning the process of releasing updated front end components for the SchemeServe administration panel also implementing an updated deployment pipeline allowing for quicker updates of individual components. Due to the use of Custom CSS and JS inside of the SchemeServe portal on some sites, this may not be automatically available on every site.

DEV-1393 unified access gateway
As part of the release we will also be switching over to a new unified access gateway for all of SchemeServe. This should not create any noticeable change in experience within SchemeServe due to the severity of the change we are informing everyone


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.
Feb 16, 17:03 GMT