Question
Cognizant
CH
Last activity: 4 Oct 2017 2:28 EDT
How to delete / hide a class from a specific ruleset version?
Hi,
During development I refactored the application's data structure and that resulted in a class being obsolete. I would like to delete / hide that specific class from App Explorer without unlocking all of the previous rulesets.
Note:
- I am aware of the Delete Class Wizzard: https://pdn.pega.com/how-delete-class-v55
- There is a similar question on PDN, but it does not mention a solution: https://pdn.pega.com/community/product-support/question/can-we-delete-class-without-unlocking-rulesets-manually
Concrete example:
Ruleset version 0.0.1:
Org
└──Org-Int
└── Org-Int-Document
Ruleset version 0.0.51:
Hi,
During development I refactored the application's data structure and that resulted in a class being obsolete. I would like to delete / hide that specific class from App Explorer without unlocking all of the previous rulesets.
Note:
- I am aware of the Delete Class Wizzard: https://pdn.pega.com/how-delete-class-v55
- There is a similar question on PDN, but it does not mention a solution: https://pdn.pega.com/community/product-support/question/can-we-delete-class-without-unlocking-rulesets-manually
Concrete example:
Ruleset version 0.0.1:
Org
└──Org-Int
└── Org-Int-Document
Ruleset version 0.0.51:
- Rulesets from 0.0.1 to 0.0.50 are locked.
- I realized that there are more document-related classes needed and I would like to logically group them under a parent class.
- Org-Int-Document class was moved (recreated) under Org-Int-DocumentManagement.
- Let's say, all the classes are abstract, they only act as data structure, there is no need for data migration.
Org
└──Org-Int
├── Org-Int-Document <-- This is obsolete, it was moved under DocumentManagement
└── Org-Int-DocumentManagement
├── Org-Int-DocumentManagement-Document
└── Org-Int-DocumentManagement-DocumentVersion
How to solve that, how to delete / hide the obsolete Org-Int-Document class from Ruleset version 0.0.51?
I know there is no simple solution for that in Pega.
I would like to ask what is the Pega way to solve this task, is there an existing coding pattern / guideline in the Pega community?
Best regards,
Attila