OmniStudio does not natively support direct JSON-to-XML transformation using DataRaptors. When a transformation to specific XML formats is needed for integration with external web services, it is recommended to use Remote Actions that invoke custom Apex classes.
* A. Use a Remote Action that calls the XMLStreamWriter class - Correct. The XMLStreamWriter Apex class provides precise control over XML structure and is the Salesforce-recommended way to programmatically generate XML from data within a Remote Action step in an Integration Procedure.
Incorrect Options:
* B. The XML checkbox in DataRaptor does not convert JSON to XML; it defines output data format for display or API serialization.
* C. XMLStreamReader is used for parsing XML, not for generating it.
* D. DataRaptor Transforms only manipulate JSON structure; they do not support converting JSON into XML format.
Salesforce Developer Guide # Apex XMLStreamWriter Class
OmniStudio Integration Procedures # Using Remote Actions with Custom Apex

When an OmniScript receives incomplete data from an Integration Procedure, the issue is typically in Response JSON path mapping or naming mismatches.
* A. The missing data is trimmed in the Integration Procedure Action Response JSON Path - If the Response JSON Path only points to part of the structure, any nested or unrelated values are excluded from the output.
* B. The element name for the missing data does not match the JSON node key in the Integration Procedure Response - OmniScript expects a matching node name to bind the data to UI elements. If the key doesn't match, that field will appear blank.
Incorrect Options:
* C. Preview Input Parameters are only for testing in the Integration Procedure editor; they don't affect runtime execution.
* D. Even if the JSON from the Integration Procedure Action is different from the original IP input, it would cause a failure or unexpected data, not necessarily missing specific values.
Salesforce OmniStudio # Integration Procedures # JSON Path and Data Binding

The best practice is to create a separate child FlexCard for the related-contact display. A child FlexCard gives the team a reusable UI component that can be embedded in other FlexCards without copying layout elements, actions, fields, and styling each time. Duplicating the elements would create maintenance problems because later changes must be repeated everywhere. A global CSS class can standardize appearance, but it does not make the component logic reusable. A Data Mapper can retrieve or transform data, but it is not a display component. Salesforce documentation confirms that FlexCards can be embedded inside other FlexCards and can use either their own data source or the parent FlexCard's data, which supports modular reuse.

According to the OmniStudio Developer Guide, "DataRaptor Transform actions can convert JSON to XML and vice versa." Therefore, the correct answer is C.

According to the Integration Procedure Actions page, "To pass data from a Set Values action to a DataRaptor action, add the Set Values action name to the Additional Input field of the DataRaptor action."