Property created in proposition management landing page is not visible in strategy (updating AssitedTreatmentStrategy)
Following this for adding new properties to treatments and our action decision data, I encountered an issue where the properties we created under the top level context (SR level) is not in the Data-pxStrategyResult class. Is this not something that is done automatically by the system?
As a result, when attempting to update our AssistedTreatmentStrategy to reference the new treatment properties for our data join, we are unable to find it and I am not sure if I am to manually create the property strategy first prior to attempting to use it or did I miss a step in the instructions when creating a new property.
I referred to this user doc guide.
CXForward
CA
One thing to note is that the way I can get around this is when saving the OOTB strategy, I uncheck the checkbox where we define the strategy on Data-pxStrategyResult, by leaving the issue/group as none/blank, the properties of the SR class are picked up. Is this what has to be done? Wanted to ensure I did this correctly.
CXForward
CA
I stand corrected, in the join treatment metadata component, even if saving the rule in my SR class rather than Data-pxStrategyResult, the source is unable to find the properties that were auto-mapped from the decision data import.
Strategy in context: AssistedTreatmentStrategy
Pegasystems Inc.
IN
@AN-PEGA Can you please confirm if you have saved as the AssistedTreatmentStrategy under your Top Level SR class or under Data-pxStrategyResult class? I think you need to save it under your applications Top Level SR class.
CXForward
CA
@RaghuShankhawaram I unchecked define on a custom Strategy Result class instead
Pegasystems Inc.
IN
Let me correct and clarify my above comment, I meant to save that when you save as the strategy, it should be under the same applies to class but we should configure the applications top-level SR class in the "Define on a custom Strategy Result class instead" field and open the Decision data shape and reselect the decision data or remap the properties.
CXForward
CA
@RaghuShankhawaram in the field where we input the custom Strategy Result class, when setting the value in the text box to our top level class, the issue is now resolved!
Is there somewhere in any guide that I might have missed this step? Happy to have resolved this but unsure if any steps were missed following the user guide.
There are also the steps to extend the response of the real time container but it seems incomplete or I am not quite following (step 7.1 to 7.7) of https://docs.pega.com/pega-customer-decision-hub-user-guide/86/frequently-asked-questions-about-treatments
The steps in the above guide differ slightly from this one that I have used in the past: https://docs-previous.pega.com/pega-customer-decision-hub-implementation-guide/85/setting-custom-property-real-time-container-response
For updating and extending the data transform, I have saved it into my top level SR class (applies to) and implementation ruleset.