Salesforce Exam Health Cloud Accredited Professional Topic 2 Question 63 Discussion

To address the use case of creating a UI component for a MedTech company that displays customer data, allows initiating a new order process, and displays available products for purchase, the following OmniStudio capabilities are required:

1. Integration Procedures:

Purpose: Integration Procedures handle server-side logic by connecting with external systems, databases, or Salesforce objects to fetch or update data efficiently.

Role in Use Case: The new order process will likely require data from external systems, such as a product catalog or inventory system. Integration Procedures are ideal for orchestrating these back-end calls and consolidating data to display product availability or order information.

Key Features:

Perform complex, multi-step actions in a single server call.

Fetch data asynchronously, improving UI performance.

2. FlexCards:

Purpose: FlexCards are lightweight, reusable UI components that display contextual information on a single screen. They can include links, buttons, and embedded actions.

Role in Use Case: The UI component displaying customer data and providing the link to create a new order is best implemented as a FlexCard.

Key Features:

Can display data fetched via DataRaptors or Integration Procedures.

Easily customizable to match the desired layout and functionality.

3. OmniScript:

Purpose: OmniScripts guide users through multi-step processes with dynamic forms and workflows, integrating seamlessly with FlexCards and Integration Procedures.

Role in Use Case: When the link on the FlexCard is clicked, the OmniScript starts the process to build a new order and display available products. This ensures an intuitive and structured user experience for completing complex processes.

Key Features:

Drag-and-drop UI for creating guided workflows.

Can call Integration Procedures to fetch product details or submit the order.

Capabilities Not Required for This Use Case:

D . DataRaptors: While DataRaptors are crucial for basic data fetch/update operations, the described use case involves orchestrating multiple steps and external system integrations, making Integration Procedures more suitable.

E . Document Generation: This feature is used for generating PDFs or documents, which is not relevant to the process of building a UI component for order creation.

Summary of Implementation:

FlexCards display customer data and include a clickable link to start the new order process.

OmniScript handles the guided workflow to create the order and fetch available products.

Integration Procedures facilitate the server-side logic for fetching products and submitting the order.

OmniStudio Documentation

OmniScript Best Practices

FlexCards for Contextual UI