How should the Remote Action element pass data to an Apex method that requires AccountId and ProductId?

How should the Remote Action element pass data to an Apex method that requires AccountId and ProductId?

• A. Check the DataRaptor Transform checkbox, and add the following Key/Value pairs to Output JSON Path:AccountId: %AccountId -ProductId: %Details:ProductId%
• B. Add the following to Send JSON Path: AccountId: %AccountId, ProductId: %Details:ProductId%
• C. Check the Send Only Additional Input checkbox, and add the following Key/Value pairs to Additional Input:AccountId: %AccountId%ProductId: %Details:ProductId%
• D. Set Return Only Additional Output to true, and add the following Key/Value pairs to Additional Input:AccountId: %Acc

Answer: (C)

The thing being tested is how inputs are transmitted from a Remote Action to an Apex method. For a method that needs AccountId and ProductId, you should supply those values as Additional Input and tell the Remote Action to send only that input. By checking Send Only Additional Input and listing AccountId: %AccountId% and ProductId: %Details:ProductId% in Additional Input, you provide exactly the parameters the Apex method expects, using data from your OmniScript or flow. This keeps the payload focused on the required inputs and uses the correct data references for each parameter. The other options mix in different features (like transforming data for output, or placing values in the main input, or configuring response behavior) that aren’t about providing the required input payload to the Apex method, so they won’t satisfy the method’s parameter requirements.

The thing being tested is how inputs are transmitted from a Remote Action to an Apex method. For a method that needs AccountId and ProductId, you should supply those values as Additional Input and tell the Remote Action to send only that input. By checking Send Only Additional Input and listing AccountId: %AccountId% and ProductId: %Details:ProductId% in Additional Input, you provide exactly the parameters the Apex method expects, using data from your OmniScript or flow. This keeps the payload focused on the required inputs and uses the correct data references for each parameter.

The other options mix in different features (like transforming data for output, or placing values in the main input, or configuring response behavior) that aren’t about providing the required input payload to the Apex method, so they won’t satisfy the method’s parameter requirements.