txn-data-harness

Generates and verifies Revenue Cloud transaction demo data through staged lifecycle scenarios.

Updated Sep 23, 2026
One-click install
npx skills add https://github.com/drgaciw/rlm-base-dev-fork --skill txn-data-harness-drgaciw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: txn-data-harness
Source: https://github.com/drgaciw/rlm-base-dev-fork/tree/main/.cursor/skills/txn-data-harness
Command: npx skills add https://github.com/drgaciw/rlm-base-dev-fork --skill txn-data-harness-drgaciw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating realistic Salesforce Revenue Cloud demo transactions (quotes, orders, invoices, usage journals) by hand is slow and error-prone, and partial runs are hard to inspect, continue, or clean up safely. ## Core Features & Use Cases - Staged data generation: Plan, dry-run, and execute scenario YAML configs covering Quote-to-Order-to-Invoice lifecycles, direct orders, and standalone invoice ingestion. - Manifest-driven operations: Inspect, continue, report on, and clean up runs using run manifests that record reached stages and record ids. - Usage upload and rating: Upload TransactionJournal rows and trigger the separate org-wide async rating flow per batch. - Use Case: A solutions engineer needs a few posted invoices in a demo org; they plan with a smoke scenario, run it with concurrency 1, then verify the invoice via SOQL using manifest ids. ## Quick Start Ask the agent to plan and run the 01-smoke-test scenario against your sf org alias, then inspect the manifest and verify the created invoice with a SOQL query.

Frequently Asked Questions about txn-data-harness

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

FAQPage Schema
How do I generate Revenue Cloud demo transactions in a Salesforce org?▼

Run the harness CLI plan command with a scenario YAML config against an sf org alias, then execute the run command with low concurrency. Verify created records by querying manifest ids with SOQL before reporting success.

How do I create standalone draft or posted invoices without a quote-to-order chain?▼

Use the invoice_ingestion scenario kind, which posts a Composite Graph payload to the invoicing ingest endpoint. Posted ingestion requires an active TaxTreatment in the org, with a taxable treatment needed for tax-on invoices.

Can I continue a partial harness run that stopped mid-lifecycle?▼

Yes, use the cli step command with the run manifest and a target stage to continue from the recorded reached_stage. Pass the account explicitly for older manifests or when ambiguity is risky.

Why did my harness run stop at order_draft instead of activating?▼

Non-billing accounts cap at order_draft because activation creates BillingSchedules and Assets that require billing setup. Use a billing-ready account for the target dataset to proceed past activation.

What records cannot be cleaned up after a harness run?▼

Posted invoices and BillingSchedules are platform-managed and not cleanly deletable. Cleanup deletes child-to-parent using manifest ids, and activated orders must be reverted to Draft before deletion.

Does the --count flag limit records in a multi-scenario config?▼

No, per-scenario count values take precedence over the CLI flag. To smoke a config that pins count per scenario, edit the per-scenario count to 1 or comment scenarios out instead.