Question

6
Replies
75
Views
PaulNFord Member since 2019 5 posts
Ford Motor Company
Posted: August 28, 2019
Last activity: September 10, 2019
Closed
Solved

Proposition Hierarchy showing incorrectly post refactoring

The original Artifacts ruleset was being used incorrectly, and contained a large number of rules, not just those created by the outbound marketing Wizard processes.

a new Artifacts ruleset was created and ALL active rules were refactored into various ruleset locations.

classes were also moved to new ruleset locations

the old Artifacts ruleset was removed from the Application stack.

the Extract marker was removed and the Application servers restarted.

some of the proposition groups were missing in the hierarchy (proposition landing page), but were visible in the app explorer, the class existed, and the decision data existed, they just did not show in the on the proposition landing page.

a manual delete and recreate action was performed in the dev environment, which addressed the issue, but is a pain to do.

when the product package was build and deployed to the QA environment, the same problem existed. the classes and Decision data were present, but the offer group did not show in the landing page.

is there some other link (other than just having the class, and the decision data rules available) that is required to have to propositions show on the landing page correctly.

see the attached image for an example

***Moderator Edit-Vidyaranjan: Updated SR details***

Pega Marketing Decision Management SR Parallel
Moderation Team has archived post
Share this page LinkedIn