Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

All classes in a class group map to one shared database table

Updated on September 13, 2021

Summary

A developer asks: We have a class group that has several individual classes (work types in one work pool). Some columns we want to expose for some work types are not present in other work types.

Can we specify separate, distinct Data-Admin-DB-Table definitions for each individual class?

Suggested Approach

This is not possible, by definition of class group.

The purpose a of class group is to group the individual member classes into one shared database table.  One Data-Admin-DB-Table, therefore, maps the entire class group; you can't place member classes into distinct tables.

This design simplifies access for reporting and searching across work types, and allows a work object initially created in one work type to be updated into another work type.

For example, a mail room intake process may create very generic work objects by scanning images from arriving mail. Upon more detailed human review of the scanned images, the work objects may be assigned more specific work type (Accounts Recievable, Customer Complaint, and so on) based on the document content. Both the generic work objects and all the specific work objects are saved in a single table.

  • Previous topic Accessing database administration operations
  • Next topic An Entity-Relationship Diagram for work object tables in the PegaRULES database

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us