Issue with embedded messages
Some correspondence with embedded messages can not be sent out because of formatting issue. Because of the code in paraEmbeddedMsgBodyS HTML rule, Block 4 content( which is populated as a single line on to clipboard) is arranged as fields with 35 char length.
But for some of the fields such as 50F or 59 etc… where content is more than 35 char and should have content in separate lines with specific length ( ex: account number), the formatting is incorrect and does not follow the SWIFT standard, and the message was rejected by end system.
Message gets rejected by end system and marked for manual intervention.
Steps to Reproduce
- Create a correspondence( ex: 192 or 196) and try to embed the message
- Before sending the correspondence, preview the content of embedded message
- Content is not same as block 4 in original message
The root cause of this problem is a defect in Pegasystems’ code/rules. The code does not follow the SWIFT standard.
HFix-10418 fixes the issue.
0% found this useful