The admin at Universal Containers has received several reports that unwanted price changes have occurred on Quotes that have already been approved.
Which two configuration changes should the admin make to prevent this issue from happening?
(Choose 2 answers)
A. Remove any edit permissions on pricing ficlds in the ficld level security.
B. Assign a different layout to ensure users cannot access the Quote Line Editor, and hide the related list of Quote Lines.
C. Add a Validation Rule on an approved Quote and Quote Line to prevent any material changes.
D. Create a Product Rule, type Validation, that blocks users from editing Quote or Quote Line fields.
A. Remove any edit permissions on pricing ficlds in the ficld level security. C. Add a Validation Rule on an approved Quote and Quote Line to prevent any material changes.
Explanation:
Issue:
Users are changing data on quotes after they’re approved. This is a big problem because it undermines the integrity of the approval process.
There are two excellent ways to address this in Salesforce CPQ:
✅ A. Remove any edit permissions on pricing fields in the field level security.
Once a quote is approved, price fields should no longer be editable. Removing edit access via Field-Level Security (FLS) ensures users can’t change fields like Sales Price, Net Price, Discount %, List Price. This locks down sensitive pricing data. However, this approach alone might not fully prevent changes in all contexts (e.g. API updates or edits via Quote Line Editor). So we also need:
✅ C. Add a Validation Rule on an approved Quote and Quote Line to prevent any material changes.
Validation Rules are the most robust way to block changes once a quote is approved. Example: AND(ISPICKVAL(Status__c, "Approved"), ISCHANGED(SomeField__c))
This completely blocks edits to critical fields if the quote’s status is “Approved.” It’s the best-practice safeguard to enforce approval integrity.
Why not the other options?
B. Assign a different layout to ensure users cannot access the Quote Line Editor, and hide the related list of Quote Lines.
This is UI-level protection only. Users might still access fields through reports, APIs, or other screens.
D. Create a Product Rule, type Validation, that blocks users from editing Quote or Quote Line fields.
Product Rules only run in the Quote Line Editor. They do NOT enforce validation when users edit Quote or Quote Line records directly (e.g. in standard record pages). Validation Rules are more comprehensive. Hence, A + C are the correct answers.