Requirement Overview:
* Users need to define Discount Tiers where the values are treated as the Regular Price instead of amounts deducted from the List Price.
Solution:
* Configure the Discount Schedule to:
* Set the Discount Unit to Amount.
* Choose All from the Override Behavior picklist.
* Select the Use Price for Amount checkbox to treat the tier values as Regular Prices.
Steps to Configure:
* Navigate to the Discount Schedule Record.
* Set the Discount Unit to Amount.
* Select All from the Override Behavior picklist.
* Check the Use Price for Amount box.
Validation:
* Test the Discount Schedule to ensure the defined tier values are treated as Regular Prices.

Requirement Overview:
* Ensure the Standard Warranty (a Percent of Total product) generates an Order Product when a partial Order is created.
Solution:
* When generating a partial Order, selecting a Shipping Container product triggers the automatic creation of a Standard Warranty Order Product, as the warranty is based on the container's Net Price.
Steps to Test:
* Add a Shipping Container Quote Line and the Standard Warranty Quote Line to a Quote.
* Create a partial Order, selecting the Shipping Container.
* Verify that the Standard Warranty Order Product is generated.

To manage a subset of eco-friendly products for opportunities flagged as eco-friendly while allowing flexibility to include all bundles, follow these steps:
Step 1: Create a Filter Product Rule
Filter Product Rules help define dynamic filtering of products displayed during the quoting process.
* Navigate to Product Rules
* Go to Salesforce Setup # Product Rules and click New.
* Set the Type to Filter and define a clear Name such as "Eco-Friendly Product Filter."
* Configure the Filter Logic
* Define the conditions to identify eco-friendly and bundle products.
* Use the Conditions related list to target the relevant product fields (e.g., a custom checkbox for eco-friendly products and a type field for bundles).
* Example condition:
* Field = Eco-Friendly Checkbox
* Operator = Equals
* Value = True
Step 2: Set up the Product Action
Product Actions define what the rule does when triggered.
* Add a Product Action
* In the Product Rule, go to the Product Actions related list and click New.
* Set the Type to Optional Filter. This allows the system to apply the filter by default but enables users to remove the filter and see all bundles.
* Link to Add Products Button
* Make sure this action links to the Add Products custom action.
Step 3: Ensure Opportunity Integration
The Opportunity flagged as eco-friendly must drive this behavior.
* Custom Field Dependency
* Ensure the Opportunity has a field (e.g., Eco-Friendly Checkbox) that can be referenced in the Filter Product Rule or through a related custom formula on the Quote.
* Dynamic Behavior
* When the Opportunity is flagged, the filter is applied dynamically, displaying only eco-friendly and bundle products in the Add Products dialog.
Step 4: Test and Validate
* Test the behavior by flagging different Opportunities as eco-friendly and verifying the Add Products functionality:
* Eco-Friendly flag # Default to eco-friendly products and bundles.
* No flag # All products, including non-eco-friendly bundles, are shown.
Additional Considerations:
* Search Filter IntegrationThe Search Filter can complement this approach by providing additional options for users to refine their selections further.
* User TrainingTrain sales reps on how to toggle the filter manually if needed.
This setup allows Universal Containers to meet its business objectives while maintaining flexibility for its sales team.

Data Import Order for Quote Templates:
Salesforce CPQ requires Quote Template data to be imported in a structured order to ensure that relationships between objects are correctly established. Quote Template: Base structure for the quote document.
Template Sections: Define sections of the quote.
Line Columns: Specify how data appears in tables within the quote. Template Content: Includes HTML and text for the quote layout.
Quote Terms: Define legal or contractual terms.
Term Conditions: Conditions related to the terms.

Requirement Overview:
* Migrate new CPQ functionality from a sandbox, ensuring that record relationships are preserved.
Migration Sequence:
* Products: Base level of the bundle.
* Options: Product Options depend on the Product.
* Attributes: Attributes are referenced by Product Options.
* Rules: Product Rules depend on Products, Options, and Attributes.
Steps to Migrate:
* Export and import Products first.
* Migrate Options, followed by Attributes, and finally Rules.
Validation:
* Test the migrated functionality to ensure all dependencies and relationships are intact.