Question
Harness Failed on 7.2.0 above (Display Error)
Hi we recently upgraded our pega platform from 7.19 to 7.21 .
when we upgraded to 7.21 we get display error on our flow action that has preactivity calling pxShowReport to retrieve data from Report Definition to pyReportContentPage.pxResults .currently we resolved the issue by changing pxShowReport to obj-browse method to retrieve data.
but we still prefer to retrive the data from report definition, is there any way for pxshowreport to still work on preactivity on 7.2.0 above ?
we tried to upgrade 7.2.1 to 7.2.2 and still get this error .
***Updated by moderator: Lochan to add Categories***
HI febryl29,
I checked my Pega 7.1.9, Pega 7.2.1 and Pega 7.2.2 system for activity pxShowReport.
Pega 7.1.9 has activity pxShowReport under Pega-Reporting: 07-10-19
Pega 7.2.1 has activity pxShowReport under Pega-Reporting: 07-10-23
Pega 7.2.2 has activity pxShowReport under Pega-Reporting: 07-10-27
Among versions, there are small changes. But they all still get the data from report definition.
I ran it on Pega 7.2.1 and I could see that the data was populated to pyReportContentPage.pxResults.
Please check attached snapshot.
Please directly run activity pxShowReport on your upgraded system (Pega 7.2.1 or Pega 7.2.2) , enter the parameters as "pyDefaultReport" and "Data-Admin-Operator-ID" for required fields and check the result.
If it displays data successfully, then something is wrong in your application. You can collect the tracer log and check where is issue by comparing the working and non-working.
Thanks,
Susan
hi it seems like our issue happen because we call pxshowreport without parameter no report display to true .
so when the preact run, it try to show both RD report and Our Flow Action Section, we only used the data to retrieve it on our workpage so after we set the param to true, it's not showing the harness failed .
Hi,
Do you mean to say that pxShowReport activity isn't working in Pega 7.2.2?
I have tried replicating the scenario in-house and able to get the report definition displayed correctly by passing parameter explicitly to activity.
Could you try executing the stand-alone activity? Also, share the tracer file capturing the event of executing the flow.