Write an activity to scan through the pagelist of the "ruleset" instance under the name "pyRuleSetVersionsList". Each embedded list item has the property "pyUsage". Just update it as some value and you should be able to get over this.
usage property to be updated:-
Let me know if you need any additional inputs. Since you have more than 2000 warnings to fix, running this via activity may be the most feasible approach,
Yes, activity seems a valid work around for our situation at client.
For a permanent solution - If there is no way to enter Usage for Ruleset Version, then Pega should not throw those warnings. We might want to address this issue in the product. Do we need to raise a SR?
I concur with you that this needs to be fixed in the product. There seems to be no way to look at ruleset-version instances and update it's usage as in older versions of pega. I am wondering if this issue is only for rulesets migrated from earlier version of pega and not in the 71 versions ? If so, then I doubt if it needs to be fixed in 71 versions.
In Pega 7 you can no longer access the record/ruleform for Ruleset Versions. You will be redirected to the Ruleset form. This is true even if you search for a ruleset version and click on a specific version in search results.
Will, you may want to try running resave/validate on all your ruleset versions to see if the warning goes away. It may be an older warning that is no longer valid in Pega 7. The way to make older/invalid warnings go away is to resave the rule.