Gruppo | Discussione | Salesforce Trailblazer Community

29 ago 2024, 22:37

Hello All!

I'm trying to build out an assessment using the Discovery Framework. One of the questions we have SHOULD result in the creation of related records to the account where the assessment is generated from. From what I've gathered, I need to create the question with the same API name as the data raptor I created to extract existing records. And then I should be able to add inputs inside of the edit block. However, there are no inputs to add even after click the pencil icon on the edit block.

5 risposte

Achref Naggati ☁ (Unio Wealth Management)
7 ott, 20:39
@Brandon LaFave
, This may be a late response, but I wanted to drop it here in case anyone else runs into the same challenge :

The trick is to create the nested block element questions as Assessment Questions, making sure to select Edit Block Question as the Related Question. This way, when you drag and drop the Edit Block Question (Using the discovery framework's edit form feature), all the related questions will automatically be nested underneath it.

One more thing: if the Edit Block Question is already present in the Discovery Framework OmniScript, remove it and drop it back in again. This allows the Discovery Framework functionality to load the nested questions where Edit Block Question is selected as the Related Question.

Aggiungi un commento

Scrivi una risposta...

0/9000

25 set, 07:03

In OmniScript, how can I navigate from Step 2 directly back to Step 7 after clicking Continue, when Step 2 was opened from Step 7 via a custom LWC button?

Hi everyone,

I have an OmniScript with 10 steps/screens, and each screen has a custom LWC Continue button.

My requirement is:

User is currently on Step 7.
Step 7 has another button (e.g., Edit Personal Information).
When the user clicks this button, I navigate the user back to Step 2.
The data on Step 2 is already populated, so the user can review/update it.
When the user clicks the Continue button on Step 2, I want to navigate the user directly back to Step 7, instead of continuing through Steps 3 → 4 → 5 → 6.
All navigation buttons are implemented using custom LWC components.

Question:

Is there a supported way in OmniScript/LWC to navigate directly from Step 2 back to a specific later step (Step 7) of the same parent OmniScript?

I have looked into OmniScript navigation methods, but I haven't found a supported method that allows me to specify a particular step/index to navigate to.

Has anyone implemented a similar Edit → navigate back to the original step

pattern in OmniScript? If so, what would be the recommended approach?

#Omnistudio #Salesforce Developer #Vlocity #Financial Services Cloud #Trailhead

3 risposte

Deepak Sachdeva (Nubys Tech)
29 set, 12:22
Hi @Rahul Khedkar

A common supported approach is to keep the navigation state in the parent OmniScript and treat Step 2 as an edit mode rather than trying to make the Step 2 Continue button directly jump to an arbitrary step index. When Step 7 opens Step 2, store a flag such as returnToStep7 = true in the OmniScript data JSON. Then, on Step 2 Continue, your custom LWC can check that flag and invoke the parent OmniScript navigation logic to return to Step 7; otherwise, it follows the normal Step 2 → Step 3 flow. This avoids hard-coding unsupported step-index navigation inside the LWC and works well for an Edit → Return pattern. If you share your current custom LWC navigation code, I can show the exact implementation for your OmniScript.

Aggiungi un commento

Scrivi una risposta...

0/9000

28 gen, 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]

14 risposte

Vijay Sadhu (Fortune Minds Inc)
22 set, 19:58
https://help.salesforce.com/s/articleView?id=xcloud.os_standard_set_up_your_environment_for_customizing_omniscript_elements.htm&type=5 Need to do these steps on Core to access OmniscriptBaseMixIn.

Aggiungi un commento

Scrivi una risposta...

0/9000

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 risposte

Julia Rösner
3 set, 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!

Aggiungi un commento

Scrivi una risposta...

0/9000

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 risposte

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.

Aggiungi un commento

Scrivi una risposta...

0/9000

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 risposte

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.

Aggiungi un commento

Scrivi una risposta...

0/9000

20 lug, 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 risposte

Buyan thyagarajand (Eigen X)
27 lug, 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?

Aggiungi un commento

Scrivi una risposta...

0/9000

10 lug 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 risposte

Ángel Armando Sangerman Martínez (Valtech‏‏‎ ‎)
22 lug, 15:41
Hello Krishnamurthy, do you achieve to solve your issue?, I am struggling with that

Aggiungi un commento

Scrivi una risposta...

0/9000

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 risposta

Manimaran Gunasekaran (Keneland)
8 apr, 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