Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Calling free-text parsing

Updated on March 4, 2022

Free-textparsing is called only from the NewWork flow of message cases. It is not available from a manual flow action, or anywhere in exception work case processing. The NewWork flow calls the FreeFormatTextParse flow immediately after the ParseMessage flow. Smart Investigate for Payments parses the inbound message (stripping away the header, parsing Fed Service or SWIFT fields, and so forth) and then calls free-text parsing.

The message class determines which properties are parsed — only block 4 is parsed for SWIFT messages, otherwise the entire body of the message is sent for parsing.

This table provides examples of field parsing values for Smart Investigate for Payments.

Data Type/ValueParsed how
SenderValue typically occupies a fixed position in the record header.
ReceiverValue typically occupies a fixed position in the record header.
Message DateValue typically occupies a fixed position in the record header.
Message TimeValue typically occupies a fixed position in the record header.
Message PriorityValue typically occupies a fixed position in the record header.
Message TypeValue typically occupies a fixed position in the record header.
Sender’s Inquiry ReferenceUnknown string; often follows a known tag (for example, :20:).
Receiver’s Inquiry ReferenceSmart Investigate for Payments ID with a PEG prefix, such as PEG051228-000001.
Sender’s Transaction ReferenceUnknown string; often in field 21 or following an “Our Ref:” string.
Receiver’s Transaction ReferenceString, often in field 21 matching a known pattern.
Transaction DateDate pattern in sentence including DD, Dated, and so forth.
Value DateDate pattern in sentence including VAL, Value, and so forth.
Transaction AmountAmount pattern that consists of up to 16 alphanumeric characters with punctuation preceded by three alphabetic characters.
Transaction CurrencyPattern of three alphabetic characters adjacent to a group of numeric characters.
Work TypeWords orphrases that drive a reason for inquiry.
Pega Smart Investigate for Payments Implementation Guide

Have a question? Get answers now.

Visit the Support 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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us