What is the relationship between X-Y-Data class and X-Y-SR class?
1. In the exercise, in the 'Approach' section (1st paragraph), it says to open the Next Best Label strategy from the DMOrg-DMSample-Data-Customer class, whereas in the setup data it is in the DMOrg-DMSampleDSE-Data class. I'm sure you will want to correct one or the other...
Which brings me on to my real questions:
2. In the Decision Strategy Essentials course it recommends putting decision strategies into the customer data class (i.e. X-Y-Data-Customer) but you didn't do this in this exercise.
What is the best practice for the class of a decision stategy?
3. In this exercise the properties we use (i.e. Cost, Average, Margin, etc) are defined in the DMOrg-DMSampleDSE-SR class, but this class is not a parent of DMOrg-DMSampleDSE-Data.
Sorry for being a bit thick but how can these properties be available to a strategy if they are not on the inheritance path of the strategy's class?
What exactly is the relationship between the X-Y-Data class and the corresponding X-Y-SR class?
Pegasystems Inc.
GB
Further to what I just wrote I notice that in a Decision Table strategy component you can even choose whether you use the Applies To class (of the strategy) or the Strategy Result (SR) class.
Pegasystems Inc.
NL
Rob,
This is a very good question.
1. First of all you have indeed spotted a typo. The correct Applies to class is: DMOrg-DMSampleDSE-Data . You will find this in the screenshot and solution video too.
2. In general we alway recommend to put all strategies on the Customer class (more precisely Customer data model). In this case the customer class is: DMOrg-DMSampleDSE-Data .
In case of multi-level decisioning you might see stratgies defined on embeded pages of the Customer class. That is fine too.
Avoid using PAges&Classes!
For eligibility criterias as you very well noticed we do use decision table defined on SR class. But that is not a strategy. The actual strategy it's still defined on the customer class and its referencing the decision table defined on SR class.
We can pass the entire Customer data model to the decision table. This the the a good practice, and we encourage this pattern.
3. You have very well noticed there are 2 important classes when it comes to designing a strategy. One is the Applies to class, which again, contains all customer data model. This would typically contain profile info, transactions, product holding etc. Sometimes Customer class could actually represent an Account (for multi level).
Rob,
This is a very good question.
1. First of all you have indeed spotted a typo. The correct Applies to class is: DMOrg-DMSampleDSE-Data . You will find this in the screenshot and solution video too.
2. In general we alway recommend to put all strategies on the Customer class (more precisely Customer data model). In this case the customer class is: DMOrg-DMSampleDSE-Data .
In case of multi-level decisioning you might see stratgies defined on embeded pages of the Customer class. That is fine too.
Avoid using PAges&Classes!
For eligibility criterias as you very well noticed we do use decision table defined on SR class. But that is not a strategy. The actual strategy it's still defined on the customer class and its referencing the decision table defined on SR class.
We can pass the entire Customer data model to the decision table. This the the a good practice, and we encourage this pattern.
3. You have very well noticed there are 2 important classes when it comes to designing a strategy. One is the Applies to class, which again, contains all customer data model. This would typically contain profile info, transactions, product holding etc. Sometimes Customer class could actually represent an Account (for multi level).
Second class is the SR class. This is the class which we propagate in stratgies from one component to another. Every decisioning component is setting some of the SR properties and it propagates a list of SR results.
In a strategy SR properties are available using dot operator ".". E.g. .Cost, .Margin etc. Properties from Customer class are available with "Primary." construct. E.g. Primary.Age.
The Customer and SR class have no relationship. They are both independent, in sepparate hierarchy.