9 Searching and auditing

 

This chapter covers

  • Another iteration on our ACH dashboard
  • Adding searching capabilities for ACH transactions
  • Auditing of user actions

In previous chapters, we built the minimum viable product (MVP) and went through an iteration where we received feedback and used it to drive the next set of enhancements. This chapter continues using the same concepts. With the release of expanded support for exceptions and various UI/UX tweaks, we should expect feedback on those features and other functionality that users need.

Users would like to be able to search for transactions based on several criteria as they need to handle customer complaints about when a transaction was processed. In addition, other stakeholders have asked for the ability to audit interactions with the dashboard to gauge customer engagement and set up user tracking in the future.

9.1 Sprint planning

9.2 Searching ACH transactions

9.2.1 BDD testing for searching

9.2.2 Search API

9.2.3 UI search page

9.2.4 Integration testing with Playwright

9.3 Auditing user interactions

9.3.1 Database design

9.3.2 TDD testing for auditing

9.3.3 Auditing logic

9.4 Using middleware for our logging

9.5 Viewing the audit log

9.5.1 Creating the page

9.5.2 Creating the page components

9.5.3 Adding the APIs for the audit log

Summary