PEGA0041 alert: Work object written to the pr_other table

The PEGA0041 alert occurs when a work object is saved to the PegaRULES database and is stored as a row in the pr_other table, instead of in the standard pc_work table or another table identified in a database table data instance.

Example message text

The message identifies the class of work object that is being stored in the pr_other table.

Work object Sample-1 of class Work-Sample- is being written to pr_other

Reason for the alert

The pr_other table is the default table for instances of classes that are not explicitly mapped. The pr_other table has only a few exposed columns; it does not have columns for all the work object properties that are typically visible (exposed) as columns in a database table. Using the pr_other table for work objects is undesirable if your application requires frequent searching of rows of this table. Therefore, if you do not map a Work- class to an appropriate database table, your work objects might have unpredictable behavior.

Create the appropriate Data-Admin-DB-Table instance for the relevant class group and map it to the pc_work table or to a copy of that table.

Have a question? Get answers now.

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