Change of Case/class structure
We have the above class structure in the application. We currently have the Proposal case and several sub cases under it.
we need to enhance it to have a Parent proposal on top of the Proposal case. What would be the best possible approach in terms of class structure?
Is there a way which handles both existing Proposals and the New proposals ?
We need a New parent as shown in the below case structure.
***Updated by Moderator: Vidyaranjan| Updated categories***
Pegasystems Inc.
US
Hello Thejasri,
I don't know if I fully understand what you are asking. Do you want to insert a class between classes, like below?
Org-US-App-Work
|
Org-US-App-Work-Parent
|
Org-US-App-Work-Proposal
I'm not sure where your subcases fit into this, since they weren't on the first diagram. Are they classes which inherit from Org-US-App-Work-Proposal? Would those need to change? I assume the "Parent" class isn't a required object, since your existing items aren't children of one. Are you expecting future items to be?
Assuming you're asking if you can do something like I diagramed above, yes. Obviously, anything at the Parent level that overides rules at the Work level will be inherited down at the Proposal layer (and below) so you'll want to keep an eye out for any suprises that might cause. Once you put the new class structure into production, existing items will inherit all of the Parent level rules. You could perhaps use things like circumstancing if you don't want that to happen all the time.
Thanks,
Mike