Sf Vlocity Build Deploy
Orchestrate Salesforce OmniStudio/Vlocity DataPack validate-export-deploy cycles with Vlocity Build job files, retries, and documented failure triage.
Overview
sf-vlocity-build-deploy is an agent skill most often used in Ship (also Build) that orchestrates Vlocity Build DataPack validation, deploy, retry, and diff workflows for OmniStudio/Vlocity on Salesforce.
Install
npx skills add https://github.com/jaganpro/sf-skills --skill sf-vlocity-build-deployWhat is this skill?
- Vlocity Build command flow: packExport, packDeploy, packRetry, packContinue, packGetDiffs
- Job-file patterns for projectPath, queries, manifest UUIDs, autoUpdateSettings, and parallel limits
- validateLocalData before packDeploy with retry/continue paths for partial failures
- Workflow structure inherited from sf-deploy references and deployment transcript examples
- Documents end-to-end Business Internet Plus Product2 bundle deployment transcripts
- Documents packExport, packDeploy, packRetry, packContinue, packGetDiffs command set
Adoption & trust: 700 installs on skills.sh; 418 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a Vlocity DataPack bundle and job file but no repeatable agent playbook for validateLocalData, packDeploy failures, and packRetry without breaking org state.
Who is it for?
Salesforce indie consultants or small pods promoting Vlocity Product2 and related DataPacks with manifest-driven jobs.
Skip if: Teams only using standard Salesforce DX without Vlocity folders, or builders who need unrelated cloud CI templates.
When should I use this skill?
Deploying or retrying Vlocity/OmniStudio DataPacks with Vlocity Build CLI and job files
What do I get? / Deliverables
You get a documented Vlocity Build deployment run with validated local data, executed packDeploy/packRetry steps, and triage notes suitable for the next release or hotfix.
- Executed deployment transcript
- Updated job file with projectPath/manifest
- Retry/diff triage notes
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Ship because the skill centers on packaging and promoting Vlocity DataPacks into target orgs with validateLocalData, packDeploy, and packRetry—not greenfield feature coding. Launch subphase matches production-oriented bundle deployment (e.g. Product2 manifests) and expansionPath vlocity jobs aligned to release cutovers.
Where it fits
Configure projectPath and manifest UUIDs before the first packExport from a vlocity expansionPath.
Run validateLocalData then packDeploy for a Business Internet Plus Product2 bundle with documented transcript.
Use packGetDiffs and packRetry after a partial failure without re-exporting the entire job file.
How it compares
Use instead of generic sf-deploy narratives when expansionPath vlocity and packRetry/packGetDiffs are required—not plain metadata API pushes alone.
Common Questions / FAQ
Who is sf-vlocity-build-deploy for?
Solo Salesforce implementers and small teams running OmniStudio/Vlocity DataPack releases who want agent-guided Vlocity Build command sequences and job-file conventions.
When should I use sf-vlocity-build-deploy?
During Ship launch prep when validating and deploying bundles; in Build integrations when exporting packs from projectPath; and in Operate iterate when retrying failed deploy segments with packRetry/packContinue.
Is sf-vlocity-build-deploy safe to install?
The skill describes deployment orchestration against your Salesforce orgs; review the Security Audits panel on this page and never let an agent run packDeploy against production without human approval and backups.
SKILL.md
READMESKILL.md - Sf Vlocity Build Deploy
# Credits & Acknowledgments This skill is based on practical OmniStudio/Vlocity DataPack deployment workflows and the Vlocity Build command model. ## Primary References - Vlocity Build (official repository): https://github.com/vlocityinc/vlocity_build - Vlocity Build README command and job-file guidance: - `packExport`, `packDeploy`, `packRetry`, `packContinue`, `packGetDiffs` - Job file patterns for `projectPath`, `queries`, `manifest`, and retry/validation flow ## Repository Inputs - `skills/sf-deploy/SKILL.md` (workflow structure template) - `skills/sf-deploy/references/` (deployment orchestration style and report patterns) ## Contributor - Shreyas Dhond (ShreyasD) projectPath: . expansionPath: vlocity manifest: - Product2/9f1d3c4a-8e5b-4d71-9a2d-f6b719a90101 autoUpdateSettings: true defaultMaxParallel: 1 supportHeadersOnly: true gitCheck: false # Deployment Transcript: Business Internet Plus Bundle This transcript captures the skills used plus the planning and execution process for deploying `business-internet-plus-bundle` with Vlocity Build. --- ## Task Summary Deploy the `Business Internet Plus` Product2 bundle DataPack and document the end-to-end process in `sf-vlocity-build-deploy/examples`. --- ## Skills Used ### 1) `sf-vlocity-build-deploy` (Primary) **Why used:** The task is DataPack deployment orchestration with Vlocity Build commands (`validateLocalData`, `packDeploy`, `packRetry`) and failure triage. **Applied guidance:** - Validate-first execution (`validateLocalData` before deployment). - Deterministic job file (`projectPath`, `expansionPath`, `manifest`) for reproducible scope. - Retry loop and failure interpretation. ### 2) `sf-industry-cme-epc-model` (Supporting) **Why used:** The deployment target is an EPC Product2 offer bundle sample with Product Child Item dependencies and companion artifacts. **Applied guidance:** - Confirmed Product2 offer markers and companion file consistency. - Preserved `%vlocity_namespace%` placeholders and stable GlobalKey references. ### 3) `sf-deploy` (Supporting preflight pattern) **Why used:** Reused deployment preflight discipline for target org/tooling readiness and concise completion reporting. --- ## Planning Process (Executed) 1. Confirm where the source bundle artifacts were authored. 2. Stage those artifacts into a standard Vlocity expansion path under `vlocity/Product2/<global-key>/`. 3. Build a deterministic deploy job file in this example folder. 4. Run pre-deploy validation (`validateLocalData`). 5. Run actual deployment (`packDeploy`). 6. Run retry (`packRetry`) to confirm whether the failure is transient or dependency-blocking. 7. Capture findings and next safe action. --- ## Execution Details ### A) Staging for deploy Source payload location: - `skills/sf-industry-cme-epc-model/examples/business-internet-plus-bundle` Deploy staging location: - `vlocity/Product2/9f1d3c4a-8e5b-4d71-9a2d-f6b719a90101` Staged files include: - `Business-Internet-Plus_DataPack.json` - `Business-Internet-Plus_AttributeAssignments.json` - `Business-Internet-Plus_ProductChildItems.json` - `Business-Internet-Plus_PricebookEntries.json` - `Business-Internet-Plus_PriceListEntries.json` - `Business-Internet-Plus_ObjectFieldAttributes.json` - `Business-Internet-Plus_OrchestrationScenarios.json` - `Business-Internet-Plus_DecompositionRelationships.json` - `Business-Internet-Plus_CompiledAttributeOverrides.json` - `Business-Internet-Plus_OverrideDefinitions.json` - `Business-Internet-Plus_ParentKeys.json` ### B) Job file used - `skills/sf-vlocity-build-deploy/examples/business-internet-plus-bundle-deploy/deploy-business-internet-plus-bundle.yaml` Key settings: - `projectPath: .` - `expansionPath: vlocity` - `manifest: Product2/9f1d3c4a-8e5b-4d71-9a2d-f6b719a90101` ### C) Commands executed ```bash npx --yes vlocity -sfdx.username sample-uat -job "skills/sf-vlocity-build-deploy/examples/business-internet-plus-bundle-deploy/deploy-business-inter