State-based Constraint Rules

A constraint rules evaluates a state of the configuration while presenting options. For example, an inclusion rule may have an action to add option A or B to the model, but option A has already been excluded by a different rule that was associated with a different selection Hence, in this case option A is not available for selection.

Use Case:
Bundle 1 - Laptop
Processor 1TB (Option 1)
Processor 2TB (Option 2)

Bundle 2 - CISCO Switch
8 Ports (Option 1)
12 Ports (Option 2)
16 Ports (Option 3)

Cisco Server (standalone)
Office 365 (standalone) Product Group Software
Google suite(standalone) Product Group Software

Rule setup -
Rule 1 - Condition add Cisco Server. Google Suite is excluded. Setup exclusion error rule
Rule 2 - Condition add Cisco Switch, Office 365 is excluded. Setup exclusion warning rule
Rule 3 - Condition add laptop, Product Group Software is included (max 1). Setup inclusion error rule.

Scenario 1 (error) = Rule 1 and 3 are explained below:

  • You add Cisco Server to cart, Google Suite is disabled and Apttus CPQ displays an error message.
  • You configure a laptop, you are prompted to add a product from Product Group Software, Google Suite is disabled on prompt, and Office 365 is available to be added.

Scenario 2 (Warning) = Rule 2 is explained below:
You add Office 365 to cart, then add Cisco Switch to cart, Apttus CPQ removes Office 365 and provides a warning message.

Constraint Rules with Prompt Scenarios

On the inclusion prompt, CPQ disables or hides the products that are excluded by an exclusion type constraint rule to keep the validity of the cart intact.

When a product is disabled, CPQ shows an error message on the Cart or Catalog page. However, for the Warning type exclusion rule the product is not disabled in the prompt. When you enable Hide Disabled Options setting under Config System Properties, then CPQ hides the product.

Use Case:

Bundle 1 - Laptop

Processor 1TB (Option 1)

Processor 2TB (Option 2)

Bundle 2 - CISCO Switch

8 Ports (Option 1)

12 Ports (Option 2)

16 Ports (Option 3)

Cisco Server (standalone)

Office 365 (standalone) Product Group Software

Google suite(standalone) Product Group Software

Rule setup

Rule 1 - Condition add Cisco Server. Google Suite is excluded. Setup exclusion error rule

Rule 2 - Condition add Cisco Switch, Office 365 is excluded. Setup exclusion warning rule

Rule 3 - Condition add laptop, Product Group Software is included (max 1). Setup inclusion error rule.

Scenario 1 (error)

Jane adds Cisco Server to cart

Google Suite is disabled

System displays Error Message

Jane configures laptop

User is prompted to add product from Product group software

Google Suite is disabled on prompt

Office 365 is available to be added

Scenario 1 (Warning)

Jane adds Office 365 to cart

Jane adds Cisco Switch to cart

System removes Office 365 and provides Warning Message

Jane configures laptop

User is prompted to add product from Product group software

Google Suite and Office 365 is available to be added

Criteria-based Replacement Rules on the Server-side

Replacement rules on Server-side that based on the condition criteria that must be defined using fields from the following objects:

  • Line Item
  • Product
  • Configuration
  • Option
  • Product Attribute Value

The condition criteria comprise a filter expression with operators and values.

Replacement type constraint rules are not supported on the Client-side.

Use Case for Replacement type constraint rule:

You bought 5 units of Performance Cloud -Enterprise, CPQ prompts to replace the product with Performance Cloud- Ultimate.

Rule has following constraint rule Action and Condition

Condition:

Product scope: Product

Product: Performance Cloud -Enterprise

Condition criteria: Quantity = 5

Action:

Action type: Replacement

Action Intent: Prompt

Product Scope: Product

Product: Premium Support