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

SI62SP1[Swift]Colon and Hyphen characters cause messages to NAK

SA-2601

Summary



Running SmartInvestigate 62SP1 and encountered an issue with SwiftMessage Validation. When a users sends SWIFT correspondence from Smart Investigate the message validation does not notice if a second line in a field content begins with a colon or hyphen character. Such a message is against SWIFT MT messaging standards so the message gets a NAK (Negative Acknowledgement).


Error Messages



None in PRPR / Smart Investigate. The message gets a NAK.

Steps to Reproduce


1) Create a Swift Correspondence of Type MT199
 
2) In Field 79, enter 2 lines of text in which the second line starts with colon or hyphen character. 
3) The validation does not occur. 


Root Cause



The root cause of this problem is a defect in Pegasystems’ code/rules in 
Rule-Edit-Validate rule SWIFT79.


Resolution



Provided HFix-9881 to address the reported 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