Question
Maantic Inc
US
Last activity: 26 Aug 2019 13:28 EDT
How to handle class group change for existing work object data and rules?
Hi,
For production live application, want to change the class group. how to handle class group change for existing work object data and rules? do we have any optimized process in Pega?
***Edited by Moderator: Lochan to branch reply to create new post***
Pegasystems Inc.
US
Hello,
I'm not sure I understand exactly what you are trying to do, though I suspect there isn't a handy tool to do it and you will need to do a bit of work on your own. Are you trying to turn your class into a class group, or switch it from class group A to class group B? What is the driver behind this? Do you want the data in a different database table? Are all your exposed columns available in the new class group? I suspect that is really the thing that will drive the conversation most.
Thanks,
Mike
Maantic Inc
US
Hi Mike,
Switch it from class group A to class group B?
Yes, switching from A (Existing Class Group) to B (New Class Group)
Do you want the data in a different database table?
Same database, different table
Are all your exposed columns available in the new class group?
Yes, all the exposed columns are available in new table
What is the driver behind this?
Application having 15 different case types, all the case type work objects are stored in one work table. it is causing performance issue though database have all the required indexes in work table
Our goal is each case type work object should be stored in separate work table, we believe it will resolve the performance issue.
Current class structure
ABC-ORG-DIV- WORK – Class group – pointing to PC_WORK
ABC-ORG-DIV- WORK-CASETYPE1 – Belongs to Class Group
ABC-ORG-DIV- WORK-CASETYPE2 – Belongs to Class Group
ABC-ORG-DIV- WORK-CASETYPE3 – Belongs to Class Group
ABC-ORG-DIV- WORK-CASETYPE2 – Belongs to Class Group
Proposed class structure
ABC-ORG-DIV- WORK – Class group – pointing to table PC_WORK
ABC-ORG-DIV- WORK-CASETYPE1 – Belongs to Class Group
Hi Mike,
Switch it from class group A to class group B?
Yes, switching from A (Existing Class Group) to B (New Class Group)
Do you want the data in a different database table?
Same database, different table
Are all your exposed columns available in the new class group?
Yes, all the exposed columns are available in new table
What is the driver behind this?
Application having 15 different case types, all the case type work objects are stored in one work table. it is causing performance issue though database have all the required indexes in work table
Our goal is each case type work object should be stored in separate work table, we believe it will resolve the performance issue.
Current class structure
ABC-ORG-DIV- WORK – Class group – pointing to PC_WORK
ABC-ORG-DIV- WORK-CASETYPE1 – Belongs to Class Group
ABC-ORG-DIV- WORK-CASETYPE2 – Belongs to Class Group
ABC-ORG-DIV- WORK-CASETYPE3 – Belongs to Class Group
ABC-ORG-DIV- WORK-CASETYPE2 – Belongs to Class Group
Proposed class structure
ABC-ORG-DIV- WORK – Class group – pointing to table PC_WORK
ABC-ORG-DIV- WORK-CASETYPE1 – Belongs to Class Group
ABC-ORG-DIV- WORK-CASETYPE3 – Belongs to Class Group
ABC-ORG-DIV- WORK-CASETYPE2 – is Class Group – pointing to table - PC_WORK_TYPE2
ABC-ORG-DIV- WORK-CASETYPE4 – is Class Group – pointing to table - PC_WORK_TYPE4
Questions are
1. Does pega have any OOTB to handle class group changes ? to automatically update related rules and data
2. After the class structure (class group) change, how to handle existing data in work table and history table?
(Part of the analysis, we found pzinskey need to updated in all the related tables, do we have any option to handle the existing data without updating pzinskey? )
3. How to handle rules (Report definition, etc..) in existing class group?