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***
Accepted Solution
Ford Motor Company
CA
so ... it turns out that the Class has metadata which controls visibility.
open the CLASS for a particular Issue or Group and go to the history Tab.
for an Issue pyDecisioningItem is set to "Issue"
for a Group pyDecisioningItem is set to "Group" and pyDecisionParametersRule is set to the name of the Decision Data Rule
When an Issue or Group is Deleted the value of pyDecisioningItem is set to "MarkedForDeletion"
so ... it turns out that the Class has metadata which controls visibility.
open the CLASS for a particular Issue or Group and go to the history Tab.
for an Issue pyDecisioningItem is set to "Issue"
for a Group pyDecisioningItem is set to "Group" and pyDecisionParametersRule is set to the name of the Decision Data Rule
When an Issue or Group is Deleted the value of pyDecisioningItem is set to "MarkedForDeletion"
if you change this value back to "Issue" or "Group" it will be re-instated in the hierarchy.
Pegasystems Inc.
IN
Hi @PaulNFord ,
Once you arrive at the resolution, please feel free to share the resolution here in the community. It helps other community users who face the same issue.
Thanks.
Ford Motor Company
CA
I suppose the same scenario would apply if you delete an issue/group on the Proposition Landing page. it will be gone from the hierarchy, but the class and the decision data rule still exist, as can be seen in the app explorer. but you cannot add them back into the hierarchy, as Pega just states that it already exists. So there is some other component that links the Decision Data to the landing page ... I gather that is what I am after. otherwise we have to delete the Decision Data rule and recreate it by adding the issue/group back on the Proposition Landing page. this requires you to re-associate the desired properties, and to re-create a custom form if one exists, and then to re-import the proposition data (assuming you first had an export of the propositions in the first place)
Ford Motor Company
CA
so I realize you can manually fix this, but it is cumbersome, and you may (probably will) have locked rulesets ...
instead of doing the following (for each missing group) there really should be a way to link up the hierarchy back to the decision data that is left orphaned behind. Surely this is possible ...
Process …
- Manually delete the decision data
- Manually delete the class
- (re)Create the group on the proposition landing page
- Add any customer properties back, and select them as form properties
- Add pyIsActive as a form property
- Import the data as exported (which you will have had to have backup up first)
- Remove unneeded form properties
- Check in.
Accepted Solution
Ford Motor Company
CA
so ... it turns out that the Class has metadata which controls visibility.
open the CLASS for a particular Issue or Group and go to the history Tab.
for an Issue pyDecisioningItem is set to "Issue"
for a Group pyDecisioningItem is set to "Group" and pyDecisionParametersRule is set to the name of the Decision Data Rule
When an Issue or Group is Deleted the value of pyDecisioningItem is set to "MarkedForDeletion"
so ... it turns out that the Class has metadata which controls visibility.
open the CLASS for a particular Issue or Group and go to the history Tab.
for an Issue pyDecisioningItem is set to "Issue"
for a Group pyDecisioningItem is set to "Group" and pyDecisionParametersRule is set to the name of the Decision Data Rule
When an Issue or Group is Deleted the value of pyDecisioningItem is set to "MarkedForDeletion"
if you change this value back to "Issue" or "Group" it will be re-instated in the hierarchy.