Question
Achmea
NL
Last activity: 26 Aug 2021 2:17 EDT
Starting evidence and propensity remain empty after check in
Hi guys,
We want to use starting evidence and propensity within offers. We have offers that we use in combination with a adaptive models. The fields remain empty after we put in the numbers. It seems to correlate with the smooth propensity calculation. Can anyone tell us what we are doing wrong?
Also, where in the adaptive model rule can we do the smooth calculation? We cannot find it anywhere.
Kind regards,
Mohamed
Pegasystems Inc.
US
Hi @MohamedA9221,
Are you using NBA Designer or a custom decision strategy? Also, when you say the field remains empty, are you referring to the strategy results after running the strategy or do you mean on the Action rule itself?
Achmea
NL
@SethRobinsonThe fields remain empty in the offer rule itself after i check in a offer. It does not give any validation error. It let's met check in the rule and after i close the rule and reopen it, the fields are empty again. Is this a bug?
Pegasystems Inc.
US
Starting Propensity and Starting Evidence values should be persisted on check-in, if they do not then I'd suspect a defect.
However, why do you need to use these? What version are you using?
We no longer use the propensity smoothing algorithm and now use Thompson Sampling instead.
Starting Propensity is only used when AI is turned off for an action or the action is Transactional. StartingEvidence is no longer used.
Achmea
NL
@hellc We are using Pega marketing 7.3. We want to use smooth propensity in relationship to our offers. It seems that we are not able to fill the fields in the offer rule.
I would expect some sort of validation error at the time of creating the offer. Pega let's met fill those fields and then they disappear after i reopen te rule.
Pegasystems Inc.
IN
@MohamedA9221 Can you check and confirm if Smooth propensity property is present in the Decision data’s form tab of that issue/group?
Also what applications do you have in your stack?
Achmea
NL
@RaghuShankhawaram We added that property in the decision data form. What do we do know. It still does not work the way we want it. Maybe it is an actual Pega bug?