Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Issue with embedded messages

SA-4763

Summary



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.

Error Messages



Message gets rejected by end system and marked for manual intervention.


Steps to Reproduce

  1. Create a correspondence( ex: 192 or 196) and try to embed the message
  2. Before sending the correspondence, preview the content of embedded message
  3. Content is not same as block 4 in original message

Root Cause



The root cause of this problem is a defect in Pegasystems’ code/rules. The code does not follow the SWIFT standard.



Resolution



HFix-10418 fixes the issue.  
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us