Common Action Element Properties

Review information about Omniscript action element properties.

Common Action Properties

Property

Description

Label

The label on the button, or, if running remotely, the heading of the Action block.

Validation

Determines whether validation runs on the step before the action is invoked. When set to Step, the action button will be clickable once all required fields within the step contain valid input. Select None to bypass validation.

Invoke Mode

Configure the response behavior of the action.

Default: The Action blocks the UI with a loading spinner.

Non-Blocking: The Action runs asynchronously, and the response is applied to the UI. Pre and Post Omnistudio Data Mapper transforms, and large attachments are not supported.

Fire and Forget: The Action runs asynchronously with no callback to the UI. Pre and Post Data Mapper transforms, and large attachments are not supported. A response will still appear in the debug console but will not be applied to the Data JSON.

Conditional View

All Action elements support conditional view. See Conditionally Display Omniscript Elements.

Pub/Sub

Communicate with Omniscript from a custom LWC by sending key-value pairs. Use the events passed in the key-value pairs to trigger custom behavior in a component. See Messaging Framework for Omniscripts.

Session Storage

Send information to a Session Storage object using key-value pairs. A session storage object clears when a page session ends. See Messaging Framework for Omniscripts.

Window Post Message

Send information from an element to a window object in key-value pairs. SeeMessaging Framework for Omniscripts.

User Message Properties

Actions that run remotely and between steps, or before the first Step is run, contain these User Message properties.

Property

Description

Show a message during execution

Enable Action Message in the designer for a managed package

Enables an input of custom action messages.

Next Label on Failure

Failure Next Label in the designer for a managed package

Label of the continue button if the Action fails.

Previous Label on Failure

Failure Go Back Label in the designer for a managed package

Label of the Go Back button if the Action fails. The default behavior enables users to return to the previous Step unless there are no previous steps.

Success Message

Post Message in the designer for a managed package

Message displayed upon success.

Send and Response Transformations

Send and Response Transformations are properties available on a variety of Omniscript remote actions. They provide flexibility in trimming and reparenting the request and response JSON. For more information on how to use Send and Response Transformations, see Manipulating JSON with the Send and Response Transformations Property.

Property

Description

Send JSON Path

This property enables one node of the Omniscript Data JSON to be sent, rather than the entire JSON. Specify the node name in this property.

Send JSON Node

This property allows you to specify the root node name in the outgoing response. For example, if your Omniscript had a Customer node at the root, you could relabel the node to CustomerAccount.

Pre-Transform Data Mapper

In situations where a more complete transformation of the JSON is required, you can specify a Data Mapper transform interface. The service will run on the server, and then return the request body to the client for sending.

Post-Transform Data Mapper

Works identically to the Pre-Transform, except the transformation is applied to the response body before merging into the Data JSON.

Response JSON Path

This property allows you to trim the incoming JSON. For example, if the response has a three-level hierarchy, and you only want one of the nodes, you can specific the path you like to extract. The syntax is node:node:node (colon-separated).

Response JSON Node

This property allows you to reparent the incoming JSON to a node within the Omniscript JSON. Specific the Omniscript element name which will be the new root node for the response JSON.

Selecting an Invoke Mode

Enable actions to run asynchronously, block users from advancing to a future Step, and modify by selecting an invoke mode.

Invoke Mode enables you to configure the response behavior of an action. It is available in:

  • Remote Action

  • Integration Procedure Action

Property

Description

Default

The Action blocks the UI with a loading spinner.

Non-Blocking

The Action runs asynchronously, and the response is applied to the UI. Pre and Post Data Mapper transforms, and large attachments are not supported.

Fire and Forget

The Action runs asynchronously with no callback to the UI. Pre and Post Data Mapper transforms, and large attachments are not supported. A response will still appear in the debug console but will not be applied to the Data JSON.

Extra Payload

Extra payload is an additional property available for the actions listed below. The Omniscript can set up extra payload to be sent while making the call. This property supports merge fields.It is available in:

  • Remote Action

  • Integration Procedure Action

  • HTTP Action

Add an Action Message

Display an action message beneath the loading spinner while the action is running.

  1. In an Action, expand the User Messages property.
  2. Check Enable Action Message.
  3. In Action Message, enter a custom message, or leave the default message.