Skip to content

(CU-86b8v3uxa) Fix metadata extraction for ACK followed by MT Output#299

Open
zubri wants to merge 1 commit intomainfrom
CU-86b8v3uxa_Fix-metadata-extraction-for-ACK-MT-Output
Open

(CU-86b8v3uxa) Fix metadata extraction for ACK followed by MT Output#299
zubri wants to merge 1 commit intomainfrom
CU-86b8v3uxa_Fix-metadata-extraction-for-ACK-MT-Output

Conversation

@zubri
Copy link
Member

@zubri zubri commented Mar 12, 2026

Summary

  • ACK (service 21) followed by MT with block 2 Output now extracts all metadata (identifier, direction, MIR, UUID, UETR, etc.) from the appended MT instead of defaulting to ACK
  • ACK followed by MT with block 2 Input preserves the existing ACK/NAK behavior
  • Changes in MtSwiftMessage.updateAttributes() (via resolveEffectiveModel()) and SwiftMessageUtils.identifier()

Test plan

  • Existing test testParseAckWithOriginalMessageCopyInput verifies ACK + MT Input keeps identifier as "ACK"
  • New test testParseAckWithOriginalMessageCopyOutput verifies ACK + MT Output extracts identifier, direction, value date, and amount from the appended MT
  • All existing tests pass

🤖 Generated with Claude Code

When an ACK (service 21) message has an appended MT with block 2 Output,
the metadata (identifier, direction, MIR, UUID, UETR, etc.) is now
extracted from the appended MT instead of defaulting to ACK.
For ACK followed by MT Input the existing behavior is preserved.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants