context-service

Configure, test, and migrate Salesforce Context Service definitions for Manufacturing Cloud pricing and billing workflows.

Updated Aug 6, 2026
One-click install
npx skills add https://github.com/salesforce-misc/ManuAssist --skill context-service-salesforce-misc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-service
Source: https://github.com/salesforce-misc/ManuAssist/tree/main/knowledge/modules/context-service
Command: npx skills add https://github.com/salesforce-misc/ManuAssist --skill context-service-salesforce-misc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Context Service is the data-caching layer behind Manufacturing Cloud Advanced (RCA) pricing, billing, and order orchestration, but its definitions, mappings, hydration behavior, and TTL scoping are complex and error-prone. This Skill provides the domain knowledge needed to set up Context Definitions correctly, write reliable E2E tests against context-backed procedures, and avoid common pitfalls like stale schema caches and missing default mappings. ## Core Features & Use Cases - Configuration Guidance: Walk through enabling Context Service, creating Context Definitions, choosing mapping types (Automatic SObject vs Input Mapping), and selecting mapping intents (Hydration, Persistence, Translation, Association). - E2E Test Design: Get concrete assertion patterns for Build Context, Query Context Tags, Update Context Attributes, Persist Context Data, and Delete Context Cache invocable actions in Flow and Apex tests. - Lifecycle & Migration: Follow checklists for extending vs cloning standard definitions, syncing extended definitions, and deploying definitions across sandboxes in the correct order. - Use Case: You are writing an E2E test for a pricing procedure and the hydrated context returns null for a newly added field. The Skill directs you to clear the runtime schema cache and verify the definition is active with a default mapping before re-running. ## Quick Start Ask the assistant to explain how to set up and test a Context Definition for a Manufacturing Cloud pricing procedure, including hydration and cache cleanup between test runs.

Frequently Asked Questions about context-service

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a Context Definition in Salesforce Context Service?

Enable Context Definitions in Setup, then create the definition with nodes and attributes, generate context tags, and add at least one mapping marked as default before activating. Prefer extending standard definitions over cloning when you need automatic upgrades.

How do I test a Flow that uses Build Context invocable actions?

Verify the Context Definition is active with a default mapping, run the flow in an Apex test, and assert on output variables populated by Query Context Tags. Clear the context cache between runs using the Delete Context Cache action for session-scoped contexts.

What is the difference between extending and cloning a Context Definition?

Extending applies only to standard definitions, allows additive changes, and auto-upgrades when the parent standard definition is upgraded. Cloning works on standard or custom definitions, allows full editing, but requires manual syncing and is not auto-upgraded.

Why does Build Context fail or return stale data in my tests?

Common causes are an inactive definition, no default mapping, or a stale schema cache after Salesforce metadata changes, which can take up to 24 hours to refresh. Clear the cache with DELETE /connect/context-runtime-schema/clear and verify activation status.

Can I deploy Context Definitions between orgs on different Salesforce releases?

No, both orgs must be on the same Salesforce release version; forward deployment to a newer release works but backward deployment fails. Deactivate the definition in the target org before deploying, then reactivate and verify mappings afterward.

What are the limits for Context Service definitions and instances?

Definitions default to 80 nodes and 1,500 attributes with up to 5 hierarchy levels. Runtime limits include 20,000 active context instances per app, 10,000 records per instance, and a session TTL of 10 minutes default up to 45 minutes maximum.