Question
Rulesware LLC
MX
Last activity: 3 Jun 2020 10:47 EDT
NBA Designer lost synchronization with auto-generated rules (Strategies and proposition filters)
Our NBA Designer lost synchronization with the strategies in <MyOrg>-Data-Customer, by this synchronization what I mean is that even if I remove for Engagement Policies for a group, let say Retention-Proactive, the actions from the group are returned in the response, in this case NBA_Retention_Proactive is not reset, instead is keeps the configuration as in the group level template, similar scenario for the proposition filters, if a proposition filter is added by adding a condition in any Eligibility, Applicability or Sustainability policies and later the condition is remove with the NBA Designer, then the auto-generated proposition filter remains in the system and being referenced by the group level strategy.
How can I delete the group strategy (group level engagement configuration) or once it is created the only option is to edit the auto-generated components?
As reference for NBA Framework’s auto-generated components I am using: https://community.pega.com/knowledgebase/articles/pega-marketing/understanding-next-best-action-strategy-framework#Group
Accepted Solution
Updated: 3 Jun 2020 10:47 EDT
Pegasystems Inc.
US
Hi Javier,
Apologies for the delay. I think there may have been a tiny miscommunication regarding proposition filters. In your initial post, you mentioned removing the condition from NBA Designer, and that was what I was responding to. If you instead delete the entire Engagement Policy, the proposition filters will remain as they were before, and you would have to re-save the Taxonomy to remove the filtering strategy from the framework. Alternatively, as you found, you can save the Engagement Policy without adding any conditions in order to allow everything to pass through.
To put it more succinctly, the act of deleting an Engagement Policy does not update backing strategies or proposition filters.
- Josh
Updated: 27 May 2020 15:49 EDT
Pegasystems Inc.
US
Hello Francisco Javier. What version of Customer Decision Hub / Pega Marketing are you using? I see a tag for Pega Marketing for Financial Services 8.4 but would like to confirm.
Updated: 28 May 2020 11:15 EDT
Rulesware LLC
MX
Hello MarioBatres yes, that's correct. I am using Pega Platform 8.4, with an implementation of Pega Marketing For Financial Services version 8.4.
Pegasystems Inc.
US
Hello! I think I can help you navigate some of this.
As you noticed, the group strategy will remain in play upon deleting the group Engagement Policy. The easiest way to clean this up is to edit your Taxonomy, remove the group from the Taxonomy for which you deleted the Engagement Policy, and then save the Taxonomy. This should regenerate the backbone strategies so that the strategy for your deleted group is no longer referenced. The group level strategy will still exist as it was previously defined, so please be mindful of this if you add the group back to the Taxonomy at any point. That said, if the group has been removed from the Taxonomy, you should feel free to manually delete the group strategy from the system.
With regard to the proposition filters, it is expected behavior that the generated proposition filters will continue to exist even if you remove the conditions from the Engagement Policy. However, this should not have any impact on the runtime outcomes of the strategies. When you clear the conditions from the Engagement Policy, the backing proposition filter should be updated so that by default, it does not perform any filtering (default behavior returns "true") and all propositions pass through as if no filter was there.
Hopefully this addresses your question. Please let me know if I can be of any more help!
- Josh
Updated: 28 May 2020 20:28 EDT
Rulesware LLC
MX
Hi Josh ( @planj )
Thank you for the quick response
As you mentioned, after removing the group from the taxonomy, I removed the group strategy. Adding the group back forced the creation of the default empty strategy, then when I added the Eligibility condition in Engagement Policies thru the NBA Designer then the NBA updated the strategy to follow the framework pattern as expected.
In regards with the Proposition filters, did not work as I understood your explanation. I removed the Engagement Policies component for the group from the NBA Designer, this did not update the PF to default, instead left the custom criteria as is was before the remove.
Then I added the Engagement Policies for the group, it did not load the PF configuration for filling the Eligibility condition. If I request the NBAContainer I got the filtered action even when the UI did not show the condition, here is where the synchronization between the NBA and the PF is lost.
Later I added eligibility condition back thru the NBA Designer save, and finally edit it again, this time remove only the eligibility condition, with this steps I got the scenario that you mentioned before and the PF, eligibility PF in my case, was return to default
Hi Josh ( @planj )
Thank you for the quick response
As you mentioned, after removing the group from the taxonomy, I removed the group strategy. Adding the group back forced the creation of the default empty strategy, then when I added the Eligibility condition in Engagement Policies thru the NBA Designer then the NBA updated the strategy to follow the framework pattern as expected.
In regards with the Proposition filters, did not work as I understood your explanation. I removed the Engagement Policies component for the group from the NBA Designer, this did not update the PF to default, instead left the custom criteria as is was before the remove.
Then I added the Engagement Policies for the group, it did not load the PF configuration for filling the Eligibility condition. If I request the NBAContainer I got the filtered action even when the UI did not show the condition, here is where the synchronization between the NBA and the PF is lost.
Later I added eligibility condition back thru the NBA Designer save, and finally edit it again, this time remove only the eligibility condition, with this steps I got the scenario that you mentioned before and the PF, eligibility PF in my case, was return to default
My understanding is that if the whole Engagement Policy component for a group is deleted in the NBA Designer, all the PFs referenced by that group should be restored to default, which is what happens when an individual condition is removed without removing the Engagement Component from for the group.
Is it a correct statement?
Best regards
-Javier
Accepted Solution
Updated: 3 Jun 2020 10:47 EDT
Pegasystems Inc.
US
Hi Javier,
Apologies for the delay. I think there may have been a tiny miscommunication regarding proposition filters. In your initial post, you mentioned removing the condition from NBA Designer, and that was what I was responding to. If you instead delete the entire Engagement Policy, the proposition filters will remain as they were before, and you would have to re-save the Taxonomy to remove the filtering strategy from the framework. Alternatively, as you found, you can save the Engagement Policy without adding any conditions in order to allow everything to pass through.
To put it more succinctly, the act of deleting an Engagement Policy does not update backing strategies or proposition filters.
- Josh
Rulesware LLC
MX
Hi Josh,
Thanks for the response now I have clear the behavior of the NBA Designer under the three scenarios:
1.- Deleting the entire Engagement Policies
2.- Deleting a condition inside the engagement policies (E, A, S, C)
3.- Removing the group from the taxonomy
Best regards
-Javier