Support Article
Classes saved with pyRecordHistorySnapshots errors
SA-34451
Summary
User is unable to import a product file into another environment because classes have been saved with errors referencing an undefined property pyRecordHistorySnapshots.
Error Messages
2017-03-01 00:25:20,753 [ PegaRULES-Batch-2] [ STANDARD] [ ] [ MyUsername:07.21] ( internal.loaders.SaverLoader) INFO CSCSysAdmin - Saved of RULE-OBJ-CLASS MY-FW-TROUBLEFW-WORK-GRP1-MYCLASS failed.
com.pega.pegarules.pub.database.BadInputException: Trying to save an invalid page: The page contains an undefined property: NewFWWorkTypeClass.pyRecordHistorySnapshots
Validation failed: Errors Detected.
Steps to Reproduce
Exact reproduction steps are not known. There was some use of the Application Accelerator.
Root Cause
The issue occurred due to the error stored in the class rule.
Further investigation suggests the original error was stored in the classes during the use of the Application Accelerator.
The NewFWWorkTypeClass page in the error message is the name of the step page used in activity Rule-Obj-Class.pzCopyFrameworkWorkType.
The page is referenced in step 11 where it does a Page-New with the comment saying "New page for the FW work type".
Resolution
Modifying the revalidate tool so the classes can be resaved without the errors, to resolve follow these steps:
- Perform a private checkout of the @baseclass.BulkValidateSave activity and do a Page-Clear-Messages after the Obj-Open-by-Handle.
- Run the revalidate tool found in DesignerStudio > System > Release > Upgrade > Validate > Revalidate and Save.
Published March 16, 2017 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.