We have looked at the incidents that haven't been bonded and they all contain '<' or '&' symbol in the Long description field. In the logs, this field is not being parsed correctly and it results in the attached error. All other special characters are being parsed correctly, for example: > ' " .
It is caused in the function below when the SOAP message is sent to Verizon:
a. Script Include: SOAP Message
b. Function: stripWhiteSpace
The error is as follows:
Caused by error in Script Include: 'SOAPMessage' at line 103
Steps to Reproduce
Create an incident that contains special characters (such as < or &) in the Long Description field of the Incident form. Note that the special characters should pass across the ebond to Verizon, but they do not.
This issue has been fixed.
Related Problem: PRB565512