Skip to main content

Release Notes 2024.17

General Overview & Impact

Additional work has been completed on the Orbit API, to allow users to view and
subscribe to events taking place on their hubs. This will include balance updates and
valve state changes

Further work has been done to progress the Credit Control project. This includes
updating the Credit Control structure in the database, to allow us to track debts in
future, rather than just those created after a credit control procedure has been set up. We
have also changed the way that all transactions are added to Mabdeck in the
background, to facilitate future Credit Control changes.

The logic which sits behind statement generation has been updated, which is the first
part in a series of ongoing changes to improve the statement approval process.


We will now save the vend code of a PAYG transaction as the transaction reference,
so that this can be referred back to in the transaction reports. This will also ensure that
PAYG transactions are never duplicated on an account.


We are currently working on upgrading Mabdeck to the newest version of .NET, which
will help us to maintan 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.

New Features

Orbit

  • Ability to see all Orbit events in the API 
  • Ability to subscribe to events in the API

General

  • Ability to generate different invoice types 
  • Creation of Account Debt when transactions are created

Improvements

  • Add Address Line 2 to import templates
  • Move PayPoint Direct Debit Robot into a function app
  • Updates to Add Data Logger form for Orbit devices 
  • Updates to statement generator logic
  • Ability to add a Late Payment Fee via the account page
  • Move add transactions into new method
  • Consolidate calls to logging API 
  • Use Vend Code as transaction reference, for PAYG transactions
  • Check vend code when adding PAYG transactions, to prevent duplicates
Powered by Zendesk