An OmniScript-based Interaction Launcher uses what to launch an interaction flow?

An OmniScript-based Interaction Launcher uses what to launch an interaction flow?

• A. A Simple Button
• B. A REST API call
• C. An OmniScript to launch an interaction flow
• D. A Screen Flow

Answer: (C)

The launcher is built to start an interaction flow from within an OmniScript, so the method used is an OmniScript-driven trigger. Because the launcher itself is an OmniScript, it invokes the interaction flow using OmniScript’s own mechanisms (often via a launch action) and can pass parameters as needed. This provides a cohesive, reusable way to initiate the interaction inside OmniStudio. A simple button wouldn’t carry the OmniScript lifecycle, a REST API call would bypass the OmniScript framework, and a Screen Flow is a different Salesforce automation type that isn’t how this launcher activates the interaction flow.

The launcher is built to start an interaction flow from within an OmniScript, so the method used is an OmniScript-driven trigger. Because the launcher itself is an OmniScript, it invokes the interaction flow using OmniScript’s own mechanisms (often via a launch action) and can pass parameters as needed. This provides a cohesive, reusable way to initiate the interaction inside OmniStudio. A simple button wouldn’t carry the OmniScript lifecycle, a REST API call would bypass the OmniScript framework, and a Screen Flow is a different Salesforce automation type that isn’t how this launcher activates the interaction flow.