Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Report browser does not return reports post update to Pega 7.2.2

SA-54232

Summary



When a portal references the pyCMReports portal in a harness, the report browser does not display reports. This occurs post update to Pega 7.2.2.


Error Messages



Not Applicable


Steps to Reproduce

  1. Update Pega 7.1.8 to Pega 7.2.2.
  2. Run pyCMReports standalone. This returns zero reports.
  3. Replace the below line of pxgetRRContentForRB (Oracle DB) 

    int len = strWhereClause.indexOf(" AND \"schedule\".pxObjClass"); 

    with 

    int len = strWhereClause.indexOf(" AND \"schedule\".\"PXOBJCLASS\""); 
     
  4. Run the pyCMReports.


Root Cause



A defect in Pegasystems’ code or rules.

Compare the SQL requests that are generated by pxgetRRContentForRB activity on both Pega 7.1.8 and Pega 7.2.2.
In Pega 7.1.8, the ""schedule".PYSTATUSWORK ='Open'' statement is added.
In Pega 7.2.2, the "AND "schedule"."PXOBJCLASS" LIKE ? AND "subscriber"."PXOBJCLASS" = ?" statements  are added.

In Pega 7.1.8, column names are written as "PC0".pxObjClass, while in Pega 7.2.2, the column names are written as "PC0"."PXOBJCLASS". Hence, the replace or indexOf functions used in Java step 3 of pxgetRRContentForRB did not work correctly.



Resolution



Apply HFix-42572.

Published September 27, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

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

Pega Community 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
Contact us