General Overview & Impact
Orbit
In this release, work has been completed on Orbit, so that Mabdeck has the ability to
read all events which have taken place in the Orbit API. This means that each time a hub
balance is updated in Orbit, for example, Mabdeck will receive this information and
update accordingly.
- Ability for Mabdeck to consume events from the Orbit API
- Balance update event
- Send HubId with events
Statements
Having identified an issue where a number of statements are becoming locked, when a
reversal is attempted, we have re-written the process for statement reversal. The result of
this will be that statements will no longer get stuck in a locked state
- New function app for statement generation
- Re-write logic for statement reversal
Credit control
A significant amount of work has been completed on the new Credit Control structure.
While we already had the ability to create account debts using the new format, this now
includes the logic behind tracking account debt when refunds are added to accounts, or
transactions are removed from an account. All of this work is progressing towards
completely replacing the existing Credit Control structure in Mabdeck, and being able to
track every single existing account debt accurately.
Although these changes will remain hidden in Mabdeck for a period of time, until the new
structure is ready in its entirety, we hope this gives an idea of the work going on in the
background to replace the existing functionality.
- Account Debt - Handling refund transactions
- Account Debt - Paying back
- Account Debt - Removing credit transactions
- Account Debt - Removing debit transactions
- Account Debt - Archiving and Unarchiving
- Credit Control procedure setup page
Careem Transaction Robot
A new transaction robot has been created, to be able to automatically process
transactions in Mabdeck made via the Careem payment provider, which will be used by
our clients in the Middle East.
- Transaction robot to process Careem transactions
Small Improvements
We have made a number of small improvements to the existing functionality, to elevate
the user experience. This includes the ability to add Client Notification transaction types
in Mabdeck, in order to track payments made outside of the system. We have also made
changes to the existing IzarNet reading robot, to account for readings coming through for
water meters.
Please find an overview of all of these minor improvements below:
- Show EE Monitor location on the Edit Property form
- New Transaction Type - Client Notification
- IzarNet Reading Robot changes for Water Meters
- Ability to remove report templates in bulk
- Update Agresso report Direct Debit claim date format
General Updates and improvements
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
- Fix issue with being unable to upload summary templates
- Fix for being unable to download multiple correspondence
- Fix for multiple Direct Debits being created when statement publish fails
- Fix for PayPoint not showing as a payment option online, if it is the only option