One of our customer who were using Pega Decisioning in older version(7.1) would like to migrate in latest 8.6.
In their previous version business user has a portal(developed using Pega Case manager) to write business rule which in turn converted(programatically) into when condition in decisioning application.
Now here is the use case where we are facing some challanges while defineing Engagement rule in 8.6
Sample Rule which business user used to define in the existing application:
If the customer is from a particular state(lets say CA) the only make those offer eligible which has cost value from 1-20
Now in latest NBAD we define rule specific to proposition(disregarding rule with respect to issue/ group for the time being). So here business has to identify every proposition manually(according to cost attribute in offer) and write the rule for each proposition as "Customer in state CA".
Another example could be
If customer has some flag matches with container request flag then only make those offer eligible which has certain feature(Feature is an offer attribute with comma separated value)
Business user is not getting comfortable with that.
Is there any other ways? or Am I missing somthing?
It is undoubtedly a big move from 7.1 to 8.6 and will need some planning. Things have changed a lot. There are various resources available on community such as the CDH enablement series (I can't paste links in here but search CDH enablement series) that will help. Also there is plenty of training on Pega Academy which is well worth exploring first (especially the Operations Manager training)
To your points, categorization of engagement policies is extremely important and you should aim to plan this out correctly. Basically we have Eligibility, Applicability and Suitability at multiple levels in the Decision Framework and you should explore them all. Aim to do as much filtering of your actions as early in strategy execution as makes sense (e.g. All Actions, Group level and then Action Level).
Engagement policies that apply at action level tend to be specifically for that action, or a set of actions within that group. To avoid writing the same condition multiple times for a set of actions, you can still save a condition as a when rule and reference it in the condition builder to avoid writing the same condition multiple times.