Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

(Software Version: 2024.09.27 Database Version: 2024.09.27)

Release Date: September 27, 2024



Bug Fixes

Fisherman Accounting

NS-12501 & NS-12896 – Fixed fisherman ACH Payment Numbers were not being automatically assigned and ACH was allowed as a Default Payment Type

ACH Payments are a great time saver: no more printing checks and hoping the alignment is current, no more stuffing the checks into envelopes, and no more licking stamps. Yay! We’ve fixed a few bugs in the Fisherman ACH configuration page to make processing ACH Payments run more smoothly. Setting ACH as a Default Payment Type now saves correctly. The options for Draft and Wire were removed, since these options only apply to the Vendor ACH. Continuing the Default Payment Type theme, we fixed a typo that included a trailing space after the word “Check”, which made our Software Quality Assurance team ecstatic.

We weren’t done with ACH just yet though. We also found and fixed a bug where the Payment Numbers weren’t being automatically assigned when ACH Payments were processed for Fisherman configured with SEC Codes for Checking or Savings.

Purchasing

NS-12921 – Fixed Vendor Class Duplicate ID Validation and Unexpected Rolldown to all Vendors

It doesn’t make any sense to have multiple Vendor Classes with the same Class ID – how would you differentiate between two or three classes all called the same thing? NorthScope was supposed to have a validation in place to prevent inadvertent duplication, but that validation wasn’t working correctly. We’ve corrected that, so the validation will work as expected. While we were testing that fix, we found and fixed a problem where the Rolldown feature on the Vendor Class record view was rolling down changes to all Vendors, Fishermen, Tenders, and Fisherman & Tenders, regardless of which class those entities were assigned.


Technical Changes

  • No schema changes.
  • No config file changes.



  • No labels