An agent at a MedTech company requires a UI component that displays customer data and...

This order-entry experience uses a FlexCard to display customer information and expose the create-order action, an OmniScript to guide the user through the order-building steps, and a DataRaptor/Data Mapper to retrieve available products and persist Salesforce data. Document Generation is unrelated to the interactive transaction. OmniStudio separates presentation, guided interaction, Salesforce data access, and server-side orchestration through FlexCards, OmniScripts, DataRaptors/Data Mappers, and Integration Procedures. DataRaptors, now also represented as Data Mappers in current OmniStudio terminology, declaratively extract, transform, and load Salesforce data for OmniStudio components. From an implementation perspective, the configuration should use delivered Health Cloud and Salesforce mechanisms first, preserving standard relationships, security enforcement, and upgrade compatibility while limiting custom code to cases where declarative capabilities are insufficient. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach.

Study Guide references/topics:Implement - OmniStudio; DataRaptor

===============