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

There are no rule changes to package error on creating revision

SA-96231

Summary

A process ends successfully after running a revision. However, no package generates to import environment. Although, a change is made to the rule, a package is not supposed to be created by the system with the no rule change to package message. This mechanism used to work correctly. Currently, two different application Overlays are present on the system. However, the same error message displays for both the applications while creating revision.


Error Messages

There are no rule changes to package            


Steps to Reproduce

  1. Create a revision
  2. Make a change to a rule
  3. Approve the revision
  4. Submit the revision. No package generates


Root Cause



A few redundant rules (an activity and a parse file) are present in the revision branch. The redundant rules are not supposed to be present since there are no other revisions in progress. The ruleset and the When rule were revised are recognised. However, the ruleset version under Rule Counts is not recognised. The system creates the below two default artefacts on a branch ruleset while creating the branch ruleset:
  • Name of the ruleset
  • Version of the ruleset


However, the ruleset version is not present causing the revision packaging to fail.


Resolution



Perform the following local-change:
  1. Perform a cleanup of the redundant rules
  2. Perform a cleanup (delete & recreate) of the branch ruleset version

 

 

Suggest Edit

Published January 20, 2020 - Updated December 2, 2021

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