Skip to main content

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

Decision table rules

Updated on June 22, 2022

The Decision Table rules listed are available to configure features to meet business needs. Copy each decision table rule into your implementation layer (ruleset) and update the values as required.

Pega Foundation for Financial Services

The following table lists the decision table rules and its purpose in Payment Exception Recovery application.

Decision Table Rules

Decision Table nameApplies to classPurpose
EvaluateProvisionalCreditPFSA-PER-Work-PaymentExceptionDetermine if provisional credit should be given
EvaluateLowValueWriteOffPFSA-PER-Work-PaymentExceptionDetermine if low value write off applies
SetCorrDataPFSA-PER-Work-PaymentExceptionDetermine which correspondence rule should be used
SetPaymentNetworkPFSA-PER-Work-PaymentExceptionDetermine which list of reason codes to display
EvaluateSupplementalInfoClassPFSA-PER-Work-ClaimDetermine which Supplemental Information questions to load
PrivilegeBasedRoutingWBPFSA-PER-WorkWork queue routing logic
PrivilegeBasedRoutingWLPFSA-PER-WorkWorklist routing logic
EvaluatePERTransTypePFSA-PER-Data-TransactionDetermine which type of Payment Exception case to create
  1. In the header of Dev Studio, search and select the decision table rule. For example, EvaluateProvisionalCredit.
  2. Save the decision table rule into your implementation layer work pool.
  3. Set the Applies to class to your implementation layer that corresponds with the Payment Exception Resolution class listed above.
  4. Perform steps 1-3 for the other decision table rules listed in the table above.

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

Close Deprecation Notice
Contact us