What problem does it solve? Constraint model changes in Salesforce Revenue Cloud often appear to deploy successfully yet never take effect in the configurator, and missing association records cause products to fail Product Validation with no clear error pointing at the model. This Skill explains the file layout, the four records every bundle member needs, and the deactivate/import/activate cycle required to make a CML change actually reach an org. ## Core Features & Use Cases - CML Authoring Guidance: Edit .ffxblob artifacts (the real model source) correctly, keep reference .cml copies byte-identical, and avoid treating reference files as deployable artifacts. - Bundle Member Wiring: Add products to configurable bundles with all four required records — the ProductRelatedComponent row, CML type/relation declarations, and both ESC Type and Port associations. - Deployment & Diagnosis: Run the deactivate → import_cml → activate cycle, recover from partial ESC imports, and verify deployment headlessly via the Product Configurator configure action. - Use Case: You added a product to a bundle and it appears in the configurator but fails Product Validation. This Skill identifies the missing ESC Type association as the cause and walks you through fixing and redeploying the model. ## Quick Start Ask the agent to add a product to a configurable bundle's constraint model and deploy the change so it takes effect in the configurator.
