|
Conditional View
|
LWC supports Hide element if false.
|
Angular supports all Conditional View options.
|
|
Currency Element
|
Optionally display a Currency code in addition to the Currency
symbol.
|
Displays the Currency symbol
|
|
Data Preview
|
In addition to the ContextId functionality, test data in the Omniscript's
Data panel by adding Key/Value pairs.
|
Angular cannot test additional data.
|
|
HTTP Action for Integration Procedures
|
To use an HTTP Action that calls Apex, you must add the Salesforce org's
domain into a Remote Site's Remote Site URL field.
|
HTTP Actions calling Apex do not require a Remote Site.
|
|
Input Fields
|
LWC supports placeholder text in Input fields.
|
Angular does not support placeholder text in Input fields.
|
|
Launching an Activated Script
|
The How to Launch Activated Script modal now
displays an LWC tab that provides code to embed or launch a URL
addressable LWC Omniscript.
|
Clicking the How to Launch an Activated Script
opens a modal that contains information on embedding an Omniscript and
launching an Omniscript from a URL.
|
|
Lightning
|
LWC Omniscripts use pure SLDS.
|
Angular Omniscripts do not use pure SLDS.
|
|
Previewing an Omniscript
|
Omniscripts using custom Lightning web components must be active before
previewing.
|
Angular Omniscripts support previewing Inactive and Active Omniscripts
with custom templates.
|
|
Single-step rendering
|
-
LWC Omniscripts load and render Steps individually, resulting in
faster initial load times
-
Actions receive smaller data sets because the data JSON only
contains prefilled data and data from Steps that have rendered
-
Data, including data from previous Steps, is accessible to a Step
containing conditionals, formulas, and merge fields once the Step
renders
-
Previously loaded Steps containing conditionals, formulas, and
merge fields can evaluate data JSON when it becomes available
-
A future Step containing conditionals, formulas, and merge fields
will not have access to the data JSON until the Step renders
-
Prefill data present in the data JSON loads into a Step once the
Step renders
|
-
Loads all of the Omniscript's Steps when the Omniscript first
loads
-
The Omniscript's data JSON is present for every Step after the
initial load
-
Actions receive the entire set of data JSON that is present
-
Merge fields in future Steps can access the data JSON
-
Formulas in future Steps can access the data JSON
|
|
Step Chart Navigation
|
-
Navigating to a future step is not possible, even if there are no
Actions between the Steps
-
Navigate back to any previously loaded Step by clicking the Step in
the Step Chart.
|
|
|
Step Instruction Field
|
Merge fields are usable in the Step Instruction field.
|
Merge fields are not usable in the Step Instruction field.
|
|
Type
|
An LWC Omniscript's Type must begin with a
lowercase letter. You cannot use case-sensitivity to define a Type's
unique name if another Omniscript with the same Type exists. For example,
if you have an Angular Omniscript with an existing Type named
Test, you cannot create an LWC Omniscript with
a Type named test.
|
The Omniscript's Type must be a unique name that is not case-sensitive.
For example, if a Type named Test exists, you
cannot enter test as a Type.
|
|
UI Validation
|
-
Validation runs when a User clicks out of a field
-
Validation runs when a User submits a Step
-
When a User submits a Step, error messages appear inline with the
Element
-
Validation runs for typed values and values set by an API
-
Validation methods are accessible in custom Lightning web
components.
|
|
|
URL Element
|
Accepts a broader range of URL patterns, including:
-
http://www.xyz.com
-
https://www.xyz.com
-
www.xyz.com
-
test.xyz.com
|
Accepts a pattern of http://www.xyz.com
|
