txn-data-harness

Generate, inspect, verify, and clean up Revenue Cloud transaction demo data via CLI manifests.

33|12|Updated Sep 24, 2024
One-click install
npx skills add https://github.com/bgaldino/rlm-base-dev --skill txn-data-harness-bgaldino
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: txn-data-harness
Source: https://github.com/bgaldino/rlm-base-dev/tree/main/.cursor/skills/txn-data-harness
Command: npx skills add https://github.com/bgaldino/rlm-base-dev --skill txn-data-harness-bgaldino

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Creating realistic Salesforce Revenue Cloud transaction demo data (quotes, orders, invoices) manually is slow and error-prone, and partial runs are hard to resume or verify. This Skill provides a governed workflow for planning, generating, continuing, verifying, and cleaning up transaction demo data with the Transaction Data Harness. ## Core Features & Use Cases - Plan-before-write safety: Run cli plan or dry-run modes before any record creation, with manifest-driven inspection and verification by record IDs. - Multiple scenario kinds: Supports quote-to-invoice chains, direct order placement with assetization gating, and standalone invoice ingestion (draft, posted, and taxable posted) via Composite Graph APIs. - Resumable runs and cleanup: Continue partial runs from manifest checkpoints with cli step, and drive cleanup from manifest IDs while respecting non-deletable platform objects like posted invoices. - Use Case: A solutions engineer needs a few posted invoices in a demo org. They confirm the sf alias, run a plan against a smoke scenario, execute a single-concurrency run, then verify the invoice via SOQL using the manifest ID. ## Quick Start Ask the agent to plan and run the smoke-test scenario from the Transaction Data Harness against your sf org alias, then inspect the resulting 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 transaction data in Salesforce?

Run the Transaction Data Harness CLI with an sf org alias: first execute `cli plan` against a scenario config, then `cli run` with low concurrency for a smoke test. Verify created records by querying the IDs stored in the run manifest.

How do I create posted invoices without a quote or order in Salesforce?

Use the invoice_ingestion scenario kind, which posts a Composite Graph payload to the invoicing ingest endpoint. Posted ingestion requires an active non-taxable TaxTreatment in the org; taxable posted invoices additionally need an active taxable TaxTreatment.

Can I resume a partial Transaction Data Harness run?

Yes, use `cli step` with the run manifest to continue from its recorded reached_stage checkpoint. Pass the account explicitly for older manifests to avoid ambiguity.

Why did my harness run stop at the order stage?

Non-billing accounts cap at order_draft because activation creates BillingSchedules and Assets, which require billing setup. Inspect the manifest and plan output, then rerun against a billing-ready account.

Can posted invoices and BillingSchedules be deleted during cleanup?

No, posted invoices and BillingSchedules are platform-managed and not cleanly deletable. Cleanup should delete child-to-parent from manifest IDs, reverting activated orders to Draft first, and warn users about these leftovers.

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

No, per-scenario count values in the config take precedence over the CLI --count flag. To smoke-test a high-volume config, edit the per-scenario count to 1 or comment scenarios out.