1. On App Menu, click Conga CPQ Admin and then click the CPQ Admin tab. The new admin console is launched.
  2. Click the more icon () on the top-right corner and select Application Management.
  3. Click Configuration Engine.
  4. Configure the following details.

    Disable Constraint RulesIndicates whether constraint rules are disabled. This may be used to optimize performance when constraints are not used in the organization. The default value is false (enabled).
    Defer Constraint on Option SelectionSelect this setting to process the constraint rules on option selection on the Configuration Page. If the selected the constraint rules deferred until the Sales Rep clicks Go to Pricing or any other action button available on the Configuration page.
    Defer Validation Check In BundlesDefers the validation check in the bundle configuration step. This is selected by default.
    Show Checkbox In Rule DialogEnables check box to select multiple products in the Inclusion Constraint Rules dialog at once, instead of adding the products individually using Add to Cart. This setting works for Inclusion Rule with Min/Max Match Rule as Include Min/Max.
    Max Constraint Rules Round TripThis is the maximum number of round trips after which the constraint rule processing should stop. Round trip happens only when auto included products trigger more rules. The default value is 3.
    Constraint Rule Execution Mode

    Enter the mode to perform the constraint rule execution on the client-side or the server-side. By default, no value is specified and the system assumes the value as Server.

    Valid values are:

    • Client
    • Server
    • CMS

    This custom setting supports inclusion, exclusion, and validation rules on the client-side as well as the server-side.

    In a Service CPQ flow, always execute constraint rules in Client mode.

    Cascade Shared Attribute UpdatesCascades the shared bundle attribute updates to options in the bundle. If this setting is unchecked, the bundle attributes will initially be cascaded to options in the bundle, but subsequent changes in the bundle attribute will not be cascaded to option attributes.
    Populate Attribute Extensions

    Select this setting to indicate that the attribute values are populated in the attribute extension objects.

    Product Attribute Extension TablesEnter comma-separated API names of the lookup relationships, created with the Product Attribute Value object. For example, if you have 4 extension objects to Product Attribute Value object and their corresponding 4 lookup relationships, you must specify 4 API names in this field.
    Enable Field ExpressionsEnables you to use Expression Builder for attributes, option groups, and options.