I made an evolution of the ListView OOTB GetNext rule, where in my first version I specialized for a ruleset of my application and defined it as a base. From there I applied a circumstance rule, where I did it based on the user's workgroup. Worked well.
We received a new demand, where we would have, based on the circumstance created previously, two new rules, where for the same property used for the circumstance, we would use different values. What we applied was, take the base rule from the previous version, create it in a new version of the ruleset and set it as a base and from there specialize for the circumstance. In the Development environment it works perfectly, but when we migrated to the test environment, after applying the package, we found that it is not managing to solve the detailed rules, the following message is presented for the ListView defined criteria
pyContentSource.pyParameters (). pyConditionFieldName is not a valid entry for ruleset and its prerequesites, and this problem does not happen in the development environment.
When we run the application validation, no error is shown, only when we try to revalidate and save the rule.
We have already restarted the server, however, nothing effective.
I have came across these types of issues. I cannot provide you an exact answer on why its behaving like this. Try to delete your list view rule in testing environment, open a ruleset and try to do the changes from scratch in testing. see how that behaves. (I know it's against to orthodox). If that rule is working in testing environment, then move it back to dev or else raise an SR. I know my approach is not right but just give it a try.
exactly the procedure that i applied. I did the rule in Branch and made the merge, but, when migrate for another enviroment the code failed. So, i decided to reopen the ruleset, remove circumstance rule and rebuilding the rules, so, after this procedure the code works fine.
Thank´s to reply! This help to open ideias and solve the problem.