Question
Verizon
US
Last activity: 29 Jun 2021 16:39 EDT
Champion Challenger Percentage as a Variable
Hi,
We want to use the Champion Challenger capabilities in Pega but we would like the ability to change the Percentage on the fly without a code change needed in production.
Is there a way to put a variable in the Percentage fields so we can just change the variable value in our configurations? This way we can make a change to the split at any time in production.
Thank you!
Emirates NBD
IN
@WilliamH9689 :Did you find any work around ?
Verizon
US
@SIREESHA kNo work around that I know of. Has to be a code change/deployment to increase or decrease the percentage for Champion/Challenger.
Maybe Pega can look into allowing variables to be used for this functionality.
Pegasystems Inc.
US
@WilliamH9689 Instead of using the Champion/Challenger component, try this design.
Create a Dynamic System Setting that holds the percentage value you'd like to be able to change on the fly. Using a DSS allows you to make a change directly in production without a release, without changing any strategy logic.
Next, add a Set Property component to the strategy canvas outside of the main decision path. Use this Set Property component to capture the value(s) of the setting(s) you just created into SR properties. Browse the list for the correct formula, I think it's something like GetSystemSetting (not exactly that).
Next, add a Set Property component in the place in the strategy where you wanted to add a Champion/Challenger. Use the below formula to set the value of a true/false SR property. The formula returns "true" for a random X% of records.
(X/@Math.Log(1-@random())) < ((100-X)/@Math.Log(1-@random()))
Simply replace X in the formula with the SR property that holds the value of the DSS setting.
After that, add filters to handle instances where the result is true vs. false differently.
@WilliamH9689 Instead of using the Champion/Challenger component, try this design.
Create a Dynamic System Setting that holds the percentage value you'd like to be able to change on the fly. Using a DSS allows you to make a change directly in production without a release, without changing any strategy logic.
Next, add a Set Property component to the strategy canvas outside of the main decision path. Use this Set Property component to capture the value(s) of the setting(s) you just created into SR properties. Browse the list for the correct formula, I think it's something like GetSystemSetting (not exactly that).
Next, add a Set Property component in the place in the strategy where you wanted to add a Champion/Challenger. Use the below formula to set the value of a true/false SR property. The formula returns "true" for a random X% of records.
(X/@Math.Log(1-@random())) < ((100-X)/@Math.Log(1-@random()))
Simply replace X in the formula with the SR property that holds the value of the DSS setting.
After that, add filters to handle instances where the result is true vs. false differently.
If you need to validate that this works, you can do so using a data flow. Create a strategy rule with the above setup, but instead of adding filters at the end, just allow all instances to pass to the results component. Then create a Monte Carlo data set to use as the source for a data flow that passes the Monte Carlo data through the strategy rule you just built. When the property value is "true" have the strategy output pass through one filter in the first branch. When the value is "false" have it pass through another filter in a second branch in the data flow. When you run the data flow, the "true" filter should allow X% of records to pass through, the false should allow 100-X%.