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

CreditTransactionsExist when rule incorrectly returns false

SA-41487

Summary



When starting a dispute with merchant credits using a non-CSR user type and routing it to the CreditSearch subflow the CreditTransactionsExist when rule runs and incorrectly returns the value "false". In this scenario, the user is never directed to review the credits, even though credits do exist.


Error Messages



Not Applicable


Steps to Reproduce



1. Using the out-of-the-box sample application, log in as a user with the DisputeSysAdminIssuer access group.
2. Initiate a claim using test account 4552999999999999
3. Select the sale transaction at Joes Bar and Grill for $917.25 (NOTE: the corresponding credit transaction with ARN 24610432650004020160158 must have its transaction type updated. "CR" is not the correct type for a Visa credit transaction (see PegaCard-Interface-Transaction-Visa.getCreditTransactionList). This data needs to have a transaction type of 06.
4. Upon submitting the claim, the dispute will immediately route to QualifyDispute, having bypassed the CheckForCredit.

Root Cause



A defect in Pegasystems’ code or rules: CreditTransactionsExist when rule returns true when CreditTransactionsList.pxResultCount != 0. .pxResultCount never has a value because the CreditCheck activity never sets it. .pxResultCount is really only guaranteed to exist when the list is sourced from a report definition.

Resolution



Apply HFIX-35819

Suggest Edit

Published August 26, 2017 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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