ADMinputs predictor data not saved, accept offers fails
Users work with stateless calls to retrieve and accept offers. An issue is seen when there are two calls in the following pattern:
During first call - Make Decision(Get Offers call), ADM Model is used in the strategy and the predictor data (pzADMInputs) is being saved in a CustomerData blob for later retrieval.
During second call - Set Response (Accept Offer call), when the CustomerData instance is opened, the pzADMInputs is retrieved as null and because of this, the predictor data is not saved in their adaptive models.
There is an issue saving the pzADMInputs.pzData (JavaObject) to the blob.
Steps to Reproduce
1. Call Get Offers: Save CustomerData with ADMInputs/predictordata - pzADMInputs.
2. Call Accept Offers: Retrieve CustomerData, notice that ADMInputs comes back blank/null.
A defect in Pegasystems’ code or rules: The serialize object option was unset in a final rule.
0% found this useful