How to detect when a work object is saved to the pr_other table (PEGA0041 alert)

The alert occurs when a work object is saved to the PegaRULES database and is stored in the pr_other table, instead of the standard pc_work table or another table identified in a DB table data instance. (The pr_other table is the default catch-all table for instances of classes 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 pr_other for work object 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 may have unpredictable behavior.

Alert log message

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

Alert settings

This alert has no configurable settings in prconfig.xml.

Next step

Create the correct Data-Admin-DB-Table instance for the relevant class group class (pc_work or a copy). See the Pega Developer Network article PRKB-20451: Troubleshooting: Work objects incorrectly saved into the pr_other table.

	alert log, prconfig.xml file
	Understanding alerts Working with the PegaRULES database — Tables for work objects Atlas — Initial Database Tables (Data-Admin-DB-Table) About Database Table data instances

SysAdmin category