Question
OLIGOS
FR
Last activity: 23 Jan 2025 10:55 EST
Customer Service - Differences between 8 and 8.8 application versions - Unanswered
Hello,
In the post https://support.pega.com/question/customer-service-differences-between-8-and-88-application-versions? , a person from Odigo asked a question about the differences between 8.8 and 8 version of Customer Service.
We are currently doing an upgrade from 8.6 to infinity 24.1, so we upgraded some application versions, including those based on Customer Service, and we face a problem that is a consequence of what the author mentionned : some rules are not available because Customer Service does not contain some specific rulesets anymore.
Can you please clarify what we have to do in this context?
FYI, the specific error message is :
.pyClassName: PegaFW-Admin-SocialSettings is not a valid entry. Class PegaFW-Admin-SocialSettings is defined in ruleset PegaFW-Social which is not among the prerequisites for ruleset version XXXX. Save the record in a different Class which allows XXXX ruleset or save it in a ruleset allowed by PegaFW-Admin-SocialSettings Class.
Accepted Solution
Updated: 23 Jan 2025 10:55 EST
HCA Healthcare
US
@AdrienPIQUENET The error you are facing during the upgrade from Pega 8.6 to Infinity 24.1 happens because the PegaFW-Admin-SocialSettings class, previously part of the PegaFW-Social ruleset, is no longer available. To fix this, check if the PegaFW-Social ruleset was removed in the newer version by reviewing the release notes. If it was removed, consider replacing the class with an alternative supported class or moving the affected rules to a different ruleset. If the ruleset still exists but was excluded, you can manually add it as a prerequisite in the ruleset definition. Run the Application Validation Wizard to catch similar issues and revalidate all rules. If the issue continues or the ruleset has been officially removed, reach out to Pega Support for further guidance
OLIGOS
FR
@Sairohith Hello,
Thank you for your input.
I will take a look at release notes as you mentionned, but indeed we will have to find a solution to re-include the needed class in our application stack.