--- schema_version: "1" id: 256f357e4c7a605b2079fcf9f9787fc626a6fbcbc4324012b2d195d3dcdc7656 title: Omnistudio Standard Designer collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_designers_common.md canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_designers_common.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: fcb946a18bac642afbd44e1e7c3e1ddad98677fda1a612037147ae28e5078854 description: In addition to the managed package designer, Omnistudio offers a standard designer for Flexcards, Omniscripts, Integration Procedures, and Data Mappers in the standard runtime. The standard designer provides ease of navigation and improved performance. All the existing elements and configurations from the managed package designer are available in the standard designer. products: - Omnistudio release: "264" --- # Omnistudio Standard Designer In addition to the managed package designer, Omnistudio offers a standard designer for Flexcards, Omniscripts, Integration Procedures, and Data Mappers in the standard runtime. The standard designer provides ease of navigation and improved performance. All the existing elements and configurations from the managed package designer are available in the standard designer. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio-264-0-0-production-enus/f526eaa8-ae05-487a-8944-4bb99b0b78ac/images/icon_note.png) Note The standard designer is available with Omnistudio only on the standard runtime. For new users, the standard designer is enabled by default. For existing users using the standard runtime, the standard designer is enabled by default after upgrading to Summer '25. If you enabled an Omnistudio license in Spring '25 without a package installation, you can get the Omnistudio standard designer by requesting for it with Salesforce Customer Support. Alternatively, you can install a Summer '25 managed package in your org and enable the relevant Omnistudio settings. Omnistudio standard designer provides these benefits for each component, as compared to the managed package designer. - Flexcard: Use this designer to create Flexcards in fewer steps. Drag elements to the canvas and edit their properties simultaneously, without switching between tabs. Dragging elements to the canvas is now twice as fast. Flexcard activation is up to 7 times faster. ![Flexcard standard designer](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio-264-0-0-production-enus/f526eaa8-ae05-487a-8944-4bb99b0b78ac/omnistudio/images/flexcard_252_designer.png) - Omniscript: Drag elements to the canvas twice as fast and edit their properties simultaneously, without switching between tabs. Omniscript activation is up to 6 times faster. ![Omniscript standard designer](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio-264-0-0-production-enus/f526eaa8-ae05-487a-8944-4bb99b0b78ac/omnistudio/images/omniscript_252_designer.png) - Integration Procedure: Create Integration Procedures up to 2.5 times faster than before. Access Integration Procedure settings in a single click and configure Integration Procedures in fewer steps. Easily insert, edit, or rearrange elements between blocks by using connectors. Drag elements to the canvas up to 7 times faster than before. ![New Integration Procedure in Omnistudio standard runtime](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio-264-0-0-production-enus/f526eaa8-ae05-487a-8944-4bb99b0b78ac/omnistudio/images/integration_procedure_252_designer.png) - Data Mapper: Create Data Mappers up to 6 times faster than before. Effortlessly access Data Mapper settings and visualize connections between objects. ![New Data Mapper in Omnistudio standard runtime](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio-264-0-0-production-enus/f526eaa8-ae05-487a-8944-4bb99b0b78ac/omnistudio/images/data_mapper_252_designer.png) ![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio-264-0-0-production-enus/f526eaa8-ae05-487a-8944-4bb99b0b78ac/images/icon_important.png) Important The performance figures in this document are provided for informational purposes only and are based on internal validation and testing under specific conditions. Actual results may vary depending on your component design, production environment, and other factors. These figures provide ‌general guidance and aren't a guarantee of performance. All elements from the managed package designer are supported in the standard designer. Due to some considerations, you might still want to switch to the managed package designer after using the standard designer. Note that after you switch back to the managed package designer, you can't view or edit components made in the standard designer. However, you can still reference these components in runtime. For a complete list of supported features across both managed package and standard designers, see [Supported Features in Omnistudio and Omnistudio for Managed Packages](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_and_omnistudio_for_vlocity_products_and_features_support.htm&type=5&language=en_US). For a focused list of feature support changes with the standard designer, see [Feature Support Changes with Standard Designers](https://help.salesforce.com/s/articleView?id=xcloud.os_feature_compatibility_standard_designers.htm&release=264.0.0&type=5 "This table provides major feature support differences. It doesn't cover all supported features across both Omnistudio managed package and standard designers."). - **[Feature Support Changes with Standard Designers](https://help.salesforce.com/s/articleView?id=xcloud.os_feature_compatibility_standard_designers.htm&release=264.0.0&type=5)** This table provides major feature support differences. It doesn't cover all supported features across both Omnistudio managed package and standard designers. - **[Enable the Omnistudio Standard Designer](https://help.salesforce.com/s/articleView?id=xcloud.os_enable_standard_omnistudio_designer.htm&release=264.0.0&type=5)** The standard designer is available to new and existing users by default, depending on the Omnistudio license and version in your Salesforce org. If necessary, you can switch to the managed package designer. However, if you switch to the managed package designer, you can't edit components that are created or modified using the standard designer. - **[Best Practices for Using the Omnistudio Standard Designer](https://help.salesforce.com/s/articleView?id=xcloud.os_best_practices_for_using_the_omnistudio_standard_designer.htm&release=264.0.0&type=5)** To troubleshoot an issue or to test new workflows, we recommend that you use a cloned Salesforce org. To directly use the standard designer in your sandbox and production environments, create a new version of your Omnistudio components and validate them in the standard designer. When you use the standard designer in your test orgs for the first time, open all Omnistudio components from the list view page. - **[Hide the Omnistudio App While Using the Standard Designer](https://help.salesforce.com/s/articleView?id=xcloud.hide_omnistudio_app.htm&release=264.0.0&type=5)** To enable better performance and faster load times for list views, hide the Omnistudio app from App Launcher and make component search the default option for your org. This way, users can search for Flexcards, Omniscripts, Integration Procedures, or Data Mappers directly, instead of searching for the Omnistudio app. - **[Access Omnistudio Designer Components from the List View](https://help.salesforce.com/s/articleView?id=xcloud.os_access_standard_designer_components_from_the_list_view.htm&release=264.0.0&type=5)** View your Flexcards, Omniscripts, Integration Procedures, and Data Mappers on the list view pages, and open them in the standard designer. The list view page for the standard designer offers an enhanced user experience and better performance, when compared to the managed package designer. - **[Omnistudio Frequently Asked Questions (FAQs)](https://help.salesforce.com/s/articleView?id=xcloud.os_frequently_asked_questions.htm&release=264.0.0&type=5)** Get answers to common questions about using the Omnistudio standard designer. - **[Common Errors and Resolutions in Omnistudio](https://help.salesforce.com/s/articleView?id=xcloud.os_common_errors_and_resolutions.htm&release=264.0.0&type=5)** Find out why some errors occur and how to resolve them #### See Also - [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.") - [Export and Import Flexcards](https://help.salesforce.com/s/articleView?id=xcloud.transfer_flexcards_and_sample_data_packs.htm&release=264.0.0&type=5 "Import or export Flexcards 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 Flexcards, 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.") - [Export or Import an Omnistudio Data Mapper](https://help.salesforce.com/s/articleView?id=xcloud.os_export_or_import_an_omnistudio_data_mapper.htm&release=264.0.0&type=5 "Export or import Data Mappers to use them in another org, such as when you create them in a sandbox. When exporting or importing data packs for Data Mappers, 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.") - [Export or Import an Omnistudio Integration Procedure](https://help.salesforce.com/s/articleView?id=xcloud.os_export_or_import_an_omnistudio_integration_procedure.htm&release=264.0.0&type=5 "Export or import Integration Procedures to use them in another org, such as when you create them in a sandbox. When exporting or importing data packs for Integration Procedures, 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.") - [Differences Between Lightning and TinyMCE Rich Text Editors](https://help.salesforce.com/s/articleView?id=xcloud.os_differences_between_lightning_and_tinymce_rich_text_editors.htm&release=264.0.0&type=5 "Omnistudio integrates the TinyMCE editor in the standard designer and managed package designer. However, you can switch to Lightning Rich Text Editor, if needed. Review the key differences between these editors. Before implementing any use cases with the Lighting Rich Text Editor, contact Salesforce Customer Support.")