Hello we want to implement a case heirarchy where the parent and the child case both belong to different class groups and work table. What this means is
Parent case mapped to Class group FW-Work-ParentCaseClass, which is mapped to work table PC_ParentCase_WorkTable.
Child Case1 mapped to Class group FW-Work-ChildCaseClass which is mapped to work table PC_ChildCase_WorkTable.
I read in the documentation that one application maps to one workpool which in turn maps to one work table. Want to understand if that is the best practice or if i can have multiple work tables for child cases for a given parent case.
Are there any issues that i should be think of before going in this path.
I haven't done this myself, so I can't say for certain, but I believe you can set up a Data-Admin-DB-Table record for any class to map it to another table. My guess is that you might have problems with some of the OOTB wizards if you do that, because they expect certain things which may not be true in your case anymore. But taking a step back, why are you looking to do this? If there is a specific business problem you need to solve, there may be a better way.
Posted: 4 years ago
Posted: 24 Aug 2017 12:46 EDT
L. Venkateswara Kotikalapudi (kotil)
Senior Principal Software Engineer, Low-Code