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 and debugging them involves a confusing split between Connect API and SObject REST endpoints, silent failure modes, and activation rules that are easy to get wrong. This Skill gives an AI agent the routing rules, gotchas, helper scripts, and reference docs needed to extend, apply, validate, and debug context definitions safely. ## Core Features & Use Cases - Design-time authoring and lifecycle: Extend standard contexts, apply additive attribute/tag/mapping plans, create new definitions, and manage activation, versioning, and upgrade/Sync across releases. - Inspection and drift tooling: Run helper scripts to list, describe, trace, diff, patch, and export context definitions across orgs, with an offline plan validator for preflight checks. - Runtime instance lifecycle: Build hydration payloads, hydrate, query by tag, update attributes, and persist values back to mapped SObjects, with guidance on request-scoped contextIds, pilot gates, and the Apex/Flow path for GA orgs. - Use Case: You need to surface a new custom field to a pricing procedure. The Skill routes you to add an attribute plus tag plus mapping to the extended Sales Transaction context, lint the plan offline, dry-run it against the org, and verify the binding landed. ## Quick Start Ask the agent to inspect the RLM_SalesTransactionContext definition on your Salesforce org and trace how a specific Quote field maps to a context tag.
