CDH Taxonmy - Deleted Group causes class error
Hi,
After deleting a group via Configure > Decisioning > Decisions > Proposition Management > Hierarchy (in dev studio), the class is still referenced from the CDH portal's taxonomy page.
Error messages
System configuration incompatible with Next-Best-Action Designer Taxonomy:
The class CRI-SR-NurtureandBranding-informativo has been removed from your application. The group "informativo" defined on the Taxonomy is no longer accessible by your application.
Steps to reproduce
- Create a group under an issue.
- Delete the group via dev studio Configure > Decisioning > Decisions > Proposition Management > Hierarchy then click the trash icon next to the created group.
- Open up NBA designer in the CDH portal and navigate to taxomomy. An error message will populate the top of the screen. Taxonomy will no longer be editable
Accepted Solution
Updated: 28 Jan 2025 3:39 EST
HCA Healthcare
US
Adqura
TR
@Sairohith thanks for detailed explanation
When issue is occured All Edit and Save buttons becamed disabled so tried to solve issue on background bu refactoring classes which caused more problem.
So as a first step to the steps you provided, we first enabled edit and save buttons on Live UI. After removing references for group and the related issue taxonmy is sorted. Then we discard the sections we changed for buttons.
Thanks again
@FusunD27 To resolve the issue of a deleted group causing a class error in the Taxonomy of Pega's CDH, first, open the Taxonomy page in NBA Designer and remove references to the deleted group. Then, refresh the Proposition Management hierarchy in Dev Studio to ensure no residual references exist. Clear the cache in Admin Studio and restart the System Pulse to sync the changes across nodes. Next, rebuild decision data under Decisioning > Data Management to align the taxonomy with the updated class hierarchy. Additionally, check the database tables, such as
pr_data_ih_hierarchyandpr_data_nba_taxonomy, for any stale references to the deleted group and remove them if found. To prevent this issue in the future, always delete groups through the NBA Designer or Proposition Management UI instead of Dev Studio to keep the hierarchy and taxonomy in sync. Ensure users have the necessary access rights, use rulesets to version changes, and periodically audit the taxonomy for consistency. This will address the error and maintain a smooth workflow in CDH