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

Unable to Save As circumstanced report definition in User portal

SA-66764

Summary



Error occurs when saving a circumstanced report definition through the report browser in the User portal. This works when using Designer Studio.


Error Messages



.pyCircumstanceVal: This Rule cannot be created: it is qualified by a Circumstance, Circumstance Date, or Date Range; but no default version exists 
java.lang.NullPointerException



Steps to Reproduce

  1. Create a circumstanced report definition.
  2. Add it in the report browser.
  3. Open the User portal.
  4. Access the report definition which is circumstanced through report browser.
  5. Provide a Category and Save As the report definition.


Root Cause



A defect in Pegasystems’ code or rules.
Circumstance report cannot be saved as a new report in the portal. When a report is circumstanced, it adds additional properties to the report Clipboard page. When a report is Saved As, validation fails due to these additional properties.
 
In the pzRRSaveAS activity, a Java step must be added such that it removes the circumstance properties from the report definition primary page.



Resolution



Apply HFix-48007.


 
Suggest Edit

Published December 13, 2018 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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