Lesson OS 2 - OmniScript

Multiple Choice

True/False/Clarification: While designing my OmniScript I am able to review what I build in real-time with live data?

• True

• False

• Not yet, but it is on the roadmap for the next realese

​You can preview your script by entering a RecordId in the Context ID filed & refreshing the preview.

Also interesting: Data JSON -> updates when entering values in data fields on the canvas

(Source: trailhead OmniScripts - Dig into the OmniScript Designer)

Multiple Choice

Which OmniScript Action do I use to send Docusign emails for signature?

• DataRaptor Post Action

• Integration Procedure Action

• DocuSign Mail Action

• DocuSign Signature Action

• DocuSign Envelope Action

• ​DataRaptor Post Action: call a DataRaptor Load

• Integration Procedure Action: Call an Integration Procedure

• Docusign Mail Action: Does not exist

• Docusign Signature Action: Sign Document w/ Docusign; use: Docusign template + Dataraptor transform

• Docusign Envelope Action: Send DocuSign email for signature; use: Docusign template + Dataraptor transform

​Which OmniScript Action do I use to send Docusign emails for signature?

​(Source: OMS345 OmniStudio Student Take Home Guide v1.0 & trailhead OmniScripts - Design a Simple OmniScript)

​Scenario: FlexCard that gives the possibility to update an Account via OmniScript

Multiple Choice

You have set up everything necessary to be able to update Account from your OmniScript - however some of the fields in your OmniScript appear empty; what is the most logical reason?

• You need an XML to parse the data coming from the Integration Procedure JSON to the OmniScript

• JSON coming from Integration Procedure doesn't match element names of the OmniScript

• The Read Action for FlexCard is missing

OmniScript uses a parser to match the JSON that comes from the Integration Procedure to the inputs in the OmniScript based on element names. If the JSON doesn’t match the element name, the fields will appear empty. 

(Source: trailhead OmniScript - Create a Simple OmniScript)

Multiple Choice

True/False: The benefit of the Reusable field on OmniScript means that I am able to reuse other OmniScripts within my OmniScript, those OmniScripts are also able to reuse other scripts.

• True

• False

True/False: The benefit of the Reusable field on OmniScript I am able to reuse other OmniScripts within my OmniScript, those OmniScripts are also able to reuse other scripts.

​

FALSE

OmniScript Embedding:

You can have only one level of nesting. This means if you plan to reuse an OmniScript, it cannot have a reusable OmniScript as part of the structure.

(Source: Hands-on exercices - Create a Simple OmniScript)

Multiple Choice

Why would you add a field for the RecordId you want to update in a block in an OmniScript if it has no purpose for the end user?

• It helps improve the efficiency of the OmniScript

• It is mandatory to have the RecordId in the same block of the OmniScript you want to update; otherwise Salesforce doesn't know which record to update

• It is not needed; it helps in debugging

​The Text2 field displays the ContactId, which is the RecordId for the primary contact.
Keeping the RecordId in the same block of the OmniScript when you update that contact’s details and save the changes back to Salesforce makes your life as a developer much easier. However, the RecordId has no purpose for the end-user. Therefore, hide the RecordId from the UI.

(Source: Hands-on exercices - OmniStudio Design and Build a Branching OmniScript)

Multiple Choice

How can you hide the aforementioned RecordId from the UI?

• No way to do this via the UI, you have to edit the JSON: put "hide" property to true

• Not possible (yet) to hide this from the UI, but you can ensure that the user doesn't update via "Read Only" checkbox

• Use the "View as Admin" checkbox

There isn't a checkbox to hide the field.

JSON has to be edited: Properties panel > Edit Properties as JSON> "hide": true --> true/false booleans must be all lowercase

(Source: Hands-on exercices - OmniStudio Design and Build a Branching OmniScript)

Multiple Choice

Translation is available for "help tooltips"?

• Yes, this is always the case

• Yes, if "multilanguage" is enabled

• No, unfortunately since SF is an American company they often forget about translations. You would have to create an OmniScript per desired language.

​Translation is available for help tooltips if multilanguage is enabled

Multiple Choice

What is the name of this type of field?

• Edit Block

• Type Ahead Block

• Navigate Action Field

• Edit block: add, edit or delete records in real time

• Type Ahead block: auto-search & auto-complete dropdown; need a data source (DR extract, remote or HTTP Action); Google Maps API is build in

• ​Navigate Action: Enables OmniScript to open different SF experiences & external endpoints

  (Source: OMS435 OmniStudio Student Take Home Guide & Hands-on exercices - OmniStudio Create a Type Ahead Block Element)

Multiple Choice

You need to bring data from a single hierarchy involving Account, Contact, Case and another customer object into your workflow? Which tool should you use?

• Screenflow

• OmniScript

Q: You need to bring data from a single hierarchy involving Account, Contact, Case and another customer object into your workflow? Which tool should you use?

​

Working with a complex hierarchy of data --> OmniScript

(Source: Lesson: Comparing OmniScripts to Screen Flows)

Multiple Choice

Which tool to use when you need complex & dynamic inputs, with conditonal rendering and dynamic validations?

• Screen Flows

• OmniScripts

Q: Which tool to use when you need complex & dynamic inputs, with conditonal rendering and dynamic validations

Regular expresison validations &v alidate format of data --> OmniScripts