arohitu/salesforce-revenue-cloud-skills

salesforce-revenue-cloud-pricing

Helps design, implement, debug, and explain Salesforce Revenue Cloud pricing logic.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/arohitu/salesforce-revenue-cloud-skills --skill salesforce-revenue-cloud-pricing

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Salesforce Revenue Cloud Pricing

Use this skill for Salesforce Revenue Cloud and Agentforce Revenue Management pricing work. Prefer out-of-the-box Salesforce Pricing configuration first, then Apex hooks only when declarative pricing cannot express the requirement.

Route The Request

  • Building or changing pricing logic: read references/build-pricing.md.
  • Debugging an unexpected price, failed pricing API, or quote/order pricing issue: read references/debug-pricing.md.
  • Debugging a decision table runtime error where lookup returns no row or multiple rows: read references/debug-pricing.md, then use the revenue-cloud-pricing-diagnostics skill to trace the pricing element inputs and context mappings.
  • Analyzing how a price, total, discount, exchange rate, or pricing field is calculated in an existing implementation: use the revenue-cloud-pricing-diagnostics skill as the primary workflow, then read references/analyze-pricing.md here only for supplemental Salesforce Pricing setup context.
  • Explaining what pricing logic is already implemented at a high level: read references/analyze-pricing.md.

If the user has not provided enough context, ask for the business scenario, object/process being priced (quote, order, product discovery, headless API), expected result, actual result, relevant product/price book/selling model, org access method, and any pricing procedure/procedure plan names they already know.

Default Workflow

  1. Identify the pricing surface: quote/order runtime pricing, product discovery pricing, headless pricing API, or procedure plan execution.
  2. Establish the active entry point:
  • Product Discovery Settings pricing procedure for product discovery list prices.
  • Salesforce Pricing Setup pricing procedure for headless pricing calls.
  • Revenue Settings pricing procedure for quotes and orders.
  • Procedure Plan Definition when Procedure Plan Orchestration for Pricing is enabled.
  1. Map the pricing path from data to result: context definition and mappings, decision tables, pricing recipe, pricing procedure elements, procedure plan sections, and optional Apex hooks.
  2. Validate with simulation, Price Waterfall, Revenue Cloud Operations Console price logs, or Apex debug logs depending on the task.
  3. Report findings as a concise pricing trace: inputs, matching rules/tables, executed elements/hooks, outputs, and likely fix.

Ground Rules

  • Use the same context definition across pricing procedures and procedure plans.
  • Prefer predefined Salesforce Pricing artifacts, especially the Revenue Management Default Pricing Procedure, before creating custom procedures.
  • Use decision tables and pricing recipes for maintainable rule lookup; do not hardcode rules in Apex unless declarative pricing cannot meet the requirement.
  • For decision table ambiguity or no-match errors, the preferred fix is to make the table inputs resolve to exactly one business-valid row. Do not assume the business wants a checkbox/setting that allows fallback, first-match, or multiple-match behavior.
  • Ask users to enable advanced/debug logging only during active troubleshooting and to turn it off afterward.
  • When Apex hook logic is needed, place prehooks before the Pricing section and posthooks after it; avoid DML in hooks and keep queries narrow.

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
arohitu
커뮤니티

revenue-cloud-decision-table

Finds and verifies Salesforce Revenue Cloud Decision Tables. Use when users need to locate a Decision Table Id, discover required Decision Table inputs, build conditionsList payloads, invoke business-rules decision-table lookup APIs, validate pricing lookup outcomes, or debug datasetLinkName and INVALIDAUTHHEADER issues.

설치 수
1
GitHub Stars
21
업데이트
9월 1일
arohitu
커뮤니티

revenue-cloud-config-apis

Reference and call the Salesforce Revenue Cloud (Revenue Lifecycle Management) Product Configurator Business APIs. Use when working with the CPQ configurator Connect REST resources - configuring a product bundle, loading/getting/setting/saving a configuration instance, adding/updating/deleting nodes, setting product quantity, or running configuration rules - and when the user mentions Revenue Cloud, RLM, Product Configurator, CPQ configurator, /connect/cpq/configurator, contextId, transactionId,

설치 수
1
GitHub Stars
21
업데이트
9월 1일
arohitu
커뮤니티

revenue-cloud-pcm

Salesforce Revenue Cloud Product Catalog Management (PCM) master data on core Salesforce objects for Agentforce Revenue Management, Revenue Cloud Advanced, and Revenue Cloud Billing. Use for any lookup, query, design, build, export, import, migration, CSV, sandbox load, troubleshooting, or analysis involving catalogs, categories, products, bundles, classifications, dynamic attributes, picklists, qualification/disqualification, selling models, Product Discovery, Product2, ProductCatalog, ProductC

설치 수
1
GitHub Stars
21
업데이트
9월 1일
arohitu
커뮤니티

revenue-cloud-pricing-diagnostics

Use this skill when dissecting Salesforce Revenue Cloud pricing in core Revenue Cloud orgs, tracing how a Quote, Order, Quote Line, or pricing field is populated, debugging pricing procedures, context definitions, context mappings, expression sets, pricing elements, decision tables, procedure plans, or Apex pricing hooks. Use it for Revenue Cloud pricing analysis even when the user asks generally how a price, total, discount, exchange rate, or field value is calculated. Do not use it for Salesfo

설치 수
1
GitHub Stars
21
업데이트
9월 1일