Loading

Table of Contents

No results

Here are some search tips

Check the spelling of your keywords.
Use more general search terms.
Select fewer filters to broaden your search.

Search all of Salesforce Help

Search all of Salesforce Help

Omnistudio
Get Started with Omnistudio
Learn about Omnistudio
- Understand Omniscripts
- Understand Flexcards
- When to Use Flexcards and Omniscripts
- When to Use Omnistudio Data Mappers and Integration Procedures
- Integration Procedure Features Not in Omniscripts
- Use the Applications Together
Plan and Prepare for Your Omnistudio Implementation
- Omnistudio Naming Conventions
- Omnistudio sObject Descriptions
- Newport Design System
  - Use the Newport Design System
- Callable Implementations
- Add Apex Class Permissions Checkers
- View the Namespace and Version of Managed Packages
- Standard Omnistudio Content and Runtime
  - View, Modify, and Enable Fast Activation on Omnistudio Content
- Omnistudio Permission Sets
Deployment of Omnistudio Components Between Orgs
- Tool Considerations for Deploying Omnistudio Components
Omnistudio Standard Designer
- Feature Support Changes with Standard Designers
- Enable the Omnistudio Standard Designer
  - Retain the Designer Setting on Org Upgrade
- Best Practices for Using the Omnistudio Standard Designer
- Hide the Omnistudio App While Using the Standard Designer
- Access Omnistudio Designer Components from the List View
- Omnistudio Frequently Asked Questions (FAQs)
- Common Errors and Resolutions in Omnistudio
Omnistudio Limits and Considerations
- Recommended Limits
Security Checks for Omnistudio
Omniscripts
- Working with Omniscripts
  - Export and Import Omniscripts
- Create an Omniscript
  - Considerations for Single-Language Omniscripts
  - Upgrade an Omniscript's Property Set
- Create Multi-Language Omniscripts
- Build an Omniscript with Elements
- Configure Omniscript Settings
- Integrate DocuSign with Omniscripts
- Customize Omniscript Behaviors, Style, and Elements
- Preview and Test an Omniscript
- Activate and Launch Omniscripts
- Omniscript Element Reference
Omnistudio Flexcards
- Working with Flexcards
- Open a Flexcard in a Canvas Instead of the Record Page Detail
- Create a Flexcard
  - Clone a Flexcard or Create a New Version
- Configure Flexcard Settings
- Add Elements to a Flexcard
  - Flexcards Display Elements
  - Flexcards Input Elements
- Set Up Actions on a Flexcard
- Display Data on Flexcards Based on Conditions
- Style a Flexcard
- Preview and Debug a Flexcard
- Activate and Publish a Flexcard
- Export and Import Flexcards
- Flexcards Context Variables
- Flexcards Omni Interaction Access Configuration
Omnistudio Data Mappers
- Working with Omnistudio Data Mappers
  - Export or Import an Omnistudio Data Mapper
- Build an Omnistudio Data Mapper
- Invoke Omnistudio Data Mappers
- Security for Omnistudio Data Mappers and Integration Procedures
- Preview and Test Data Mappers
- Examples of Omnistudio Data Mappers
Omnistudio Integration Procedures
- Work with Integration Procedures
  - Export or Import an Omnistudio Integration Procedure
- Build an Integration Procedure
- Integration Procedures on Agentforce
  - Integrate Integration Procedures with Agentforce
- Invoke an Integration Procedure
- Long-Running Integration Procedures
  - Settings for Long-Running Integration Procedures
    - Invoke a Chainable Integration Procedure with REST Calls
  - Continuation in Long-Running Calls
    - Make a Long-Running Remote Call Using VlocityContinuationIntegration
    - Make a Long-Running Remote Call Using Omnistudio.OmniContinuation
- Security for Omnistudio Data Mappers and Integration Procedures
- Test Procedures: Integration Procedures for Unit Testing
  - Workflow for Test Procedure Example
    - Mock a Response in the Tested Integration Procedure
    - Create an Example Test Procedure
- Integration Procedure Actions
- Integration Procedure Blocks
Omnistudio Design Assistant
- Monitor and Manage Your Flexcards and Omniscripts
Use Custom Numbering with Omni Global Auto Number
- Set Up Omni Global Auto Numbers
Automated Testing with UTAM for Omnistudio
- UTAM Testing Workflow
- How to Write End-to-End Tests with UTAM for Flexcards
  - Sample Flexcard Test (Java)
- How to Write End-to-End Tests with UTAM for Omniscripts
  - Sample Omniscript Test (Java)
Agentforce for Omnistudio (Pilot)
- Subagents for Omnistudio (Pilot)
Use the Omnistudio MCP (Beta)
Omnistudio Formulas and Functions
- Supported Data Mapper and Integration Procedure Data Types
- Supported Data Mapper and Integration Procedure Operators
- Supported Data Mapper and Integration Procedure Functions
- Sample Apex Code for Custom Functions
Using OmniAnalytics to Track User Engagement in Omniscripts and...
- Enable OmniAnalytics and Store Tracking Data
- Configure Internal OmniAnalytics
- Configure OmniAnalytics with Google Analytics
- Create Google Analytics Trusted URLs
- Adding Ecommerce Data to the Example Omniscript for OmniAnalytics
  - Add Google Tag Manager Data to the Example Omniscript Setup
  - Add Google Tag Manager Data to the Example Omniscript Steps
- Setting Up Third-Party Tracking and Event Types
Omnistudio Lightning Web Components
- Set Up Lightning Web Components
- Extend Omnistudio Lightning Web Components
- Deploy Lightning Web Components
- Base Omnistudio LWC ReadMe Reference
Omnistudio on Experience Cloud
Omnistudio Usage

Customize Omniscript Behaviors, Style, and Elements

You are here:

Customize Omniscript Behaviors, Style, and Elements

To meet your business needs and improve user experience, you can customize Omniscripts for their style and appearance and for their actions. Apply custom styling via static resources, global stylesheets, or SLDS design tokens. Modify Omniscripts to conditionally hide or show elements and errors and to trigger platform events. For more complex customization, you can extend Omniscript elements to add custom behavior and styling. Finally, you can create custom Lightning web components (LWCs) to add custom HTML, JavaScript, and CSS.

Custom Styles for Omniscripts
Add custom styling to Omniscripts by using static resources, overriding global stylesheets, or using SLDS design tokens. View the behavior of each customization option in this page's table, and choose the solution that meets your requirements.
Modify Omniscript UI Behavior
You modify UI behaviors in an Omniscript to hide or show elements and errors conditionally. You can also trigger Salesforce platform events. When previewing large Omniscripts, you can hide the userProfile node.
Customize Omniscript Elements
Add custom behavior and styling to an Omniscript element by extending the functionality of an Omniscript element. By extending the Omniscript component, you modify its properties and add new properties. Then, replace or override the Omniscript element's Lightning web component with the customized component in the designer to use the customized component at run time.
Create a Custom Lightning Web Component for Omniscript
Add custom HTML, JavaScript, and CSS to an Omniscript by creating a custom Lightning web component. The Custom LWC element enables custom components to either interact with the Omniscript or to act as a standalone component. Standalone components do not interact with the Omniscript or the Omniscript's data JSON.
Omniscript ReadMe Reference
This page lists the Lightning web components ReadMes available for Omniscripts. Extend Lightning web components to add custom behavior and styling.

Did this article solve your issue?

Let us know so we can improve!

Loading

Salesforce Help | Article