Value Finder requirements for strategies created outside of Next-Best-Action Designer
You can analyze a custom strategy that does not use the Next-Best-Action Designer strategy framework by running a Value Finder simulation test. Value Finder can analyze the custom strategy as long as it has the appropriate structure of eligibility rules and arbitration that contains propensities from adaptive models.
Pega Customer Decision Hub
Required fields
Ensure that the strategy results include the following fields and values:
- pyStage – This column must contain at least two values: Eligibility and Arbitration. You can leave the column empty when there are no actions for a customer after eligibility.
- pyPropensity – This column must contain the propensities as obtained from the adaptive model.
Previous topic Creating simulation tests in Pega Customer Decision Hub Next topic Value Finder requirements for data sets