An object-based Interaction Launcher uses what to query data?

An object-based Interaction Launcher uses what to query data?

• A. Apex class
• B. A data record
• C. Fields specified in the setup to query
• D. A REST service

Answer: (C)

The key idea is that an object-based Interaction Launcher determines what to fetch by the fields you configure in its setup. You specify exactly which fields from the target object should be queried, and those fields define the data that will be retrieved and made available to the interaction. This focused field-based query keeps the data retrieval targeted and aligns what’s pulled with what you’ll use in the interaction. This isn’t driven by custom server code like an Apex class, nor is it about pulling a single data record by itself. It isn’t about calling an external REST service either; the launcher uses the configured fields to query the Salesforce object directly within the OmniStudio flow. If you need specific data such as Account name or Case status, you list those fields in the setup so they’re retrieved when the launcher runs.

The key idea is that an object-based Interaction Launcher determines what to fetch by the fields you configure in its setup. You specify exactly which fields from the target object should be queried, and those fields define the data that will be retrieved and made available to the interaction. This focused field-based query keeps the data retrieval targeted and aligns what’s pulled with what you’ll use in the interaction.

This isn’t driven by custom server code like an Apex class, nor is it about pulling a single data record by itself. It isn’t about calling an external REST service either; the launcher uses the configured fields to query the Salesforce object directly within the OmniStudio flow. If you need specific data such as Account name or Case status, you list those fields in the setup so they’re retrieved when the launcher runs.