---
schema_version: "1"
id: a2cc69e1c16c33d9f6ceb5fb44df675fff2778ab51712759be3a71f05a923e97
title: Working with Omniscripts
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/omniscript_workflow.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.omniscript_workflow.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 8610144786b80c5ff32394104cd8ee541af8d262dbee39496a362ef2c03f4a18
description: Use the Omniscript Builder to create and manage guided, interactive processes. Retrieve, update, and add data to a variety of sources with elements for Data Mappers, Integration Procedures, REST APIs, and Apex. Or allow users to add or modify data with input fields. Drag Omnscript elements to the canvas and edit properties without changing tabs. Omniscript activation is instant.
products:
  - Omnistudio
release: "264"
---
# Working with Omniscripts

Use the Omniscript Builder to create and manage guided, interactive processes. Retrieve, update, and add data to a variety of sources with elements for Data Mappers, Integration Procedures, REST APIs, and Apex. Or allow users to add or modify data with input fields. Drag Omnscript elements to the canvas and edit properties without changing tabs. Omniscript activation is instant.

This diagram shows the high-level workflow for Omniscripts in the new designer and the designer on a managed package:

![Omniscript workflow](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio-264-0-0-production-enus/f526eaa8-ae05-487a-8944-4bb99b0b78ac/omnistudio/images/Omniscript_Flowchart.png)

1. Create the Omniscript with a unique combination of Type, Subtype, and Language.
    
    See [Create an Omniscript](https://help.salesforce.com/s/articleView?id=xcloud.os_create_an_omniscript_8570.htm&release=264.0.0&type=5 "Create an Omniscript to build a form in the Omniscript Designer.") or [Create Multi-Language Omniscripts](https://help.salesforce.com/s/articleView?id=xcloud.os_create_multi_language_omniscripts_20695.htm&release=264.0.0&type=5 "Enable a single Omniscript to run in multiple languages using custom labels.").
2. Configure optional settings for your Omniscript, such as making your Omniscript reusable. Create the logic based on your requirements by building a hierarchical structure of action elements and steps in the Omniscript.
    
    See [Configure Omniscript Settings](https://help.salesforce.com/s/articleView?id=xcloud.os_set_up_an_omniscript_8598.htm&release=264.0.0&type=5 "Configure optional settings for your Omniscript in the Setup panel of the Omniscript Designer, such as making your Omniscript reusable or enabling logging.") and [Omniscript Element Reference](https://help.salesforce.com/s/articleView?id=xcloud.os_omniscript_element_reference_10533.htm&release=264.0.0&type=5 "The available elements are Omniscripts are organized as groups, Data Mapper actions, standard actions, display elements, functions, input, and Omniscripts (to embed reusable Omniscripts). Each element uses an extendable Lightning web component (LWC).").
3. Verify the Omniscript's appearance and functionality by previewing the Omniscript. Test your Omniscript by adding test data, viewing the data JSON, and debugging action requests and response data.
    
    See [Preview and Test an Omniscript](https://help.salesforce.com/s/articleView?id=xcloud.os_preview_an_omniscript_8849.htm&release=264.0.0&type=5 "View the Omniscript's appearance and functionality by previewing the Omniscript in the Omniscript Designer.")
4. After you confirm that the Omniscript is ready, activate it. Make an active Omniscript available for launch:
    
    - In the new designer, launch the Omniscript as a URL.
    - In the designer for a managed package, launch the Omniscript as a standalone Lightning web component on a Lightning web page, as an embedded link in another LWC or as a URL.
    
    See [Activate and Launch Omniscripts](https://help.salesforce.com/s/articleView?id=xcloud.os_activate_and_deploy_omniscripts_19760.htm&release=264.0.0&type=5 "Make Omniscripts available to Experience Sites, Lightning Pages, custom LWCs, and Lightning tabs by activating and launching the Omniscript. If an error occurs during deployment, the Omniscript is deactivated.").

- **[Export and Import Omniscripts](https://help.salesforce.com/s/articleView?id=xcloud.os_export_omniscripts_23953.htm&release=264.0.0&type=5)**  
    Export or import Omniscripts to use them in another org, such as when you create them in a sandbox or to use sample data packs that Salesforce provides. When exporting or importing data packs for Omniscripts, if you encounter Apex limit errors such as heap or CPU limits, reduce the size of the data pack by unselecting dependencies during the export process. Additionally, break the data pack into multiple smaller data packs. As a best practice, we recommend including no more than 10 elements in each data pack.