Skip to main content

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.

Support Article

Internal Error message get displayed when adding a Note

SA-28611

Summary



User has implemented the following scenario: 

1. User initiates a screenflow. Adds notes in OOTB Notes section. 
2. Then user moves to the next screen, and eventually submits the work object. 
3. User then logs off from PRPC. 
4. Another user logs in (say the first user's manager). There is a "Recall" button, which is used by this other user to recall (or open) the above submitted work object. 
PS: On click of "Recall" button, OOTB pxTransferCaseOwners activity is executed, which allows the other user to open the work object. 
5. Now, when the other user recalls the work object, and adds a note on the same screen, they encounter the following error. 

** internal error while copying page: exception caught during invocation of PRObjectWrapper.prGet() for Java Property pxObjClass. Message: null: code: <none> SQLState: <none> Message: <none> 

Failed To Save Note attachment: 



Error Messages



** internal error while copying page: exception caught during invocation of PRObjectWrapper.prGet() for Java Property pxObjClass. Message: null: code: <none> SQLState: <none> Message: <none>
Failed To Save Note attachment:


Steps to Reproduce



1. User initiates a screenflow. Adds notes in OOTB Notes section. 
2. Then user moves to the next screen, and eventually submits the work object. 
3. User then logs off from PRPC. 
4. Another user logs in (say the first user's manager). There is a "Recall" button, which is used by this other user to recall (or open) the above submitted work object. 
PS: On click of "Recall" button, OOTB pxTransferCaseOwners activity is executed, which allows the other user to open the work object. 
5. Now, when the other user recalls the work object, and adds a note on the same screen, they encounter the following error. 


Root Cause



While doing a call to autopopulate, getAssociatedObject API ends up adding a non-existing page value to the autopopulate result's Page List. This, in turn, ends up in ConcurrentModificationExcepiton error.

Resolution



Apply HFix-29550. getPageValue function has been amended in getAssociatedObject API to getPageValueIfPresent function. This is modified so that we do not have unnecessary addition to Page List.

Published October 20, 2016 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration 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 Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us