Consumer Goods Accruals Datakit Deploy

MANDATORY: Always write the Phase 6 report

After completing all phases — including early stops, blocked phases, or error conditions — you MUST write the Phase 6 report to disk. Failure to write the report is always a test failure, regardless of how well you handled the scenario.

This applies to ALL exit paths without exception:

• Normal completion (all phases ran)
• Phase 1 stop (preflight failed, sales org not found, CGCloudAddons missing, Data Cloud not enabled)
• Phase 3 error (setup script non-zero exit)
• Phase 4 failure detection (DataKitDeploymentLog failures)
• Schedule conflict (Phase 5 guard triggered)
• Any other blocking condition (missing inputs, org unreachable, etc.)

Write the report to ${outputDir}/report.md (the path from the generatedFileLocationDirective in the task). Do not print it as a chat message only — it must exist as a file on disk. If you handled a scenario correctly but never wrote the file, the eval will record no_output and score zero.

Deploy the Accrual Data Kit

Installs the TPM Liability Accruals solution into a Salesforce org end to end. Runs the full setup toolchain bundled in scripts/: checks the org is ready, verifies the Data Cloud connection, downloads the CGCloudAddons static resource, deploys the data kit, confirms the deployment, and schedules the Data Cloud export and accrual calculation chain.

Designed for headless delivery: point it at an org and it runs the full install.

The namespace differs per build: cgcloud (released), cgcloud_dev (dev/beta), or no prefix (source-only). The setup script auto-detects the prefix at runtime via the DataCloudExportScheduler Apex class query. Never hardcode cgcloud. or cgcloud_dev..

Reference: TPM Accrual Engine concept

Run the setup script from the skill root directory:

node scripts/setup.js --org <alias> [options]

Inputs to collect

Collect and validate ALL required inputs before running any Phase 1 checks. Do not start Phase 1 until org alias and sales org name are both confirmed. If either is missing after asking, stop immediately and write the Phase 6 report.

Ask before starting — do not guess.

The dry-run flag is collected once here and honored through all phases — do not re-prompt.

Phase 1 — Preflight

Stop on first failure. Do not continue past a failed check.

1.1 Local tooling

1. Salesforce CLI present: sf --version
2. Node 22: node --version

1.2 Org reachable

sf org display --target-org <alias> --json

Confirm status is Active. Capture id (org id), instanceUrl, apiVersion. Non-zero exit or inactive status → stop, ask user to log in.

1.3 Data Cloud Data Kit framework present

sf data query --target-org <alias> \
  --query "SELECT Id FROM DataKitDeploymentLog LIMIT 1"

INVALID_TYPE or NOT_FOUND → stop immediately: the Data Cloud Data Kit framework is not enabled in this org. Tell the user they must enable Data Cloud and the Data Kit feature before this skill can proceed. Write the Phase 6 report now with Phase 1 blocked and the exact query error. Do NOT run any further queries, downloads, or deploys. Zero rows is fine — the framework is present, continue to Phase 1.4.

1.4 CGCloudAddons static resource present

sf data query --target-org <alias> \
  --query "SELECT Id FROM StaticResource WHERE Name='CGCloudAddons'"

Zero rows → stop immediately: the managed package is not installed (or this version does not ship CGCloudAddons). Tell the user the package must be installed before proceeding. Write the Phase 6 report now with Phase 1 blocked: CGCloudAddons not found. Do NOT attempt to download, deploy, or schedule anything after this failure.

1.5 Sales org validation

sf data query --target-org <alias> --json \
  --query "SELECT Id, Name FROM Sales_Organization__c WHERE Name = '<salesOrg>'"

Zero rows → stop immediately: the sales org name provided does not exist in this org. Show the user the query and the zero-row result. Do NOT proceed to deploy or schedule. Record Phase 1 as blocked: Sales org '<salesOrg>' not found.

1.6 Deployment baseline

sf data query --target-org <alias> --json \
  --query "SELECT MAX(CreatedDate) maxCreated FROM DataKitDeploymentLog"

The aggregate query always returns exactly one row. maxCreated is null when the table is empty (first-ever deployment). Store DEPLOY_BASELINE_TIME = maxCreated ?? '' (treat null as empty string). Phase 4 uses WHERE CreatedDate > DEPLOY_BASELINE_TIME only when DEPLOY_BASELINE_TIME is non-empty; omit the WHERE clause entirely when it is empty — WHERE CreatedDate > null is an INVALID_QUERY_FILTER_OPERATOR error in Salesforce SOQL and will abort the query.

1.7 Org-side manual prerequisites

If the user's prompt already confirms these prerequisites, treat them as confirmed — do not re-ask. Only ask for items the user has not already addressed:

• Data Cloud and Analytics Studio enabled (Setup → Data Cloud Setup)
• Connectors feature enabled (Data Cloud Setup → Feature Manager)
• A user assigned to the Accrual Ingestion Process in Processing Services Pairing with the Data Cloud Architect permission set
• OAuth scope cdp_ingest_api on the TPM Offcore connected app
• Licenses: AccrualsProcessingAddOn, AccrualsProcessingUserAddOn, TpmAccrualsAddOn, TpmAccrualsUserAddOn (advisory — record what the user confirmed)

Phase 2 — Verify the Data Cloud connection (best-effort)

Try to verify cdp_ingest_api by query — treat "cannot verify" as WARN, not STOP:

sf data query --target-org <alias> \
  --query "SELECT Id, Name FROM ConnectedApplication WHERE Name LIKE '%TPM%'"

If the query errors on permissions, ask the user to confirm cdp_ingest_api is in Setup → App Manager → (edit TPM Offcore connected app) → OAuth Policies → Selected OAuth Scopes. Continue only after the user confirms.

Phase 3 — Run the setup script

Run the end-to-end setup script from the skill's own root directory. In dry-run mode, pass --dry-run.

node scripts/setup.js --org <alias> --sales-org <salesOrg> [--skip-dataspace] [--dry-run] [--namespace <ns>]

If scripts/setup.js is not accessible in the current working directory, record Phase 3 as not run — script path not accessible in this environment in the Phase 6 report and proceed directly to Phase 4 (query DataKitDeploymentLog for any rows after DEPLOY_BASELINE_TIME).

The script runs these steps in order:

• Step 0 — Prerequisites confirmation (interactive prompt, skipped in dry-run)
• Step 1 — Download CGCloudAddons static resource
• Step 2 — Replace __SF_ORG_ID__ placeholders in data kit metadata
• Step 3 — Deploy TPM Accruals Data Kit metadata (sf project deploy start)
• Step 4 — Deploy Liability Accruals Engine data kit via sfdatakit__DeployDataKitComponents (skips already-deployed components; waits up to 30 min for completion)
• Step 5 — Deploy TPM Accruals data kit via sfdatakit__DeployDataKitComponents (same pattern; also waits for completion)
• Step 6 — Create Data Space (manual prompt — see below; skipped with --skip-dataspace)
• Step 7 — Deploy Accruals Reports metadata with Data Space placeholder replacements (two-pass)
• Step 8 — Deploy TPMAccrualTacticSummary UI component with namespace and Data Space replacements
• Step 9 — Print scheduling instructions

The script pauses at Step 0 (prerequisites confirmation) and Step 6 (Data Space creation). When it pauses, capture the stdout block starting at === Step N: and relay it verbatim to the user. Wait for the user to complete the step before continuing.

Adding the TPMAccrualTacticSummary UI component to the Promotion page is a post-run manual step — the script only prints the instruction. Track it as pending in Phase 6.

On non-zero exit → stop and surface the last 50 lines of stdout. Do not proceed to Phase 4 on a failed script.