We have test rulesets, application rulesets as part of our profile stack.
There were some valid application rules created in test ruleset mistakenly and being referred as part of application ruleset rules.
As we don’t include test ruleset in package While we do deployment we missed those rules and flow started to run in to missing rule exceptions.
Is there any simple OOTB report we can use to get the list of rules in test ruleset that are referred in main application ruleset. ? Before we do deployment we will run this report to make sure we don’t have any valid rules in test ruleset.
In general unit testing is good practice in development, so make an application wrapper for your application. Lets says CITICLAIMS is your application, make CITICLAIMS_DEV as your dev application which includes your unit test rulesets.Use this application(_DEV) in your developer access groups and use the actual application in the access groups of the end users. By taking this approach, any missing rules would be identified by unit testing with end user logins (which is a good practice).
Another way to enforce developers maintain uniformity is make it mandatory to add a prefix of "Unit_" or "Test_" as part of your rule name while creating rules in your test rulesets. this you can achieve by making a modification in the rule-validate rules.
As both the above practices are manual and we do mistakes manually, extend one of the Rule -WBsave activity to make sure there is no existing rule in the system except in test ruleset with the same pzinskey(primary key combination of the rule class).If the rule exists, then add a error message to the rule page which avoids the developer to save the rule in the first place.
I am not a big fan of revalidate and save as it has its own known issues but would prefer to make sure we run the Application Validation tool in latest versions.