Skip to main content
GruposSalesforce OmniStudio Developer
Grupo

Salesforce OmniStudio Developer

This group is to support development using Salesforce OmniStudio (Earlier known as Vlocity Digital Interaction Platform). Training Org: https://www.salesforce.com/form/signup/financial-services-cloud-trial Trailmix: https://trailhead.salesforce.com/en/content/learn/trails/build-guided-experiences-with-omnistudio Developer Documentation: https://help.salesforce.com/s/articleView?id=sf.os_omnistudio.htm&type=5
Formular una pregunta...
Shreya Roy (Packaged App Development Analyst en Accenture)
14 mar 2024, 08:05
Error: Definition for module "forceGenerated/omniScript_abcd___AccountClassification___English___lightning___false___brand___ltr" was not found.

I have an omniscript which is active and loading fine for System Admins but showing error Error: Definition for module "forceGenerated/omniScript_abcd___AccountClassification___English___lightning___false___brand___ltr" was not found for other profile users. The user already have Omnistudio user permission set assigned and with similar settings working perfectly in other org but after deployment to upper org its throwing this error. Can anyone help me?

3 respuestas
  1. Julia Rösner
    3 sept, 11:40

    I noticed that you have to assign the users to the library which is referenced by the document template. To do that, you open Salesforce Classic, open the library, and assign the user or profile/public group to the library. 

     

    Hope that helps!

Escribir una respuesta...
0/9000
Santosh Umate (Salesforce Developer en Tata Consultancy Services)
28 ene, 07:05
Omnistudio Standard Runtime No MODULE named markup://omnistudio:omniscriptBaseMixin found : [markup://c:customToggleButton]

Hi All,  

I am using standard runtime Omnistudio which is trail org, I have created a Toggle lwc component and want to use that on Omniscript but I am getting No MODULE named markup://omnistudio:omniscriptBaseMixin found : [markup://c:customToggleButton] while deploying lwc component. Any Idea on this issue. 

 

Omnistudio Standard Runtime No MODULE named markup://omnistudio:omniscriptBaseMixin found : [markup://c:customToggleButton]

 

 

13 respuestas
Escribir una respuesta...
0/9000
Buyan thyagarajand (Partner en Eigen X)
15 ago, 14:28
Does it make sense to have separate dev sandboxes for omnistudio development

Hi Guys, 

We have a team of omnistudio developers around 5 to 10 who are working on multiple usecases on our project. Currently we have one dev sandbox where our developers are working and have a source control tool with Copado for deployments. The work is already partitioned in a way that there is no overlap on the components and  each developer is working on their own module with no conflicts. We have leadership asking on why we cannot have individual dev sandboxes for each developer compared to one sandbox which is quite the norm on standard apex salesforce development.  I have been told that there is a lot of manual config work which needs to be done for deployments if we have more sandboxes increasing the deployment time. I would like to know the pros and cons of having an individual sandbox compared to one sandbox with work managed to avoid conflicts and considerations I need to be aware of to manage deployment and code conflicts better. 

Buyan

4 respuestas
  1. Simran Sharma (Growth Natives)
    19 ago, 10:41

    I wouldn’t create individual sandboxes just because that is common for Apex. If OmniStudio work is already split cleanly and Copado is handling deployments, one shared dev sandbox can still work. 

      

     I’d add separate sandboxes only if conflicts or release collisions are actually slowing the team down. Otherwise, you may create more environment drift and deployment cleanup than you solve. 

     

Escribir una respuesta...
0/9000
Matthew Comer (Principal en CapTech)
12 ago, 15:44
Omni on LWR?

Hey everyone, quick question: we just run into something odd which I can't believe is still the case. We're working on a project and are in the early stages, just getting all of the discovery work done, some infrastructure setup work, very early development for some demos to help with requirements gathering, etc. We've setup a quick LWR Experience Cloud site and tried to drop an OmniScript on a page to show the client agency the art of the possible for their web forms - only to discover that we have to contact Salesforce support to enable Omni on LWR? Really? Is LWR not mainstream at this point, pretty much the default for any new Experience Cloud sites? Is there any reason that standard runtime and LWR shouldn't just work together transparently at this point? It makes me a little nervous that we have to reach out to support to enable this.

6 respuestas
  1. Matthew Comer (CapTech)
    14 ago, 12:20

    Well, after working with support it turns out this is a known issue: 

     

    https://help.salesforce.com/s/issue?id=a02g7000006WSlhAAG

     

    https://help.salesforce.com/s/issue?id=a02Ka00000lbMcqIAE

     

    https://help.salesforce.com/s/issue?id=a02Ka00000jhXoxIAE

     

    I am a little bit shocked and concerned by this. Apparently this issue was reported nearly a year ago and is still not resolved. If I am reading these correctly the reality is that OmniScript on LWR simply 

    does not work right now, period. (This issue is the clearest about this: https://help.salesforce.com/s/issue?id=a02g7000006WSlhAAG

    )  

    Something big like this stays broken for almost a year? 

     

    The fix is scheduled for Winter '27. Preview starts in a few weeks so at least we should be able to see if this is fixed in a sandbox soon.

Escribir una respuesta...
0/9000
Buyan thyagarajand (Partner en Eigen X)
20 jul, 18:53
Questions on measuring performance of Omni load times and Submit times

Hi Guys, 

We have a giant 40- to 50-step Omniscript multistep wizard that we use to capture claims for one of our federal clients. There have been complaints from users about Omniscript performance, which I understand can be subjective. I would like to know how we measure Omni load times: when the form loads with pre-populated data, and once they click submit, how much time it takes to store all the data and load the next page? I know in LWC we can use browser tools and measure EPT. How do you guys measure performance in Omniscript? 

Buyan

2 respuestas
  1. Buyan thyagarajand (Eigen X)
    27 jul, 09:52

    Hi @Harsh Veer Nirwan Thanks for answering it and it seems your answer might have been cut off on this thread. I would appreciate if you could explain the two layers and how can we measure performance?

Escribir una respuesta...
0/9000
Krishnamurthy KA (Senior Application Development Analyst en Accenture)
10 jul 2025, 02:46
LWC Component Override for Messaging Element

I’m working on overriding the standard Messaging element in OmniScript using a custom LWC that extends OmniscriptAtomicElement via LWC Component Override.  

 

The UI renders fine, but I’m running into a key issue: I need to conditionally show or hide the message based on a formula field in the OmniScript data JSON (e.g., IsAvailable). This formula evaluates to true/false based on field selections in the same step. However, inside my LWC, this.omniJsonData always returns undefined, so I can’t access the value.

 

Here’s what I’ve tried so far:

 

  • I’ve extended from OmniscriptAtomicElement as required for element overrides.
  • I attempted to mix in OmniscriptBaseMixin to access OmniScript’s reactive props like omniJsonData, omniJsonDef, etc., but that didn’t work either (it throws errors or breaks the override structure).
  • I also verified that the formula field is part of the current OmniScript data node and accessible if I preview the OmniScript.
  • I even tried putting the omniDataJson in connectedCallback() and stateRefresh() but both still result in undefined data.

 

My main issue is that I don't know how to pass the data from the Omniscript to the override LWC to do validation checks or post processing logic.  

 

#Salesforce Developer @Nick Maio @Riyaz Usman Appreciate your help.

2 respuestas
Escribir una respuesta...
0/9000
Shashank Chauhan (Web Application developer en Onelogica)
3 feb, 06:46
Has anyone encountered a limitation in OmniScript step navigation where a user cannot return directly to the last completed step?

I have an OmniScript built using Salesforce Industries that contains 10 sequential steps. A user completes all 10 steps successfully and then navigates back to a previous step using the Back button.

When the user proceeds forward again, the OmniScript forces the user to go through all intermediate steps instead of allowing them to return directly to Step 10, even though all steps were already completed once.

Has anyone encountered this behavior in OmniScript? 

 Is this an expected

platform limitation, or is there a configuration or design pattern that allows users to jump directly back to the last completed step without re-entering the middle steps?

If this is not supported out of the box, what are the recommended workarounds (for example, Review Step pattern or alternative OmniScript design)?

1 respuesta
  1. Manimaran Gunasekaran (Keneland)
    8 abr, 18:29

    Yes, this is a known platform behavior in OmniScript. The sequential step navigation is by design - OmniScript's Back button re-evaluates each step in order to ensure data integrity and conditional logic is correctly reapplied. This behavior exists because subsequent steps may have dependencies on values entered in intermediate steps.

     

    Here are the recommended approaches to achieve direct navigation to the last completed step:

     

    1. Review Step Pattern: Add a dedicated "Review" step at the end of the OmniScript (Step 10). On this step, display all the collected data in a summary format using Display Text elements or Datatable. Add an Edit button for each section that uses the "Navigate to Step" action to jump directly to a specific step. This is the standard Salesforce-recommended pattern for multi-step forms.

     

    2. Custom Navigation Action: Use a Custom LWC action in the OmniScript that calls the omniNavigateTo() method to programmatically jump to a specific step number. Combine this with storing the "last completed step" in an OmniScript variable so you can recall the user's progress.

     

    3. Save and Resume Pattern: Use OmniScript's built-in Save & Resume functionality. Users can save their progress and when they return, they are taken directly to the step where they left off, bypassing the intermediate steps. Enable this in the OmniScript Properties by enabling "Save State".

     

    4. Flatten the Step Structure: If the 10 steps are logically grouped, consider using a single step with multiple sections and show/hide logic (using conditional rendering) to simulate multi-step behavior while technically being on one step. This gives the most flexible navigation.

     

    For most implementations, the Review Step + Navigate to Step combination (Option 1) is the most user-friendly and maintainable approach.

     

    Mani G | Principal/Founder | https://Keneland.com

Escribir una respuesta...
0/9000
ANJALI VISHWAKARMA (Salesforce developer en Pletra technologies)
8 jul, 09:26
I am unable to activate the omni script , please help me with the solution for the same .

I am unable to activate the omni script , please help me with the solution for the same . 

 

I am unable to activate the omni script , please help me with the solution for the same .

 

 

2 respuestas
Escribir una respuesta...
0/9000
Bosede Omolayo (Consultant en Self)
4 jul, 18:32
OmniStudio Integration Process record name update - is there an efficient way to update rather than updating manually?

I signed up for FSC trial org to enable OmniStudio for use but the toggle fails with no error description in the email received. From web research findings, all OmniStudio component name should not have spaces or special characters. 

Question: Does anyone know a better way to update Omnistudio Integration Process record name.  Is this the root cause of the error or are there other reasons the OmniStudio enable toggle fails in FSC trial org? Note I installed the current OmniStudio Package, Post installation settings also done. The Omnistudio Integration Process record Type and Subtypes are in the right format. Thank you.

3 respuestas
Escribir una respuesta...
0/9000
David Boada (Salesforce Developer/Consultant en Allied Global)
30 sept 2025, 15:05
Could not save new Omniscript

I'm completely new to Omnistudio, I just finished installing it following the salesforce guide: https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_release_summary_for_installation_and_upgrade.htm&type=5

, I've made sure my user has the Omnistudio Admin assigned and has visibility over the Omniprosess object and fields, however, when I try to create a new Omniscript I face this error, I have no idea if I maybe missed a step or something, or some aditional configuration is missing besides the permission sets, I appreciate any help, I can provide any other information needed, I've spent some hours trying to debug and tinkering with permissions but the error is still there. 

 

 

Could not save new Omniscript

 

 

2 respuestas
  1. Pedro Henrique (Accenture Brasil)
    1 jul, 17:36

    In this case, the error is caused by the "Language" field; it is a picklist value containing special characters in the *MasterLabel*. If you select a different value that does not contain them, you can successfully create the OmniScript.

Escribir una respuesta...
0/9000