Rule is not referring the highest version that I deployed, why?
I have deployed a ruleset with 10 rules, those 10 rules are sections, all of them are in same version, after deployment when I am doing unit testing I see that one section is not referring the highest version that I deployed.
Application is pointed to the correct ruleset, 9 sections are working fine and there is an issue with one section.
With respect to Rule availability all 10 rules are available, it is in correct context, all checked in rules and took a JAR and deployed.
I have same access in Dev and QA, that one section is still referring to the old version.
How will you start debugging, what is your thought process?
Thanks
Updated: 14 Jun 2021 7:38 EDT
Pegasystems Inc.
IN
Could you please check if the 10th section in the same ruleset is available in the QA environment by searching, and what is the status of the rule in the Dev of the latest version?
Updated: 14 Jun 2021 7:38 EDT
Pegasystems Inc.
IN
Could you please revalidate and save the rule which is the highest version that needs to be picked.
Else it could be a rule cache issue, a restart should fix if it is.
Pegasystems Inc.
IN
Go to Configure->Application->Tools->Validation and run a ruleset validation. If there are any errors in the section rule, you can see it there.