Pega gives Warning not to use Data pages in strategy set property, how to reference data from data page in strategy
Pega gives Warning not to use Data pages in strategy set property.
We have product info and pricing details stored in a table in DB, and each proposition has product code values stored in it. As per current implementation , we are passing these product codes into a data page.
Data page held the logic of computing the final pricing and mapping it to single property.
The computed value is mapped to SR property . This mapping was done in the set property component , which is throwing warning .
what sis the other way to implement?
We tried 3 different approaches to overcome this warning but faced limitation in all.
In the First approach, We tried the approach of creating a property called “.OfferPricing” in SR class to Refer to the data page D_OfferPricing and have the property directly mapped to the “.Fee” but found that we cannot create a page/pagelist on SRclass
In the Second approach, We tried the approach of creating a property called “.OfferPricing” in Customer class to Refer to the data page D_OfferPricing and have the property mapping in strategy but the pointer concept did not work in the strategy..
In the Third approach, We used Data import in strategy, call data page from it and map the result in properties mapping. HERE AGAIN THE ISSUE IS OF PASSING THE Product CODES as .ExternalCodes property value in data page parameter which is coming from propositions, as data import component will not take any input connector. If the value is hard coded the above approach , it works fine.
***Edited by Moderator Marissa to update SR Details***
If I understand correctly, you have a parameterized data page D_OfferPricing which accepts one parameter ExternalCode and returns a scalar value as .Fee, is that correct?
The reason we issued a warning about data page from strategy side was because:
poor performance of running data page
inference engine is not supported from decisioning side
If these two issues are not your major concern, I think you can safely ignore this warning. If you want to get rid of this warning, you can do the property assignment in a decision table for example to hide the warning.