SA-6799

Summary

We want to store different work objects in different database tables, however the work objects belong to same work pool/class group.

When we create a separate database table for the classes, they are gnored and the objects still get written to the table of the work pool/class group.

Resolution

Per the documentation, work items in one class group are stored in the same table by design.  If your business requirements dictate otherwise, you should separate them in the class structure too.

All instances of classes that are associated with a class group share a common key definition and common lock definition. This allows the database software (such as, Oracle or Microsoft SQL Server) to save the instances as rows in one table in the PegaRULES database.

The common key format also ensures that the same database table is accessed when an instance is converted from one class (within a class group) to another class (in that same class group). For example, a work item may initially be entered incorrectly as a merchandise order, but later be reclassified as a merchandise return request. Both work types have the same key structure and belong to a common work pool (class group).

https://pdn.pega.com/sites/default/files/help_v71/procomhelpmain.htm#data-/data-admin-/data-admin-db-/data-admin-db-classgroup/related.htm