Question
Capgemini
NO
Last activity: 2 Sep 2020 10:57 EDT
Harness Launch Removes pyWorkPage
After migrating from 7.3 to 8.1, in work class section on click of a button a Harness is being launched when the case is open. The Harness is being launched using a different page of the same work class. However in doing so it is being observed that it removes pyWorkPage.
This issue is only happening in Pega 8. It is working fine in 7.
How to resolve this? When i change the page context of Harness to pyWorkPage, the issue is not observed but we cannot do this in actual?
***Edited by Moderator: Pallavi to update platform capability tags***
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Accepted Solution
Updated: 2 Sep 2020 10:57 EDT
Pegasystems Inc.
US
According to the SR the resolution is:
Perform the following local-change: pyRetainPage has been set to "true"
Hope that helps!
Marissa | Senior Moderator | Pega Collaboration Center
Pegasystems Inc.
FR
Hello,
Have you tried to trace this issue to understand what is actually removing the page? Can you share the tracer with us?
Capgemini
NO
Found the trigger point of the problem. doUIAction Activity (Pega 8) at step 10 is removing additional pages which includes pyWorkPage. This is not happening in Pega 7 though even that also has the similar step. Though there is slight change in the code of step "Remove Additional Pages" in doUIAction (08-01-01,07-33-10). However even if I copy the code from version 7, the issue persists. Only when that particular step (10) is commented, the issue gets resolved.
Should we raise an SR for this?
Pegasystems Inc.
US
If you'd like to get this formally evaluated, yes an SR would be the route to go here.
If you do create one, just let us know the ID here so we can track it.
Capgemini
NO
We are still trying to find some work around. Please let me know if there is any other approach to this. If nothing helps we will go for SR.
Sopra Steria
FR
Did you create a SR and had an answer ?
Pegasystems Inc.
GB
This behavior seems to occur only when using a portal (e.g. 'Launch web interface' from Dev Studio). If you open your case directly in Dev Studio the behavior is not observed.
On my project we have a workaround for this.
As mentioned by OP the problem occurs in data transform @baseclass.doUIAction at a step with comment: Remove additional pages for No-Frame Case.
In Pega 8.1 this occurs at step 10; in Pega 8.2 it occurs at step 11.
In Pega 8.2 the When condition for this step looks like this:
(@pzIsPortalSDM()==true || param.isDCSPA == true ) && param.isMDC != "true"
The workaround is for each developer to do a private checkout on this rule and remove the first logical condition from this When condition so that it looks like this:
param.isDCSPA == true && param.isMDC != "true"
Save it and refresh your portal screen and you will be able to open the clipboard tool and see pyWorkPage.
I have used this workaround in both 8.2 and in 8.1.
Occasionally the workaround will break a test case: you will have to remove the private checkout to enable the test case to pass.
Sopra Steria
FR
Hello,
We're having the same issue on Pega 8.2.1 but with the newAssignPage page, on Production (so the private checkout "solution" is not an option).
Did you have any news on how to solve this ?
I created SR-D26136 in parallel, I'll update you if I have any useful news
CommonWealth Bank of Australia
IN
Hi,
Please try to check the value of the pyRetainPage property. The pyRetainPage flag should be set to true to retain the page.
Thanks,
Capgemini
NO
This is a work around that we used.
Swedbank
SE
Hi,
We are also facing the same issue. Please let me know if you receive any update from SR-D26136
Sopra Steria
FR
It was 9 months ago and I changed projects so I do not have access to the SR historic anymore :/
I don't know if anyone from Pega Support could access it and adress what solution we found
Swedbank
SE
Hi,
Thank you for the reply. I will check with Pega support if they can access it.
Accepted Solution
Updated: 2 Sep 2020 10:57 EDT
Pegasystems Inc.
US
According to the SR the resolution is:
Perform the following local-change: pyRetainPage has been set to "true"
Hope that helps!
Marissa | Senior Moderator | Pega Collaboration Center
-
Piyush Kumar Rima Dutta
Swedbank
SE
Hi,
Thank you for your reply. Setting pyRetainPage to true helped to retain pyWorkPage but few clipboard pages are still missing after this workaround.
PKUtech Co., Ltd
JP
Hi, do you have any other solution?
The thing is not a problem that pyWorkpage is not visible from case manager when the case is open?
It is quite weird that pyWorkPage is not visible during case open...