Salesforce Docs Portal

Creating Job Files for the Omnistudio Build Tool (Managed Package)

For the managed package runtime, when you define your project through a manifest, we recommend that you create two job files: one for export and one for deployment.

Managed Package app icon This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.

Export Job File

The export job file exports only the listed manifest items and their dependencies. For someone working on a set of products, the job file would look like this Export.yaml example:

projectPath: .
expansionPath: vlocity
manifest:
- Product2/1b1b6c6f-c1b0-1c1d-e068-4651202cb07b
- Product2/6e28982d-57c8-5bd3-e6db-d66c02c20e43
- Product2/7e0b4fa5-4290-d439-ba96-f1a1c3708b0b
- Product2/9a86f5d9-2e05-ef0d-3492-3479db233ef8

Running packExport -job Export.yaml also exports any data packs that these products depend on. To export only the exact manifest, add -depth 0 to your command.

Deployment Job File

The manifest also controls what is deployed. Only what’s specified is deployed. You can deploy a specific set of local folders to the org because data pack keys are the folder paths of the data packs.

For best results, create a second job file for deployment. This job file needs only the project path because it deploys the entire contents of the project by default. For example, the Deploy.yaml job file has these lines: 

projectPath: .
expansionPath: vlocity

packDeploy -job Deploy.yaml deploys all of the data packs in the folder because no manifest is defined.

See Also