---
schema_version: "1"
id: ba1471698a973f4262361f6f16dc13ce84ab550f97315c6d3d296ad79329f77c
title: IDX Workbench Desktop Application (Managed Package)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_idx_workbench_desktop_application.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_idx_workbench_desktop_application.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 52584a88c9348e4cfe1a4cebeb647096814150418cfaad807828be22c2c555b5
description: For the managed package runtime, IDX Workbench is a desktop application that you use to deploy Omnistudio data packs and Salesforce metadata. Its user interface is built on top of the Omnistudio Build Tool. The application is available for Mac and Linux.
products:
  - Omnistudio
release: "264"
---
# IDX Workbench Desktop Application (Managed Package)

For the managed package runtime, IDX Workbench is a desktop application that you use to deploy Omnistudio data packs and Salesforce metadata. Its user interface is built on top of the Omnistudio Build Tool. The application is available for Mac and Linux.

![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).

Deployment is supported:

- From one Vlocity org to another
- From a Vlocity org to a Git repository
- From a Git repository to a Vlocity org
- From the Vlocity Process Library to a Vlocity org
- From a JSON file to a Git repository or a Vlocity org

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/images/icon_note.png)

Note

We recommend the [Omnistudio Build Tool](https://help.salesforce.com/s/articleView?id=xcloud.os_data_deployment_with_build_tool.htm&release=264.0.0&type=5 "For the managed package runtime, the Omnistudio Build Tool (formerly Vlocity Build Tool or VBT) is a Node.js command-line automation tool that packages and deploys Salesforce data packs in a source-control-friendly format. The tool creates a YAML (YAML Ain’t Markup Language) manifest that describes a deployment project. The Build Tool enables continuous integration of Omnistudio metadata to source control.") for deploying Omnistudio components between orgs. It ensures that the deployment includes dependencies, it validates deployment success, and you can use it with automated deployment, such as scripts or Jenkins.

Components are packaged as data packs, which are optimized for source control and deployment to other orgs. For example, you can develop apps on a dedicated development org. Then, use IDX Workbench to deploy them to a QA org until they’re ready for use in production, and then deploy from your QA org to production orgs.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/images/icon_note.png)

Note

You can import data packs of some older Omnistudio for Managed Packages objects into an Omnistudio Standard org. Omnistudio Data Mapper, Integration Procedure, and LWC-enabled Omniscript custom objects are automatically converted to standard objects.

Importing data packs of standard objects into an Omnistudio for Managed Packages org isn't supported. Importing Cards between Omnistudio and Omnistudio for Managed Packages orgs isn't supported.

See [Differences Between Omnistudio and Omnistudio for Managed Packages (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_differences_between_omnistudio_and_omnistudio_for_vlocity.htm&release=264.0.0&type=5 "For the managed package runtime, Omnistudio and Omnistudio for Managed Packages differ in a few ways, but the key differences are the data models, the features available in each, and how you access each suite depending on your org licenses. Think of Omnistudio and Omnistudio for Managed Packages as two versions of an application suite, not two types of packages. While Omnistudio uses the standard object model, Omnistudio for Managed Packages uses the custom object model. That difference is why the two versions don’t have exactly the same features.").

When you choose a component for deployment, IDX Workbench ensures that its dependent components are included. For example, if you deploy an Omniscript that requires a Data Mapper, that Data Mapper is packaged for deployment with the Omniscript.

In IDX Workbench, you define the source org or repository, the target org or repository, and the components to be deployed. You must create this definition before you can deploy. Deployment is one way, from source to target. Source components overwrite target components of the same name and type.

If you need a command-line client for scripting deployment, download and use the [Build Tool](https://www.npmjs.com/package/vlocity).

- **[Install IDX Workbench (Alpha) (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_install_idx_workbench.htm&release=264.0.0&type=5)**  
    For the managed package runtime, to deploy changes to Omnistudio components, download and install the IDX Workbench application.
- **[Configure LWC Omniscript and Flexcard Activation and Compilation (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_configure_lwc_omniscript_and_flexcard_activation_and_compilation.htm&release=264.0.0&type=5)**  
    For the managed package runtime, if Google Chrome is your default browser and IDX Workbench logs you into your source and target orgs through it, you can skip this task. When you deploy Omniscripts, Integration Procedures, and Flexcards, they’re automatically activated in the target org. However, if you use a different browser, you must configure this automatic activation feature manually.
- **[IDX Workbench Configuration for Deployment (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_idx_workbench_configuration_for_deployment.htm&release=264.0.0&type=5)**  
    For the managed package runtime, before you can deploy components, you must specify the source, the target, and the objects to be deployed. The source can be an org, a Project object in an org, a JSON file, the Vlocity Process Library, or a Git repository. The target can be an org or a Git repository.
- **[Object Deployment and Comparison (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_object_deployment_and_comparison.htm&release=264.0.0&type=5)**  
    For the managed package runtime, after you have configured a project, you can deploy objects from the Source to the Target. After the initial deployment, you can compare objects in the Source and Target to see if any have been updated and need to be deployed again. You can also save objects in the Source to DataPacks.
- **[Use the IDX Workbench Process Profiler (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_use_the_idx_workbench_process_profiler.htm&release=264.0.0&type=5)**  
    For the managed package runtime, the Process Profiler lets you view the Tracking Service data for an object in a source or target org.
- **[Compare Omniscript and Integration Procedure Versions (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_compare_omniscript_and_integration_procedure_versions.htm&release=264.0.0&type=5)**  
    For the managed package runtime, the Version Compare dashboard lets you compare two versions of an Omniscript or Integration Procedure in the same Source or Target org.
- **[Run Test Procedures (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_run_test_procedures.htm&release=264.0.0&type=5)**  
    For the managed package runtime, the Test dashboard lets you run Test Procedures (Integration Procedures that perform unit tests) and analyze the results of the tests.
- **[IDX Workbench Menu Commands (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_idx_workbench_menu_commands.htm&release=264.0.0&type=5)**  
    For the managed package runtime, most of the commands in the IDX Workbench menus are like those of any application. For example, **Edit** | **Copy** copies the selected text. Commands specific to IDX Workbench are listed here.