SOAP Integration and & ampersand causing data feed fault
Our Archer data feed between Archer and ServiceNow faults if a special character like & is in the filename.
This is my understanding without seeing any of the actual log data from Archer that attachments are feed into ServiceNow using the SOAP integration. Most of the SOAP integration’s use XML as the language and in XML, the ampersand is a reserved character that has a special meaning so when it’s used in actual text, it normally has to be escaped, for example by replacing “&” with “&” in the name.
Even if we don’t use XML in the SOAP integration, there’s definitely something with the names of specific attachments that causes them to fail and it seems likely that there is something with how the names of certain attachments are not encoded correctly for their language. It’s difficult to know the root cause without see the log or knowing the specifics but we know that the common thread seems to be the name of the attachment.
I need a means to either mask the attachments field so that I can prevent files named with & in the filename from being submitted, forcing them to be renamed, upon Save/Submit test the filename to be sure it is valid, or I need a method to allow them to pass through the data feed.
When I move files between Archer servers via data feeds, I don't have this issue.
Any advice is appreciated.