@Leeann, after digging into the data it looks like the failure is caused by a newline character inside the licenseNumber value which is why the JSON parsing is failing and triggering the ITC.
Regarding the Convert text to JSON Wrk Action, this can handle escaping newlines, carriage returns, and quotes within values but it requires a specific configuration to do so correctly.
In the current setup the entire Converted text output is being passed directly into the Convert text to JSON. When used this way, the action attempts to escape the entire blob as a single value, which can result in invalid JSON instead of properly escaped fields.
To use this action correctly, only the individual values should be passed in as data library variables so the bot knows exactly what needs escaping. For example, the JSON should be constructed like this:
{
"launchTitle": "{{launchTitle}}",
"user_id": {{user_id}},
"requirement_id": {{requirement_id}},
"first_name": "{{first_name}}",
"last_name": "{{last_name}}",
"state": "{{state}}",
"licenseNumber": "{{licenseNumber}}",
"reqState": "{{reqState}}",
"role": "{{role}}",
"customUniqueID": "{{customUniqueID}}"
}
This ensures that each value is escaped independently and correctly even when user entered data includes newlines or quotes.
That said, I agree that the action behaviour and documentation are not very clear about this requirement. I have opened a ticket to improve both the action description and documentation so this is more obvious going forward.
https://wrk-technologies.atlassian.net/browse/WASR-1599
