Loading

Readiness Tool shows non CPQ or Advanced Approvals users need PSL

Fecha de publicación: Sep 23, 2025
Descripción
There are a number of scenarios in which users may show as non-compliant when using the Check Upgrade Readiness tool. In addition to the users outlined in the check upgrade readiness article, certain users with the following access defined in a custom Permission Set may not appear in the readiness check reports but are still required to have an appropriate license. The following shows custom Permission Set access granted to users which will or will not prevent a successful upgrade to the Winter '21 release:

Prevents successful upgrade to 228 (Winter '21)
  • Custom Permission Set that grants the Modify All Data system permission
  • Custom Permission Set that grants the View All Data system permission
NOTE: Users, including integration users not shipped with the CPQ package, who have access to CPQ or Advanced Approvals licensed custom objects need to have a related license. 

Will not prevent successful upgrade to 228 (Winter '21)
  • Custom Permission Sets which grant access to these 6 CPQ Licensed Custom Objects (LCOs) or related dependent objects:
    • Price Rule
      • (Price Action, Price Condition)
    • Pricing Guidance 
      • (Pricing Guidance Tier)
    • Product Rule 
      • (Configuration Rule, Error Condition, Product Action)
    • Quote 
      • (Quote Document, Quote Line, Quote Line Group, Quote Line Pricing Guidance, Quote Line Consumption Schedule, Quote Line Consumption Rate, Quote Document)
    • Quote Template 
      • (Line Column, Template Section)
    • Subscription
      • (Subscribed Asset, Subscription Consumption Schedule, Subscription Consumption Rate)
  • Users with access to these 2 Advanced Approvals LCOs or related dependent objects:
    • Approval
      • (Approval Snapshot)
    • Approval Rule
      • (Approval Condition)
NOTE: Dependent objects can be any custom object that defines one of these CPQ or AA LCOs in a Master-Detail relationship. Permissions granted to custom objects used in this manner will also require a permission set license post upgrade to CPQ 228 or AA 228.
Solución

The above scenarios that will not prevent a successful upgrade to v228 can temporarily be ignored if users do not require CPQ/Advanced Approvals access. However, if they do require CPQ/Advanced Approvals object access, these users need to have a Permission Set License (PSL). If they do not need access to either package, their assigned custom Permission Sets should be edited to remove access to LCOs and their dependent objects in order to be in a compliant state in CPQ/AA version 228. 

  • Integration Users are system added users whose user record cannot be edited.
  • Note that View All Data and Modify All Data are treated as having access to CPQ/Advanced Approvals objects. If a user has either system permission Modify All Data or View All Data, they will need to be assigned a Permission Set License.
Número del artículo de conocimiento

000380551

 
Cargando
Salesforce Help | Article