Sending data via RESTMessageV2 cuts/breaks content if data include dollar and curly bracket together without space in REST content - Known Error

Sending data via RESTMessageV2 cuts/breaks content if data include dollar and curly bracket together without space in REST content Description Sending data via RESTMessageV2 cuts/breaks content if data include dollar and curly bracket together without space in REST content

Steps to Reproduce

1. Create REST message, give dummy end point. 2. Create post method and in content field addbelow value: {test:"one ${"} 3. Now test this method and see that result is expected and in content same value is available. 4. Go back to POST method aand remove space in between dollar and curly bracket 5. Test and see in result , desired value is not available instead content gets truncated after 'one', see below: {test:"one

Workaround This is working as expected, explanation:

------------------------------------------------

The cause of the behavior is the Variable Substitution feature in RESTMessageV2. When there is a substring of the format ${--insert-variable-here--} then RESTMessageV2 attempts to replace the variable with the provided variable value. Incase it isn't present, it replaces it by an empty string (called forced substitution -- enabled by default).

RESTMessageV2 also offers a method called disableForcedVariableSubstitution() to disable this behavior. Customer can call the method in their script while using RESTMessageV2.

For example: var sm = new sn_ws.RESTMessageV2(" ","get"); sm.disableForcedVariableSubstitution(); var response = sm.execute();

Reference: https://docs.servicenow.com/en-US/bundle/utah-api-reference/page/app-store/dev_portal/API_reference/RESTMessageV2/concept/c_RESTMessageV2API.html#title_RMV2-disableForcedVariableSubstitution