Error "trying to calculate the handle of an instance without a pxObjClass"
Hi to all.
I'm getting the error "trying to calculate the handle of an instance without a pxObjClass property: code: <none> SQLState: <none> Message: <none> " on the 3rd step of the activity RevokeWorkObject. Pega 7.2.2v CSHC 7.1 FW
Could anyone say what it is?
***Updated by moderator: Lochan to add Categories***
Accepted Solution
Virtusa Corporation
US
Basically we get this issue if we try to save a page with wrong pxObjClass.
In my scenario newAssign page pxobjclass is changed and while saving that page we got this issue.
We got this issue only in 7.2 not in 7.1. I asked why this worked in 7.1. Then below is Pega's reply.
In pxProcessResolutionStage activity in 7.2 they used pega_procom_flow.removeassignment(tools,mysteppage). Which caused this issue. So they have given HotFix for this. They changed pega_processengine_flowutilities.removeassignment(tools,mysteppage). It worked.
EPAM Systems, Inc.
ES
Hi,
Could you set Logging Level Settings as Debug and share the logs for further analysis.
Navigate
DesignerStudio -> System -> Operations -> Logs -> Logging Level Settings
Logger Name :- Rule_Obj_Activity.RevokeWorkObject.Work_.Action
Current Level: - Debug
Kindly share PegaRULES logs and briefly explain what you are trying to achieve? And is this error occurring while running this activity stand-alone?
Virtusa Corporation
US
There is no such Logging Name in 7.2.2.
Please find attachment for Log File.
It logged an error saying "Created Dump File oldStreamki7zyyd14u.dat due to The reference .pzAutoPopulateKeyMap(1).pzAutoPopulateKey is not valid. Reason: Non-Page List property "
PFA for log file
Thanks
sateesh yennam
Accepted Solution
Virtusa Corporation
US
Basically we get this issue if we try to save a page with wrong pxObjClass.
In my scenario newAssign page pxobjclass is changed and while saving that page we got this issue.
We got this issue only in 7.2 not in 7.1. I asked why this worked in 7.1. Then below is Pega's reply.
In pxProcessResolutionStage activity in 7.2 they used pega_procom_flow.removeassignment(tools,mysteppage). Which caused this issue. So they have given HotFix for this. They changed pega_processengine_flowutilities.removeassignment(tools,mysteppage). It worked.