Explanation:

An Integration Procedure is the correct tool because creating a Chatter post is an action that requires interacting with the Salesforce platform API.

Here's a breakdown:

API Interaction: Posting to a Chatter feed is not a simple data retrieval or transformation; it's an action performed by calling the Salesforce Chatter REST API.

Role of Integration Procedure: An Integration Procedure is designed to execute a series of actions, including Remote Actions. A Remote Action within an IP allows you to call a custom Apex class.

The Complete Flow: To create a Chatter post, you would build an Integration Procedure that includes a Remote Action step. This Remote Action would call an Apex class you've written that uses the ConnectApi.ChatterFeeds class to post the message to the desired feed.

In essence, the Integration Procedure serves as the orchestrator that can execute the specific, coded action required to post to Chatter.

Why the Other Options are Incorrect:

A. DataRaptor Load: A DataRaptor is designed for declarative data extraction (Load), transformation (Transform), and saving (Post). It cannot perform API calls or execute the specific Apex logic needed for a Chatter post. Its scope is limited to manipulating SObject data.

C. Calculation Procedure: This tool is specifically for performing multi-step calculations, often using Calculation Matrices and DataRaptors. It is not designed to execute side-effect actions like posting to an external feed or API.

D. FlexCards: A FlexCard is a front-end UI component used to display data and trigger actions. While a FlexCard could initiate the process (e.g., a user clicks a button to post), the actual work of creating the Chatter post must be handled by a backend tool like an Integration Procedure. The FlexCard itself cannot perform the action.

Reference:

This is based on the fundamental capabilities of each OmniStudio tool. The official Salesforce OmniStudio Developer Guide outlines that Integration Procedures are the primary tool for orchestrating multi-step processes that can include:

DataRaptor Turbo steps (for high-performance data).

Remote Action steps (to call custom Apex code).

Calculation Procedure steps.

Since posting to Chatter requires custom Apex, the Integration Procedure is the only tool that can orchestrate this action in a declarative workflow.

Explanation:

To meet the requirements of a multi-step, conditional guided process that interacts with both Salesforce and external systems, the consultant should use OmniScripts and Integration Procedures.

➡️ OmniScripts are the ideal tool for creating guided processes with conditional logic. They are designed to walk a user through a series of steps (pages), collecting information and performing actions along the way. The branching logic described in the scenario is a core capability of OmniScripts, allowing the flow of the process to change dynamically based on user input.

➡️ Integration Procedures are declarative, server-side processes that can retrieve and manipulate data from various sources in a single server call. They are essential for this solution because they can retrieve data from external systems (e.g., via REST APIs) and from Salesforce in a highly efficient manner. An OmniScript can then call an Integration Procedure to get all the necessary data before presenting it to the user. This approach is a best practice for performance and for handling complex data interactions.

Why the Other Options Are Incorrect?

❌ A. FlexCards and Integration Procedures:
FlexCards are used to display data and launch actions, but they are not designed for multi-step, guided processes with conditional branching. They are single-screen components. While they use Integration Procedures for data, they don't provide the necessary multi-step workflow.

❌ B. FlexCards and DataRaptors:
This combination is used for displaying data from Salesforce, not for a guided, multi-step process. DataRaptors are server-side tools for reading and writing data within Salesforce and are not used for retrieving data from external systems.

❌ D. OmniScripts and DataRaptors:
This combination can be used for guided processes that interact with Salesforce data. However, DataRaptors cannot directly retrieve data from external systems like Integration Procedures can. Therefore, this option fails to meet the full requirements of the problem.

Explanation

FlexCards are the ideal OmniStudio tool for displaying data and launching actions from a Salesforce org. They are designed to present concise, contextual data in a card-based format and can include actionable elements like buttons or links to trigger actions (e.g., launching an OmniScript, updating records, or calling an Integration Procedure). FlexCards fetch data using DataRaptors or Integration Procedures and can be embedded in Salesforce pages or external websites to provide an interactive user experience.

Reference: Salesforce Trailhead module "Get Started with OmniStudio FlexCards" describes FlexCards as tools to "display contextual information and provide quick access to actions" from Salesforce data.

Why Not the Other Options?

A. DataRaptors: DataRaptors are used to extract, transform, or load data between Salesforce and OmniStudio components but do not directly display data or launch actions for users.

C. OmniScripts: OmniScripts create guided, interactive processes for user input and workflows, not for simply displaying data and launching actions.

D. Integration Procedures: These handle server-side data operations (e.g., aggregating data from multiple sources) but are not designed for front-end data display or user-initiated actions.

Reference: Salesforce OmniStudio documentation on Trailhead, specifically the FlexCards module, emphasizes their role in data display and action triggers.

Explanation

D. Radio (or Select/Radio Group):

This element is best suited for the first step where the user needs to select one option from a defined set: Credit Card, Debit Card, or Direct Bank Account Payment.

A Radio Group allows only one selection and can easily incorporate the requirement for a different icon to display with each payment type, making the user interface clear and visual.

C. DataRaptor Extract Action:

This element is required to implement the logic for checking for saved payment information.

An Extract Action is used to retrieve (read) data from Salesforce or other external sources. The OmniScript would execute this action based on the selected payment type to see if a matching saved record exists for the customer.

E. DataRaptor Post Action:

This element is required to implement the logic for saving the new payment information if no saved information is found.

A Post Action is used to create, update, or delete (write) data to Salesforce. If the Extract Action returns no saved data, the OmniScript would display input fields, and upon submission, the Post Action would handle the saving of the new payment details.

Why the others are incorrect:

A. DataRaptor Transform Action: While a Transform Action is used to reshape data (e.g., flatten, group, or change node names), it is not strictly required for the core functions of checking and saving data, which are handled by the Extract and Post actions.

B. Select: While a Select element (a dropdown) could capture the payment type, a Radio or Radio Group is generally better for showing options with icons on a first step and is more direct for a small number of choices. Both could technically work for the selection, but the combination of Extract and Post for the data manipulation makes C, D, and E the most comprehensive answer set. Given that Radio and Select serve the same input purpose, and the problem requires three distinct functional elements, the necessary data actions (Extract and Post) along with the primary input (Radio/Select) are the key components. Radio is often preferred for visibility in this scenario.

In summary, you need a:

Radio to get the user's input.

DataRaptor Extract to check the existing data.

DataRaptor Post to save the new data.

Explanation

DataRaptors are a declarative tool within OmniStudio used to manage and manipulate data on the Salesforce platform. They are a powerful, no-code/low-code substitute for Apex when dealing with data.

Read and Write Data to Salesforce (Extract and Load):

DataRaptor Extract (and Turbo Extract) is used to read (extract) data from one or more Salesforce objects.
DataRaptor Load is used to write (load/save) data back into one or more Salesforce objects (i.e., perform Create, Update, or Delete operations).

Reference: Salesforce OmniStudio DataRaptor Documentation (Trailhead/Help Docs) describes Extract and Load as its primary methods for interacting with Salesforce data.

Transform Data (Transform):

DataRaptor Transform is used to perform intermediate data transformations on data, such as restructuring JSON/XML, renaming fields, converting data formats, or applying complex formulas.
This is often done with data that has been extracted or before it is loaded, or even with data that never touches the Salesforce database.

Reference: The Transform DataRaptor type is specifically designed for this data manipulation function.

Why the other options are incorrect:

B. Combine requests into a single response: This function is typically performed by an Integration Procedure, which can call multiple DataRaptors, HTTP calls, or other actions and orchestrate them into a single, unified service response.

C. Read and write data to external systems: While DataRaptors can manipulate data received from or prepared for external systems, the actual connection and execution of external API calls (HTTP/REST/SOAP) is handled by a separate OmniStudio component, the Integration Procedure.