General Overview & Impact

Ability to delete a meter

Having taken on feedback, we have now implemented the ability for a user to delete a
meter in Mabdeck, provided this hasn't been used on a statement, or is linked to a PAYG
hub. This provides more flexibility for users to remove meters which are no longer
needed, or have been added in error, so the list of meters in Mabdeck is concise, correct
and updated.

Ability to delete a meter - PBI/2460

Ability to get most recent reading from the API

We have added two new fields in the Readings API, for most recent reading, and most
recent automatic meter reading against every meter. Now that this functionality is in
place, we can work on improving the speed of the Active Meters report, and the Last
Meter Read report.

Ability to get most recent read back from the Readings API - PBI/18569

General upgrades and fixes

We are currently working on upgrading Mabdeck to the newest version of .NET, which
will help us to maintain ISO27001. As part of the ongoing work to upgrade Mabdeck,
there are some more changes in this release which will help towards that. Although you
won't be able to see these changes themselves, be assured that the code is being
tweaked and improved in the background, and we hope your front end experience will
become a lot smoother as a result of this too.

Additional Fixes & Improvements

Fix for property refresh when a meter has been selected on the "Upload Readings"
form - Bug/2757

Add transfer server success message showing incorrectly - Bug/8317

Virtual Meter - Edit form shows incorrect Network and Supply Type - Bug/13280

Fix for Stripe recurring payment dropdown when "no options available" - Bug/15508

Unable to delete reports set up to "All Networks" - Bug/19523

New error message for statement generation - PBI/19090

Add Billing Agent VAT Number to client setup - PBI/19529