SA-19799

Summary

Developer upgraded environment from Pega 7.1.7 directly to Pega 7.1.9. After the 7.1.9 update to Decision framework, the application started throwing InvalidReferenceException stack traces.

Error Messages

( internal.mgmt.Executable) ERROR AdminUser - Exception
com.pega.pegarules.pub.clipboard.InvalidReferenceException: The reference pyWorkPage.Customer is not valid. Reason: Cannot modify value of Reference Property without first linking it to another property using Property-Ref
at com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl.getThis(ClipboardPropertyImpl.java:5347)
at com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl.setAsReference(ClipboardPropertyImpl.java:5626)
at com.pega.pegarules.data.internal.clipboard.PropertyDataPageWrapper.getPageAfterSettingReference(PropertyDataPageWrapper.java:1257)
at com.pega.pegarules.data.internal.clipboard.PropertyDataPageWrapper.populateDataFromPage(PropertyDataPageWrapper.java:1181)

Steps to Reproduce

1. In Next-Best-Action Advisor (NBAA), enter customer ID and then select an Intent.
2. When an Offer is presented, accept or reject the Offer.

Root Cause

The Customer property reference was getting lost between the two work objects from Customer Intent to Present Offer in this application; as there was a customization in the Out-of-the-box (OOTB).

Present Offer flow for the SetupCustomer Activity was calling a “SetupCustomerDummy” custom Activity instead of calling the OOTB SetupCustomer Activity. Because in this custom “SetupCustomerDummy” Activity, missed setting up Property reference link for Customer property.

Resolution

After making a local change to explicitly establish Property reference link in the custom SetupCustomerDummy Activity for Customer property, one can Accept the Offers successfully from the Suggested Offer page.