Two class groups are mapped to single Table- Will there be any issue ?
We have a application where two different 'is a class group' classes are mapped to single data base table.
By doing this way will there be any issues with work object save/commit ?
Some time we observe that these two classes - class group instances (Data-Admin-DB-ClassGroup) instances are getting deleted automatically by pega - and observe locking warning on save open of work objects ---- we are not sure how they are getting removed ?
Can we know the reason for this behaviour ?
Accepted Solution
Aaseya IT Solutions
IN
There is no technical problem, but you will end up creating a very bad data model for your work class.
Reporting on work objects and other operational reports may not give you desired output.
Coming to the errors you are encountering, they are not related to them mapping to same table.
Pegasystems Inc.
US
Hello,
As long as the two class groups won't ever try and generate the same pzInsKey, I don't see any reason why you shouldn't be able to put them both in the same table.
I don't have enough context to comment on the locking issues/class groups being deleted by the system, so it's possible I'm wrong and the root of that is why. Or possibly, if they are both generating the same lock key or something, then that's a problem that you could understand and then tweak to avoid.
Thanks,
Mike
Accepted Solution
Aaseya IT Solutions
IN
There is no technical problem, but you will end up creating a very bad data model for your work class.
Reporting on work objects and other operational reports may not give you desired output.
Coming to the errors you are encountering, they are not related to them mapping to same table.