What problem does it solve? Constraint model changes in 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 correctly, keep reference .cml copies byte-identical, and understand that scripts/cml/*.cml is documentation only. - Bundle Member Wiring: Add products to configurable bundles with all four required records — PRC row, type/relation in the model, and ESC Type plus Port associations. - Deployment Diagnostics: Discover active models per org, cycle Expression Set versions after import, and verify deployment headlessly via the Product Configurator configure action. - Use Case: You add a product to the QuantumBit bundle, run import_cml successfully, but the configurator still behaves the old way — this Skill walks you through deactivating and reactivating the version and validating the rebuilt runtime model. ## Quick Start Ask the agent to add a product to a configurable bundle's constraint model and verify the change reaches the configurator.
