---
schema_version: "1"
id: a449ab9a20454af1bc5f1e457f5c5d5f9aa0453693edbc86ffbe9b6889d079b8
title: Creating Job Files for the Omnistudio Build Tool (Managed Package)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_build_tool_adding_job_files.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_build_tool_adding_job_files.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 58de58250100c2465c1c096e4e37744ea2af9d544d545ea475d51ed5b55e5ac9
description: "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."
products:
  - Omnistudio
release: "264"
---
# 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](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/resources-global/_corporate/images/managedpackageicon.png) This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see [Omnistudio Help](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_standard.htm&language=en_US).

## 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

- [Other Job File Settings (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_build_tool_other_job_file_settings.htm&release=264.0.0&type=5 "For the managed package runtime, the job file has a number of additional runtime settings that you can use to define your project and to run exports and deployments run. Modify the default settings only to account for unique issues in your org.")