Support Article

pyCommitError while attempting to save instance of class History

SA-33954

Summary



An activity that gets is called from a URL snapstart throws an error on screen after a call to Work-.commitWithErrorHandling.

Error Messages



pyCommitError:** Cannot save instance of class History-CustomClassName; it belongs to fully exposed table PEGADATA.pr_History_CustomClassName in database PegaDATA, but the instance has properties which do not correspond to columns: pyFlowName , pxAddedByID , pxAddedBySystem , pyFlowKey , pyMessageKey , pyFlowType


Steps to Reproduce

  1. In an activity, create a work object page, (actvity createWorkPage),
  2. Call activity WorkCommit. The error appears on the WorkCommit step.


Root Cause



The appropriate columns did not exist in the custom history table.

Resolution



Perform the following local change:
clone out of the box pc_history_work table onto the appropriate table name.

Published February 21, 2017 - Updated March 1, 2017


100% found this useful

Have a question? Get answers now.

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