Posted: 1 Jul 2020 0:15 EDT Last activity: 1 Aug 2020 15:23 EDT
pxTransferAssignment throws error -- Database-General error ... instances trying to calculate .... may not be written to Assign-
I am running the OOTB pxTransferAssignment as shown below to transfer an assignment to JohnGault@Gault.com.
When I run the activity I get the following message
info: Database-General trying to calculate the handle of a class whose instances may not be written to the database: Assign-
I do an Obj-Open-By-Handle on step 3.2 and let the OOTB pxTransferAssignment to the Save and Commit. After the code runs, the assignment is indeed JohnGault's worklist but there is no Audit History on the WorkObject and this pop up that says info: Database-General trying to calculate the handle of a class whose instances may not be written to the database: Assign-
From the message it seems to be that PEGA is trying to write to the Assign- DB table, instead of the Assign-WorkList table.
I added a .pyNote property after I transfer the assignment (for unit testing) and that is empty which leads me to believe that the WO/Case is not getting saved an/or committed because of the message above, BUT somehow the assignment itself gets transferred.
The reason PEGA is trying to write to Assign- class is because the OOTB pxTransferAssignment works for BOTH Assign-Worklist and Assign-WorkBasket. Although you have specified 'Worklist' in the Param.DestinationType, I would hazard to guess that this a 'product' issue' and NOT an error in your code. Also the error is an 'Info' error and as your tracer is good AND the assignment went to John Gault, I don't see anything wrong in your code.
Best way to check is once you have run your code, go to Assign-WorkList class and see if your instance has been created/updated and the recipient is John Gault (which you have confirmed is working).
There is no Audit History on the WorkObject, even though you have specified Param.AuditNote is because you are missing another Param i.e Param.UpdateHistory. Set Param.UpdateHistory to true in step 4.1 and run your activity.