Hi,
I tried renaming a class using Refactor. The rename completed successfully without any errors, but I’m still seeing the old class name, the new class name isn’t getting reflected. What could be the issue? Can anyone help?
Regards,
Mamatha Adiraju
This usually happens because the old class name is still coming from cache after the refactor. The rename may have completed correctly, but Pega can continue showing the old class until the rule cache is refreshed. Clear the rule cache on the node, log out, and open the application again. After that, check the class rule using the new name. In most cases, the new class name starts reflecting only after this cache refresh.
Yes, the most common reason you still see the old class name after a successful Refactor rename is rule and class metadata caching.
The refactor likely completed correctly, but the old class definition is still being served from cache (node-level and/or browser session). Clearing the cache and restarting the user session usually resolves this.
You can check the rule XML to see if the old class name is still present post refactoring.
If cache clearing does not resolve the issue, validate the following.
Application Explorer Context: App Explorer can still show inherited or outdated class paths until refresh Switch application context.
Class Exists in Multiple Rulesets: Check if the old class name still exists in a different ruleset version, refactor only renames within the selected application/ruleset scope
Built-On Applications: If your application is built on another app, the old class name may still exist in the parent layer. App Explorer may show both unless scoped carefully.
Validation Mode / Rule Conflictsm :If Application Validation (AV) is enabled, some dependent rules may still be marked invalid until re-validated
Run Revalidate and Save on affected rulesets if needed.