What problem does it solve? Salesforce Revenue Cloud Context Definitions are the canonical data layer that pricing, expression sets, the configurator, DocGen, and billing bind to at runtime, but authoring, extending, activating, and debugging them involves a confusing split between Connect API and SObject REST endpoints, version-level activation rules, and request-scoped runtime instances. This Skill guides an AI agent through those operations safely, with preflight validation, per-endpoint behavior matrices, and live-verified gotchas. ## Core Features & Use Cases - Design-time authoring and lifecycle: Extend standard contexts, apply additive attribute/tag/mapping plans, create custom definitions, and manage activation, versioning, and release upgrades via CCI tasks and helper scripts. - Runtime instance debugging: Build hydration payloads, hydrate context instances from live records, query values by tag, and persist changes back to mapped SObjects, with guidance on the Apex/Flow path required on GA orgs. - Inspection and drift management: Describe, trace, diff, export, and patch context definitions across orgs using read-only scripts before mutating anything. - Use Case: You need to surface a new custom field to a pricing procedure. The Skill walks you through adding an attribute plus tag plus mapping to the extended Sales Transaction context, linting the plan offline, dry-running it against the org, and verifying the result with describe_context.py. ## Quick Start Ask the agent to inspect the RLM_SalesTransactionContext definition in your org and explain how its nodes, attributes, tags, and mappings relate before making any changes.
