You are right. I've fixed it and added proper check in the unit test.

You are right. I've fixed it and added proper check in the unit test.

Since DefaultAdjustmentReasonValidator, DefaultFreeTextValidator, and DefaultUnpackKitValidator still implement StockEventValidator and exist as bean, won't they get executed twice? First in a for ...

Since DefaultAdjustmentReasonValidator, DefaultFreeTextValidator, and DefaultUnpackKitValidator still implement StockEventValidator and exist as bean, won't they get executed twice? First in a for loop, and then via those above extension point injections (not 100% sure, but I think this is what happens)

OLMIS-6911: Added extension points for AdjustmentReason FreeText and UnpackKit validators
OLMIS-6911: Added extension points for AdjustmentReason FreeText and UnpackKit validators
COVSUP-51: Added automatic loading of Aggregate Equipment Report to database
COVSUP-51: Added automatic loading of Aggregate Equipment Report to database
OLMIS-6897: Added the ability to cache physical inventory drafts and valid reasons in local storage
OLMIS-6897: Added the ability to cache physical inventory drafts and valid reasons in local storage
Changelog

Changelog

This file should be removed.

This file should be removed.

OLMIS-3100 - Removed stock adjustment reasons endpoint
OLMIS-3100 - Removed stock adjustment reasons endpoint
Actually it's a build-in column name

Actually it's a build-in column name

Typo in 'typname'?

Typo in 'typname'?

OLMIS-6890: Provide a way to automatically upload Requisition templates
OLMIS-6890: Provide a way to automatically upload Requisition templates
OLMIS-6876: Fixed order created without releasing requisition
OLMIS-6876: Fixed order created without releasing requisition
OLMIS-6876: Fixed order created without releasing requisition