Is it possible to bypass strict schema validation in Genesys Cloud Data Actions when pushing nested conversation metadata to ServiceNow? The current flow triggers a 400 Bad Request due to a mismatched field type in the incident table. The payload structure aligns with the ServiceNow REST API documentation, yet the Data Action rejects the nested object. How can we handle complex JSON transformations within the flow without resorting to external middleware?