What is the second key capability of VIPs?

What is the second key capability of VIPs?

• A. They can be called only from OmniScript.
• B. They can be a data source for multiple technologies and be called from OmniScript, Card Layout or Card, API, and Apex code.
• C. They can only be used within a single Card.
• D. They cannot be called from Apex code.

Answer: (B)

VIPs are designed to be reusable data sources that can be consumed by multiple parts of the OmniStudio stack. The second key capability is their cross-technology accessibility: a VIP can be used as a data source by OmniScript to drive a flow, by Card Layout or a FlexCard to display data, exposed via API, and called from Apex code for custom processing. This makes VIPs a central source of truth for integration data, enabling consistent data retrieval and reuse across different tools. Statements that limit VIPs to OmniScript, to a single Card, or that forbid Apex access don’t fit this design.

VIPs are designed to be reusable data sources that can be consumed by multiple parts of the OmniStudio stack. The second key capability is their cross-technology accessibility: a VIP can be used as a data source by OmniScript to drive a flow, by Card Layout or a FlexCard to display data, exposed via API, and called from Apex code for custom processing. This makes VIPs a central source of truth for integration data, enabling consistent data retrieval and reuse across different tools. Statements that limit VIPs to OmniScript, to a single Card, or that forbid Apex access don’t fit this design.