Some areas where performance was affected were migrated to Dapper -it was also agreed that all new features would be created directly on Dapper, instead of using the already implemented data repositories running on EntityFramework or Linq2Sql. This significantly increases productivity, as well as simplifies support and updates.
We also replaced .asmx Web Service with ASP.NET Web API, to facilitate the further support and maintenance of the website. This decision was also made due to the need to apply some functions that would be more expensive to introduce using WebServices, and would limit our ability to properly redesign the system.
A payment system for one-time payments had already been implemented in Unit Connect. However, the client wanted users to be able to create recurring payments by specifying a particular day of each month the payment would be repeated. In addition, it was necessary to allow customers to specify a date for one-off payments.
View and manage Tenant Invoices for specific property and billing cycle
Find bills quickly and conveniently by bill number and account number
Print Bills quickly for specific property(ies) and/or Tenants
Create new bills and close previous month
After examining their current system, it became clear that it was not suitable for this purpose. When the payment system was developed, it didn't have the potential for further expansion. Considering the fact that this system was linked to different parts of the service, making any changes could have led to the failure of the entire system.
After some discussion, we solved the problem by taking the existing payment system down and developing it from scratch, being mindful of all expectations, as well as problems that arose in the previous version of the system. We updated all the places where the payment system interacted with the rest of the service, laying the possibility to expand in the future.