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

The correct syntax for the Send JSON Path is ActionName: BlockName, where ActionName is the name of the action element and BlockName is the name of the block element that contains the output data. The other options are either missing the colon or using incorrect names.

The correct syntax for passing all of the parent FlexCard's records to a child FlexCard is {Records}, which represents an array of records. The other options are incorrect because they either use an invalid syntax or refer to a single record instead of an array of records.

According to the Salesforce OmniStudio DataRaptor documentation, specifically under DataRaptor Load Best Practices and Common Issues:
* A. "The Input JSON paths in the Data Mapper Load do not match the JSON sent from the OmniScript." This is a common configuration issue. If the paths between the OmniScript's structure and the DataRaptor Load mapping are mismatched, fields may not map correctly, resulting in partial updates or no updates.
* B. "The fields that are not updated are read-only in Salesforce."If a field is Read-Only at the field- level security (FLS) or object schema, DataRaptor Load will not be able to write to it, which explains why only some data is updated.
Incorrect Options:
* C. The RecordId from the wrong record type would typically cause a complete failure, not a partial update.
* D. A misspelled ContextId could prevent data from being linked correctly, but this is less likely to cause partial field-level issues, and more likely to affect record association.
:
Salesforce OmniStudio Developer Guide # DataRaptor Load # Troubleshooting Salesforce Help Documentation: OmniStudio DataRaptor Best Practices

Using two separate Calculation Steps with the Conditional Step property selected allows the developer to specify different formulas based on different conditions. The ISTRUE(isCustomer) and NOT(ISTRUE(isCustomer)) functions are used to evaluate the Boolean variable in the Condition syntax. The other options are either missing the Conditional Step property, using incorrect comparison operators, or using an IF statement instead of separate Calculation Steps.