Question 11
Choose 3
A company wants to create a new digital interaction process that allows customers to request a quote for service from a local retail energy supplier. The process requires the following actions:
• Allow the user to select one or more energy products from a list
• Get current energy usage data from an external system via an API
• Save the data back to Salesforce as a lead
Which three OmniScript elements should the consultant recommend to meet these requirements? (Choose 3 answers)
• Allow the user to select one or more energy products from a list
• Get current energy usage data from an external system via an API
• Save the data back to Salesforce as a lead
Which three OmniScript elements should the consultant recommend to meet these requirements? (Choose 3 answers)
Correct answer:
B. Multi-select Input
C. Post to Object Action
D. HTTP Action
Explanation:
Let's map each requirement to the OmniStudio element designed to fulfill it.
B. Multi-select Input: This is correct. The requirement is to "Allow the user to select one or more energy products from a list." The Multi-select input element is specifically designed for this purpose. It presents the user with a list of options (which can be statically defined or loaded from a DataRaptor) and allows them to select multiple values.
D. HTTP Action: This is correct. The requirement is to "Get current energy usage data from an external system via an API." The HTTP Action element is the primary tool in OmniStudio for making outbound callouts to external REST APIs. It can be configured with the necessary endpoint, headers, and parameters to retrieve the energy usage data and store it in the OmniScript's JSON data model for later use.
C. Post to Object Action: This is correct. The requirement is to "Save the data back to Salesforce as a lead." The Post to Object Action (also known as an "Action" element of type "SFDC Action") is the standard element for performing DML operations (Create, Update, Delete) on Salesforce records. It can take the data collected in the OmniScript (like the user's contact info, selected products, and the fetched energy usage) and use it to create a new Lead record.
Why the Other Option is Incorrect:
A. DataRaptor Post Action: This is incorrect. A DataRaptor Post Action is used specifically to execute a DataRaptor Turbo of type "Export" (a Post-DR). While a Post-DR can also be used to save data to Salesforce, its primary strength is complex data transformation and saving data to multiple related objects in a single transaction. For the straightforward requirement of saving data to a single Lead object, the simpler and more direct Post to Object Action is the recommended and more efficient choice. Using a DataRaptor here would be over-engineering the solution.
Reference:
OmniStudio Elements: Multi-select (Input Element), HTTP Action (Integration Element), Post to Object Action / SFDC Action (Action Element).
Key Concept: The correct element is chosen based on the specific task:
➡️ User input from a list: Multi-select
➡️ Call an external API: HTTP Action
➡️ Create a Salesforce record: Post to Object Action (for simplicity) or a DataRaptor Post Action (for complex transformations).
Let's map each requirement to the OmniStudio element designed to fulfill it.
B. Multi-select Input: This is correct. The requirement is to "Allow the user to select one or more energy products from a list." The Multi-select input element is specifically designed for this purpose. It presents the user with a list of options (which can be statically defined or loaded from a DataRaptor) and allows them to select multiple values.
D. HTTP Action: This is correct. The requirement is to "Get current energy usage data from an external system via an API." The HTTP Action element is the primary tool in OmniStudio for making outbound callouts to external REST APIs. It can be configured with the necessary endpoint, headers, and parameters to retrieve the energy usage data and store it in the OmniScript's JSON data model for later use.
C. Post to Object Action: This is correct. The requirement is to "Save the data back to Salesforce as a lead." The Post to Object Action (also known as an "Action" element of type "SFDC Action") is the standard element for performing DML operations (Create, Update, Delete) on Salesforce records. It can take the data collected in the OmniScript (like the user's contact info, selected products, and the fetched energy usage) and use it to create a new Lead record.
Why the Other Option is Incorrect:
A. DataRaptor Post Action: This is incorrect. A DataRaptor Post Action is used specifically to execute a DataRaptor Turbo of type "Export" (a Post-DR). While a Post-DR can also be used to save data to Salesforce, its primary strength is complex data transformation and saving data to multiple related objects in a single transaction. For the straightforward requirement of saving data to a single Lead object, the simpler and more direct Post to Object Action is the recommended and more efficient choice. Using a DataRaptor here would be over-engineering the solution.
Reference:
OmniStudio Elements: Multi-select (Input Element), HTTP Action (Integration Element), Post to Object Action / SFDC Action (Action Element).
Key Concept: The correct element is chosen based on the specific task:
➡️ User input from a list: Multi-select
➡️ Call an external API: HTTP Action
➡️ Create a Salesforce record: Post to Object Action (for simplicity) or a DataRaptor Post Action (for complex transformations).
