Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Piyush Kumar (Piyush)
Capgemini
Managing Consultant
Capgemini
NO
Piyush Member since 2015 46 posts
Capgemini
Posted: Feb 11, 2019
Last activity: Feb 27, 2019
Posted: 11 Feb 2019 5:11 EST
Last activity: 27 Feb 2019 0:47 EST
Closed

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***

To see attachments, please log in.
Low-Code App Development
Java and Activities
User Experience

Posted: 5 years ago
Posted: 15 Feb 2019 13:03 EST
Mahesh Midthuru (Mahesh Midthuru)
PEGA
Senior Principal Application Engineer, Customer Service Digital
Pegasystems Inc.
US

Hi Piyush,

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,

Mahesh M

To see attachments, please log in.
Posted: 5 years ago
Posted: 21 Feb 2019 11:00 EST
Mahesh Midthuru (Mahesh Midthuru)
PEGA
Senior Principal Application Engineer, Customer Service Digital
Pegasystems Inc.
US

Hi Piyush,

Thanks for sharing the requested tracer for our analysis and please find my observations as follows:

  1. Page-Remove on newAssignPage is being called from @baseclass.ProcessAction activity step 10 code.
  2. 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.
  3.  so in both the scenarios the newAssignPage is not being removed.
  4. 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.

Hope this analysis might help you going forward.

Regards,

Mahesh M

To see attachments, please log in.
Posted: 5 years ago
Posted: 27 Feb 2019 0:47 EST
Piyush Kumar (Piyush)
Capgemini
Managing Consultant
Capgemini
NO

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.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center 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