An Integration Procedure is designed to be called by a Sub-Integration Procedure Action.

The child Integration Procedure must return the full generated payload, so the Response Action must point to the full/root response instead of a narrowed child node or single response parameter. Setting the Response JSON Path to the root node is the explicit configuration in the given answer set. A Data Mapper Transform can reshape data, but it does not define the final return payload of the Integration Procedure. A single Response Parameter named Output with %AllData% is not the standard configuration. Leaving parameters blank can be acceptable in some caller configurations when the default behavior returns all data, but the question asks what to configure on the child Response Action, and the explicit root Response JSON Path is the strongest answer.

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