Skip to main content

 –

Extending message validation

Suggest edit Updated on September 18, 2020

Copy the following rules in your ruleset to extend the validations of the transaction, information receiver (Provider), and Subscriber submitted in the message:

NameTypeDescription
CheckLimitActivityValidates for number of benefit requests in a single transaction. The threshold set in the Foundation is 25.
SetAAAData TransformSets AAA segment information when Check Limit validation fails.
CheckProviderOnFileActivitySearches for Information Receiver Provider information based on Provider ID.
SetProviderReceiverLevelData TransformMaps AAA segment information when Provider validation fails (provider not found).
SubscriberOnFileActivitySearches for Subscriber in membership system.
SetForNoMemberDataData TransformMaps AAA segment information when Subscriber validation fails (subscriber not found).
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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