Lessons learned from migrating from Angular OmniScript to LWC OmniScript

Scroll for more

Lessons learned from migrating from Angular OmniScript to LWC OmniScript

Now that Salesforce has acquired Vlocity, they are making a few changes to the way things are done and what tools will be supported in the future. One of the changes is the move from Angular OmniScript to LWC OmniScript. In this article, we look at how to migrate from AngularJS OmniScript to Salesforce Lightning Web Component (LWC) OmniScript. Want to learn more about Salesforce Industries? Then read our blog, "What is Salesforce Industries CPQ? Or '7 secret migration pitfalls from Product Console to Product Designer' to learn more.

Deep Dive Series 3

Salesforce will soon stop using AngularJS in favor of the LWC framework. One of the reasons for the push to LWC OmniScript was the announcement that Google would end support for AngularJS as of Dec. 31, 2021. Without Google support and thus regular updates, security vulnerabilities could be exploited, causing huge problems over time.

This past year, I had the opportunity to lead a migration from AngularJS to LWC OmniScript on a project for an Energy & Utilities client.

I am going to discuss my experience dealing with migration to give others an idea of what to expect.

The overall experience

No multilingual support

One of the first challenges I ran into was that LWC OmniScript does not support multi-language. AngularJS OmniScript has native support for multi-language. The lack of support at the start made it challenging to convince the client to move forward with this project.

Initially, we started with Dutch OmniScripts. After I ironed out the inefficiencies, it worked reasonably well. One challenge we still face is that when you have a few OmniScripts, the labels are in one big pile. Then you have to search this stack and try to match the label with the correct OmniScript.

After this project, multilingual support did become available. We slowly started converting the client.

Uniform UX and UI

I found the LWC OmniScript tool much nicer to work with when I got started. It integrates very well with the Lightning Design System. With its functionality and extensive feature list, it seemed like it would take some time to master. However, after the expected initial learning curve and getting used to the tool, I realized how intuitive and easy to use it is, especially since the UX and UI are so accessible.

Unlike some other design tools I have worked with in the past, it integrates seamlessly with the larger Lightning Design System, allowing me to quickly and easily apply standard design patterns to my components.

Cleaning up is a breeze

With the launch of the new LWC framework, replacing old AngularJS with new OmniScripts is a piece of cake. The migration is very smooth because cleanup is so easy.

Points that were well liked

  • It integrates very well with the Salesforce LWC framework.
  • You can integrate LWC FLexCards into LWC OmniScript.
  • OmniStudio is an app in the app launcher. A central place for all OmniStudio administrators to manage OmniStudio components.
  • The new messaging framework is pleasant to work with.
  • It's great to be able to easily integrate a custom-made LWC.

Points that did not like

  • Lack of multilingual support in the beginning (later they fixed this).
  • Data Table support is disappointing compared to FlexCards. Now you have to create a FlexCard with a data table and then integrate the FlexCard into OmniScript.
  • Displaying the CPQ cart was difficult in AngularJS. Creating a custom LWC component with IFrame that included the CPQ cart solved this.
  • Reloading the shopping cart from OmniScript was difficult. We made it possible via pub/sub messaging. We found pub/sub messaging very useful in building communication between elements.
  • The edit block component previously had no support for clearing the table. A recent release resolved this with the "Allow Clear" parameter.


Despite some initial challenges, the migration to Salesforce generally went smoothly. Before getting started, I recommend consulting Salesforce's Help articles here and here, which provide valuable guidance and tips on various aspects of the transition.

The Apex Hours website is an excellent resource for learning more about OmniStudio, including how to get started with this platform. In addition, if OmniStudio or OmniScript is new to you, their introductory article on What is an OmniScript is a good starting point for understanding these tools.

Interested in what we can do for you?

Contact our experts directly. We'd love to hear from you!

Or would you like to learn more about Salesforce Industries CPQ? Find out what Salesforce Industries can do for your business. Download our presentation today.

Theodore van Donge

Tech Lead

Theodoor van Donge works at CaseNine as a Tech lead. In this capacity he is responsible for several projects at customers. Theodoor is not only involved in the actual development and implementation, but also advises customers in the areas of process and strategy. In doing so, he uses his substantive expertise and practical knowledge.

Receive notification when a new blog arrives

We would love to keep you updated on the latest news.