Outbound REST message fails due to incorrect escaping in variable substitutionsIssue Variable substitution in outbound REST fails to escape quotes (" ") and incorrectly prints it as " """ causing the request the fail. CauseFor example, when we have 4 variable substitutions for an outbound REST message with values in quotes (" "). The escape type for all these 4 are set to "No Escape". When we click on 'Test', the content is wrong. Content when the test run failed: { "workflowArgs": { "applicationId" : "8a4890db539c40b901539c48a9da000e", "emplId" : "31690", "snTicketId" : "39ff79664fc726001b1ae3414210c70a", "accountArgs" : {"Role": ["8a4890db542b436301543b69570c4069"]} } }ResolutionIf the escaping is incorrect for the variable substitutions, you would need to apply the below solution: Change the escape type of the affected variable substitutions from "NO ESCAPE" to "ESCAPE XML". Content when the test run is successful: { "workflowArgs": { "applicationId" : "8a4890db539c40b901539c48a9da000e", "emplId" : "31690", "snTicketId" : "39ff79664fc726001b1ae3414210c70a", "accountArgs" : {"Role": ["8a4890db542b436301543b69570c4069"]} } }