8 Exceptions

 

This chapter covers

  • Initial feedback from the MVP
  • Planning and addressing user requests
  • Identifying different types of exceptions
  • Updating the dashboard
  • Ensuring our UI is responsive

In chapter 7, we successfully launched our minimum viable product (MVP) to our user base to help solicit feedback and drive enhancements to the product. The feedback varied significantly—from users who loved the new direction of the dashboard to those who expressed their dissatisfaction, feeling it was missing too much functionality although it was not meant to be a full replacement yet. The business now wants us to both capitalize on what went well and address some of the missing functionality the users are currently clamoring for.

By far, the biggest need recognized in our MVP was having a wider variety of ACH-related exceptions and making their handling possible within the user interface. This chapter identifies different categories of exceptions and ways to identify and potentially recover from them.

8.1 Planning enhancements

8.2 Exceptions and warnings

8.3 Creating ACH files with exceptions

8.3.1 Creating ACH files with file-level exceptions

8.3.2 Creating ACH files with batch-level exceptions

8.3.3 Creating ACH files with entry-level exceptions

8.3.4 Clean-up of our file creation syntax

8.4 Expanding the ACH processing for exceptions

8.4.1 ACH exceptions in the database

8.4.2 Recovery options

8.5 Updating the ACH parser

8.5.1 Creating unit tests for the exceptions

8.5.2 Supporting the exceptions in our parser

8.5.3 Validation in Pydantic

8.6 Updating the APIs

8.6.1 Retrieving an unparsed record

8.7 Insights into exceptions with the UI

8.7.1 Showing all the exceptions

8.7.2 A visual cue for exceptions

8.8 Additional UI changes