In my last article concerning Vlocity, I wrote about the CPQ and the JSONAttribute. Now it’s time to discover the tools that Vlocity provides in order to optimize the User Experience; one of them is the Omniscript.

What is an Omniscript?

In few words, it’s a powerful tool to build guided procedures. It is both Salesforce Classic and Lightning compatible and it should properly work on Salesforce1 as well.

It provides a lot of interactive functionalities and you can create a very basic Omniscript by using drag and drop capabilities. Html, Remoting and Angular skills are required to build advanced Omniscripts, but we will see it in later posts.

To create your first Omniscript, composed by two basic steps, you just need to follow the next bullets:

  • Register the Type and the SubType
  • Open the Vlocity Omniscript Designer
  • Compose the Omniscript
  • Check the preview

Register the Type and the SubType

First of all, you need to register the Type and the Subtype. Very easy, just need to open the Vlocity Omniscript object (Setup -> Objects -> Vlocity Omniscript) and add your values into the Type and Sub Type Picklists (i.e. Test, Test).

Open the Vlocity Omniscript Designer

Let’s create the Omniscript.

  • Open the Vlocity Omniscript Designer


  • Click on New Button


  • Insert the Name, the Type, and the subtype and click on the Save button

Compose the Omniscript

The Omniscript is very versatile to your needs, you can basically create every kind of guided procedures by just using drag & drop. In this first tutorial, we are going to create an input form step and a final resume step.

  • Create two Steps by dragging & dropping the Step element into the Structure Panel


  • Drag & Drop Input Text into the Step 1 and the Text Block into the Step 2


  • Open the Display Block and insert the %Text Input% string into the Text Editor. It is the way to recall the value of another block (like a variable)


That’s all. We have just created a very basic Omniscript that we can test just clicking on the Preview Tab.

Check the Preview

The Preview mode is a very useful tool to check the result of your composition.

By inserting a value in the first step, you will see the same value in the second one. The Next button will move you from a step to another.



Easy right? Don’t miss the next advanced tutorial by following us on Facebook and Twitter

Support us with a small donation:

  • LTC Address: La5f6W1rPr5VHFGCrCmPJ3sSa2AiwKZJbU
  • BTC Address: 1FG1j42MUze8jiW7JbgNaUMZxZeu7M1b4f
  • Ripple Address: rPVMhWBsfF9iMXYj3aAzJVkPDTFNSyWdKy     Tag: 562614972
  • ETH Address: 0x0940958167ca9cbd6409999957a011be7907d904
(Visited 5,135 times, 3 visits today)
Francesco Boccassi
Francesco Boccassi

Francesco is what the business chemistry calls a blend between a Pioneer, always looking for the next generation idea, and a Driver, methodical and clear goal minded. With more than 6 years in consulting he has a deep knowledge of CRM and Salesforce. He is now focusing on Blockchain and DApps.


  1. This article assumes a lot of foundation, so I have a newbie question for clarification.

    “Simple to register type and sub-type”; may be true logistically, but what are the meanings for type and sub-type so I can decide an appropriate name to assign and if I need a new one or use an existing one from another developer?

    Are there standard type/subtypes?


  2. Hi Bob,

    you can choose the type and subtype you prefer. They are useful to cluster the omniscripts. I usually set the Type as the SFDC Object and the Subtype as the specific process related to that Object.

    Kind regards

Leave a Comment