Debugging Invalid Configuration Status on Product Baskets

Symptom

A product basket is stuck in "Invalid" configuration status. The basket cannot be submitted because one or more Product Configurations fail validation rules. The issue may work correctly after manually editing and saving the PC, but fails during automated/initial rule execution.

Cause

Configuration validation rules (defined as cscfga__Configuration_Rule__c records with validation predicates) are evaluating to "invalid" for one or more attributes. Common causes include:

• Rule execution sequence issues where dependent rules run before their prerequisites
• Product Definition changes that introduced new validation predicates
• Attribute values that don't match the expected predicate conditions

Resolution

Step 1: Identify the failing validation rules

Query the validation messages on the Product Configurations in the basket:

SELECT Id, Name, cscfga__Product_Definition__r.Name,
  cscfga__Product_Definition__r.LastModifiedDate,
  cscfga__Validation_Message__c
FROM cscfga__Product_Configuration__c
WHERE cscfga__Product_Basket__c = '<BASKET_ID>'

The cscfga__Validation_Message__c field shows the exact error messages from the failing rules.

Step 2: Identify which rules are producing the validation errors

Match the validation messages to specific rules. Rules are named systematically (e.g., "Rule419", "Rule422"). The message text in cscfga__Validation_Message__c corresponds to the validation message configured on each rule.

Step 3: Debug rules using browser Developer Tools

1. Open the basket in the Solution Console
2. Press F12 to open Developer Tools
3. In the Sources tab, enable "Search in anonymous and content scripts"
4. Search for the rule name (e.g., "Rule419") to find the generated anonymous script for that rule
5. Place a breakpoint on the rule's predicate logic
6. Trigger a recalculation to step through the rule execution and identify which attribute values are causing the validation to fail

Step 4: Debug rules using Apex (backend)

The CloudSense Configurator User Guide (available on the Support Portal, Article 333) documents additional debugging options for rules, including Apex-level tracing for rule evaluation.

Step 5: Check for recent Product Definition changes

Verify whether the Product Definitions linked to the PCs were recently modified:

SELECT Id, Name, LastModifiedDate, LastModifiedBy.Name
FROM cscfga__Product_Definition__c
WHERE Id IN (
  SELECT cscfga__Product_Definition__c
  FROM cscfga__Product_Configuration__c
  WHERE cscfga__Product_Basket__c = '<BASKET_ID>'
)

Recent changes to Product Definitions (e.g., new rules, modified predicates, changed attribute defaults) may explain why baskets that previously worked are now failing validation.

Step 6: Verify rule sequence

If the issue only occurs during automated rule execution (but works when manually editing and saving), the rule execution sequence may be incorrect. Ensure that rules with dependencies on other rules' outputs have higher sequence numbers than their prerequisites.

Additional Notes

• If the same issue occurs across multiple environments, the root cause is likely in the Product Definition rules/predicates rather than in environment-specific data
• The fact that manually editing and saving a PC "fixes" the validation typically indicates a rule sequence issue -- manual saves trigger a full recalculation cycle that resolves ordering dependencies
• Check the Configurator User Guide (Support Portal Article 333) for the full list of debugging tools and techniques available for rule troubleshooting