Posted: 11 Feb 2019 5:11 EST Last activity: 27 Feb 2019 0:47 EST
pzRunActionWrapper deletes the newAssignPage
A grid is being sourced from a pagelist (data class). In the last column I have to give the option to upload documents. So I am running a local action "pyAttachContent" using page "Top" as it belongs to work- class.
However, after attaching documents (successfully), when I click continue to move to next assignment (Flow is screes flow) it shows error "The operation completed successfully but returned no content".
When traced I observed that newAssignPage was getting removed when I clicked the attach icon in the grid. So I set the property "pxFlowInsKey" of "newAssignPage" on watch which highlighted that as soon as I clicked the attach icon, the activity "pzRunActionWrapper" in it's first step made changes/deleted to the property/page.
Later at 14th step of "Work- pyAcquireObject" activity a new "newAssignPage" gets created.
Note : I am using PRPC 8.1 personal edition
***Edited by Moderator: Pallavi to update platform capability tags***
I cross checked the step 1 code in pzRunActionWrapper activity and couldn't see the piece of code that is deleting/updating the newAssignPage. Can you please trace the use case and share the tracer log for our analysis.
Thanks for sharing the requested tracer for our analysis and please find my observations as follows:
Page-Remove on newAssignPage is being called from @baseclass.ProcessAction activity step 10 code.
In the shared tracer log noticed that at line 2172 and 8832 this step 10 is being called but in both the scenarios the step 10 has been skipped due to failure of "newAssignPage.pxRefObjectKey != Local.workHandle" condition.
so in both the scenarios the newAssignPage is not being removed.
While coming to the pzRunActionWrapper step 1 at line 694, i can see Set Top.pyPageName method is being called followed by a sequence of select queries that has been triggered.
Thanks for the analysis but it doesn't help in resolving the issue. How do I prevent the removal of "newAssignPage"? None of my code is triggering it. Can't you replicate the issue and see if there is any internal Pega bug that is causing this.