Introduction

Initially this wrapper class was named ConfigurationContext, but it happenned to be a reserved word that was generating different conflicts and errors.

There are a lot of operations that must be performed over a Product / Order during the Order Management Cycle:

• Configuring a new Order
• Loading an existing Order
• Checking Out an Order
• Validating and Order Item
• Validating and Order
• Evaluating Agreement Mapping Rules
• Checking Compatibility Rules
• etc

In order to simplify and normalize this, the CPQ comes with an APEX class named ConfigurationWrapper that holds all the information required to execute any of the previous actions. This apex class has the usual structure of a Configuration Context:

• Context
  • Items
  • Attributes

ADD DATA MODEL

In other words, the way that the CPQ internally handle the required Product/Asset/Order data is not through specific SOBJECTS like Orderc, OrderItem__c etc, or Map<String, Object> or whatever other structure. It’s always done through this ConfigurationWrapper class.