Some Gotchas When Installing Vlocity Industries in your Salesforce Org

So our client has a fresh vanilla Salesforce org that I am setting up by installing Vlocity Industries – Energy and Utilities Cloud and learned a few gotchas that I wanted to share.

First off, know if your org uses OmniStudio sObjects(standard) or OmniStudio for Vlocity SObjects(custom objects). You can do the following:

Under Setup > Quick Find and search if Omni Interaction Configuration appears in the results. If it does, this means your org uses OmniStudio sObjects.

Omni Interaction Configuration

Other gotchas to know:

Managing Licenses

  1. There is now a different method of assigning permissions to users with the E&U, you no longer have to manage the licenses from the installed package.
    1. To allocate the license go to the Company Information in Setup and assign users to the following Permission Sets
      1. OmniStudio Admin
      2. Energy & Utilities Base Sales
      3. Energy & Utilities Base Service
    2. Aside from the Permission Sets listed on the Company Information page, you need to go to the Permission Sets from Setup and add the following users to the following permission sets as well.
      1. OmniStudio Admin
      2. EAndU Cloud Base Runtime
      3. EAndU Cloud Sales Runtime

No Access to Vlocity Card Tab

Next, going to the installation step when you get to install step — Import CPQ Base Templates and Omniscripts, it says to open the Vlocity Card tab, but instead, what you get is an error This Page is deprecated (likely this only happens if you are on an OmniStudio sObject org).

Vlocity Card

Do the following to fix the error:

  • Go to Setup > Omni Interaction Configuration
  • Click the New button and enter the following
  • Name: ShowLegacyOmniStudioUi
  • Value: true
  • And Save
Omni Interacton Configuration

Note: Opening any OmniScript installed will open in the Angular UI.

Editing OTB Cards, Templates and OmniScripts

If you customize any out-of-the-box cards, templates, and OmniScripts, give them new, unique names. Renaming them prevents them from being overwritten when you upgrade to the latest release.

Installing Console Apps

At this moment, it seems if you want to install any of the console apps(Energy & Utilities Contact Center Console, Large Account Sales Management app) you would need to request a demo org. There does not seem to be a method to directly install it in an existing org. To transfer the components you would need to retrieve the components from the demo org and manually migrate them to your target org, you have couple few options to accomplish this.

  • Using IDX workbench
  • VSCode with Salesforce Vlocity Integration extension from the Marketplace.
  • Using the Vlocity cli.

Integration Procedure and DataRaptors Actions

If you managed to deploy the console apps to your target org, you would notice that data is not flowing from the Integration Procedures that calls Dataraptors even when checking to the Debugger.

The solution I figured out was to:

  • Create a new version of the Integration Procedure,
  • Add any Dataraptor action
  • Then delete that Dataraptor action
  • Activate the new version

Only then will the data be returned from the existing Dataraptor Action to that Integration Procedure.

FlexCard Opening as Record instead of the FlexCard Designer

If the FlexCard is opening a record instead of the FlexCard Designer, perform the following:

If using OmniStudio sObjects

  • Go to Setup > Object Manager > Omni UI Card > Lightning Record Pages > Vlocity Card Designer > View > Activate the layout as the Org default
  • If you can’t find the Lightning Record Pages, you would need to recreate it.
    • Edit the existing Omni UI Page and remove all components and add the following components
      • cardDesignerHeader
      • cardPreview
      • rightSidebar

If using OmniStudio for Vlocity

  • Go to Setup > Object Manager > Vlocity Card > Lightning Record Pages > Vlocity Card Designer > View > Activate the layout as the Org default

Deploying DataPacks

As I mentioned earlier it is important to know if you are using OmniStudio standard objects or Vlocity for Omnistudio(custom objects).

If you are on Omnistudio standard objects then retrieving or deploying DataPacks using VSCode with the Vlocode extension this doesn’t work. You have two options

Note: I was informed that you would need to use vlocity build tool with FlexCards, they do not work with the IDX alpha tool as of writing.

Installing Vlocity Industries Summary

Just installing the package is one part, the amount of manual steps is a lot of work. I wish it can be automated in the future like tweaking page layouts, flexipage, and such, etc. I’ll keep this post updated as I learn a few more gotchas as I do the implementation.

I am currently working on an OmniStudio Udemy and Skillshare course where I will cover more about development and building on the framework. Will be an in-depth good resource for preparing for the OmniStudio Developer Certification.

If you are interested to know and want to be notified when it comes out. Show your interest by leaving a comment below.

2 thoughts on “Some Gotchas When Installing Vlocity Industries in your Salesforce Org

Leave a Reply

Your email address will not be published. Required fields are marked *