There are no rule changes to package error on creating revision
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.
There are no rule changes to package
Steps to Reproduce
- Create a revision
- Make a change to a rule
- Approve the revision
- Submit the revision. No package generates
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.
Perform the following local-change:
- Perform a cleanup of the redundant rules
- Perform a cleanup (delete & recreate) of the branch ruleset version
Published January 20, 2020 - Updated December 2, 2021
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.