Support Article
SWIFT inbound message fails to create case BadInputException
SA-86623
Summary
Inbound SWIFT message causes a failure and does not create a Message case.
Error Messages
<Workitem id> creation failed
com.pega.pegarules.pub.database.BadInputException: Trying to save an invalid page: Trying to save an invalid page: page is not valid .pyWorkParty(SendingBank).LastCorrRef: Invalid value specified for LastCorrRef. Value doesn't adhere to the Validate: SWIFTLastCorrRef
at com.pega.pegarules.data.internal.access.Saver.validate(Saver.java:1162) ~[prprivate.jar:?]
at com.pega.pegarules.data.internal.access.Saver.saveDeferred(Saver.java:385) ~[prprivate.jar:?]
at com.pega.pegarules.data.internal.access.DatabaseImpl.saveDeferred(DatabaseImpl.java:2735) ~[prprivate.jar:?]
at com.pega.pegarules.data.internal.access.DatabaseImpl.saveDeferred(DatabaseImpl.java:2719) ~[prprivate.jar:?]
Steps to Reproduce
- From the Manager portal, click 'New'.
- Select 'MsgCase' as Business.
- Select Generic Message as the Case Type.
- Use a SWIFT message with Field 20 that includes a '+' sign, (for example, ...:20:GR1921253012.0+H...).
- Click Create. A new case is not created.
Root Cause
A defect in Pegasystems’ code or rules.
The SWIFTLastCorrRef Edit Validate rule does not allow all values in the SWIFT character set.
Resolution
Perform the following local-change:
Override the SWIFTLastCorrRef Validation rule.
For more information, refer to: https://community.pega.com/support/support-articles/case-creation-swift-message-fails-prod-some-tag20
Alternatively, apply HFix-55775.
Tags:
Published September 6, 2019 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.