[PEGA 7.1.6] Pega Marketing - Interaction History Only Evaluates Most Recent in Group By Aggregator
Hello,
In a Pega Marketing Strategy rule, I am pulling back all Interaction History for a specific customer for the past 31 Days. I am then using the Group By to set a flag to TRUE IF ANY of the Interaction History pyOutcome contains a certain value. However, it appears that the Group By aggregator only checks the most recent Interaction History...It works the first time, but not the second time. It should work all the time, as the Interaction History will always have an entry with that value as pyOutcome.
Can someone please explain why the Group By aggregator only evaluates against the most recent Interaction History and not all? I also checked the Parameter INTERACTION_HISTORY in the Clipboard, and that contains all Interaction History, including the value of interest, but still it does not work the second time.
I appreciate your assistance!
- Fran
Accepted Solution
Pegasystems Inc.
IN
Can you post a screenshot of your strategy so that folks can understand better and respond why you see a different behavior.
Pegasystems Inc.
AU
Hi,
Could you please elaborate further on your requirement? By providing screen-prints from your strategy canvas.
Also you can filter the pyOutcome values directly in the Interaction History component by providing the necessary condition.
Thanks,
Santhosh
Pegasystems Inc.
JP
Hello,
See attached for the Group By Aggregator screen shots.
If I pull back all Interaction History, this condition evaluates to false, if the last outcome was "Insurance B". It only evaluates to true if the last outcome was "Insurance A".
I can only achieve my requirement by doing as you suggest, and filtering on the Interaction History import. Unfortunately, this could lead to many Interaction History import shapes in my Strategy, if I need to know the profile of many different types of Interaction History.
I appreciate your help resolving/clarifying this issue.
Thank you!
Fran
Pegasystems Inc.
AU
Hi Fran,
I reviewed the Group By aggregator screen shot. And I see that you are comparing pyOutcome to a proposition.
Please note pyOutcome, contains the result of the interaction. Ideally the possible outcomes for the interaction (pyOutcome), are such as Accept, Accepted, Reject, Rejected, Pending etc. Could you please refer "Define Outcome" (Page No. 86) section under "About Interaction Rules" from the DSM getting started guide for more details. You may need to re-visit the strategy implementation as per this guide.
Hi Fran,
I reviewed the Group By aggregator screen shot. And I see that you are comparing pyOutcome to a proposition.
Please note pyOutcome, contains the result of the interaction. Ideally the possible outcomes for the interaction (pyOutcome), are such as Accept, Accepted, Reject, Rejected, Pending etc. Could you please refer "Define Outcome" (Page No. 86) section under "About Interaction Rules" from the DSM getting started guide for more details. You may need to re-visit the strategy implementation as per this guide.
Also request you to refer the Aggregation Category (Page No. 73) for more details on the usage of “Group By” components along with example.
Hope this helps!
Cheers,
Santhosh
Pegasystems Inc.
JP
Hi Santhosh,
Thank you for the detailed explanation. I will make sure to review my implementation. However, I would really appreciate a response to my specific question. When you pull back all Interaction History, using the Interaction History shape in a Strategy rule, why does it appear to only pull back the most recent interaction history entry?
I look forward to your response on this specific question.
Thank you!
- Fran
Pegasystems Inc.
AU
Hi Fran,
Are you having any filter condition in your Interaction History component?
Also in "Fetch interaction history for the last" field do not mention any number for the days. So that it will fetch all interaction history data.
Thanks,
Santhosh
Pegasystems Inc.
JP
Hi Santhosh,
I have done as you instructed (removed Interaction History filter and removed Day filter). I can see the full Interaction History in the Parameter Page, as a comma-separated list. Unfortunately, when I use in the Group By, with "TRUE IF ANY of Interaction History contains Insurance A", it returns true if most recent Interaction History is Insurance A and false if most recent Interaction History is Insurance B. This doesn't make sense, as the Interaction History in the Parameter Page clearly shows at least one instance where Insurance A was previously the outcome, so it should always return true for the above Group By condition.
Let me know your feedback.
Thank you!
Fran
Pegasystems Inc.
JP
Hello,
Can someone please assist with my question regarding reviewing the full interaction history versus most recent?
Please refer to the rest of this thread for background on what I am asking for.
Thank you!
Fran
Accepted Solution
Pegasystems Inc.
IN
Can you post a screenshot of your strategy so that folks can understand better and respond why you see a different behavior.