Release: feat/USBAML1-2169-transaction-view

Overview

This release refines integrity check processing by improving event condition evaluations and filtering for SAA rules. It enhances code maintainability with the use of constants instead of hardcoded strings and adds comprehensive documentation of the integrity check comparison logic. Additionally, method behavior updates streamline difference handling.

Improvements / Changes

• Updated SAA-In and SAA-Out rule filters to rely on specific system and interface fields rather than loosely on status or generic application fields, improving rule precision for transaction views.
• Refined event condition checks in integrity comparisons: removed explicit application field equality checks to fully rely on defined input/output rule conditions, simplifying and consolidating logic.
• Replaced hardcoded index and message key strings related to integrity checks with constants imported from BamlConstants for better consistency and maintainability.
• Changed addIntegrityCheckDifferences method from returning a collection to void, reflecting internal handling improvements in difference message processing.
• Added detailed JavaDoc comments outlining the integrity check comparison workflow, including flagging of events, severity updates, and message creation, thereby enhancing code readability and supporting future maintenance.

Bug Fixes

• None explicitly identified.

Technical / Developer Notes

• Imported static constants from BamlConstants to replace string literals for keys such as integrityCheckDifference, correlationIdentifier, currency, and reference.
• Adjusted timestamp key retrieval to use a variable rather than hardcoded key string.
• Commented complex integrity check comparison logic to ensure clear understanding of difference detection, event flagging, and severity management.

No breaking changes require developer action.