pyAutoHTML has null for non-autogenerated rules after upgrade
User has configured a report definition in order to fetch the results based on the value of pyAutoHTML for control rules.
But observed that the values of pyAutoHTML is null in the XML of few rules because of which there is incorrect result from the report.
pyAutoHTML value is null for few control rule XML's
Steps to Reproduce
1. Create one Report Definition in Rule-HTML-Property.
2. In Report Definition, add a filter with pyAutoHTML as false.
3. Observe that no results are fetched.
After upgrade from PRPC 5.x version where there is no concept of autogenerated rules to Pega 7.2.2 version, all the rules created in PRPC 5.x are upgraded with pyAutoHTML as null and since the report definition has a filter of "pyAutoHTML" value as "false", it is not giving any results.
Here's an explanation for reported issue:
Rules that have the value of "pyAutoHTML" as null are also considered to be as "Non-generated rules" along with rules that have "pyAutoHTML" as False.
Below are the two alternatives that are suggested to address the issue:
Create an activity to update rules only from your application ruleset. Based on the value of “pySourceStream”, one can perform “Property-Set” of “pyAutoHTML” as false for that rule, then perform Commit. Otherwise if pySourceStream is not null, then pyAutoHTML is saved as true.
Consider Rules that have “pyAutoHTML” value as false or null as “NON-Autogenerated rules” and the rest are autogenerated.