Release Explorer

Release Summary for feat/USBAML1-2169-transaction-view

Overview

This release significantly enhances the transaction view capabilities and observability for SWIFT messages by integrating new integrity check enrichments, improving message splitting for GPO 'MX' and 'MT' messages, and introducing a comprehensive regression test suite to validate observability fields. It also refines event filtering logic to better handle valid event triples and correlation identifiers.

New Features

  • Introduced multiple new observability enrichment property files with integrity check expressions for various SWIFT message fields, including intrabank settlement amounts, debtor/creditor identifiers, agents, and remittance information.
  • Added support for extracting and processing MT message payloads embedded within GPO 'MX' messages, enabling separate handling and componentization of MT and MX payloads.
  • Developed a new regression test class dedicated to verifying the observability fields, including transaction and transaction event indexes, ensuring accurate indexing and passport check workflows.
  • Added validTriples configuration to define sets of event triples requiring only GPO context ID correlation, simplifying filtering and correlation logic for message processing.

Improvements / Changes

  • Extended transaction report and event report fields to include integrity check-related fields such as integrityCheckIssue, maxIntegrityCheckDifferenceSeverity, and integrityCheckDifference.
  • Added a dedicated integrity check difference index with associated constants and keys (e.g., comparisonTimestamp, comparisonRuleName, attributeName, severity) for enriched monitoring of data integrity discrepancies.
  • Updated internal indexing logic to set integrity check difference keys from input/output events and conversation messages using the defined constants for consistency.
  • Refined GPO filtering and RPIST correlation by incorporating the validTriples list to recognize valid event triples and adjust validation flow accordingly.
  • Enhanced message splitting logic in the GPO MX message splitter to detect and separate both MX and MT payloads embedded in GPO messages, facilitating improved payload processing.
  • Improved unit tests for the GPO MX message splitter covering MX-only, MT-only, and no-split cases to ensure robust message component detection.
  • Updated multi-value field sorting and message link normalization in regression tests to improve consistency and reliability of exported data.
  • Configured the observation regression test to load input data from multiple message readers, properly clear indexes before tests, and wait for processing completion to validate observability data end-to-end.

Bug Fixes

  • Fixed issues in message splitting where MT messages within GPO events were not correctly isolated, potentially causing incorrect payload handling.

Technical / Developer Notes

  • Added numerous constants representing integrity check difference fields to centralize key names and ensure code clarity.
  • Implemented new component wrappers and updated splitter logic with regex patterns to reliably parse complex GPO event payloads containing nested MT and MX messages.
  • The regression tests utilize transaction management to safely perform bulk data loads and validations with appropriate waiting periods for asynchronous processing.
  • Configuration of validTriples was externalized with proper getter/setter to enable dynamic management without code changes.

Breaking Changes

  • None identified.

Acknowledgements / Contributors

  • Thanks to the implementation and testing teams for comprehensive coverage of observability enhancements and message parsing improvements.