Question

1
Replies
442
Views
 Attila Donath (AttilaDonath)
Cognizant
Pega Lead System Architect
Cognizant
CH
AttilaDonath Member since 2016 10 posts
Cognizant
Posted: October 3, 2017
Last activity: October 4, 2017
Posted: 3 Oct 2017 17:08 EDT
Last activity: 4 Oct 2017 2:28 EDT
Closed

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:


Concrete example:


Ruleset version 0.0.1:



Org
└──Org-Int
   └── Org-Int-Document


Ruleset version 0.0.51:

Show More

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:

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

Show Less
Low-Code App Development Enterprise Application Development Dev/Designer Studio
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Posted: 3 years ago
Posted: 4 Oct 2017 2:28 EDT
Gisela Rodrigues (rodrg)
PEGA
Technical Lead, Global Client Support
Pegasystems Inc.
IN

Hello,


As mentioned in the post https://pdn.pega.com/community/product-support/question/can-we-delete-class-without-unlocking-rulesets-manually, there is no way to delete a class without unlocking the rulesets. There is no existing coding pattern to do so. This has thus been raised as an enhancement to the Product.


Regarding hiding a class, I see that is not possible too unless you rename the class to something else (if there is not data ) and use the renamed class to develop the application further.


When complete, the renaming wizard changes your system in the following ways:


  • The class is renamed.

  • Direct and pattern inheritance references the new class name. As a result, there will be no effect on rule resolution.

  • If the option has been selected, Work- instances associated with the class are renamed.

  • All properties, activities, flows, and other rules that referenced the original class now reference the class by the new name.

  • If the class is a work pool or defines an external data table, the Data-Admin-DB-Table instance is updated to reflect the new class name.

  • The wizard creates a new History- class for the new class, and it will identify that the class has been renamed. The History- class for the old class name is deleted.

If there is another way, someone will surely post it out here for you.


Thanks,


Gisela