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

Field 79 validation issue



Field 79 in swift messages should have a max of 35 lines as per standard. Even though Smart Investigate provides validation for this field 79 to be 35 lines , it fails to provide validation for field 79 in the tickler messages.

Error Messages

No error message is shown . when an tickler message is sent out some tickler information is added to the existing 79 field, as a result the 35 lines limitation is broken

The tickler is being sent successfully now but it is essentially rejected at outside system i.e BESS

Steps to Reproduce

1) Create an case and send a swift correspondence with tickler enabled.
2) fill the maximum number of lines for field 79 i.e 35.
3) Submit the correspondence, this swift message will be sent successfully as it has valid number of 35 line

Root Cause

The root cause of this problem is a defect in Pegasystems’ code/rules.

Edit validate rule SWIFT79 fails to validate the swift message F79 field when Tickler is selected. Enabling Tickler adds extra lines of text which gets appended to F79 field when the activities ASSEMBLEF79TICKLER1 and ASSEMBLEF79TICKLER2 are called, but these activities does not have step to validate F79 length.


This issue is resolved by hotfix item HFix-22421

Published June 3, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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