Are you submitting attachments into these systems via web services?
If yes, I suggest you try the same from "neutral party" soapUI and see whether it works fine into ServiceNow and/or Remedy...
What exactly is this "neutral party" Soap UI and how do I do that?
SoapUI (SoapUI | SourceForge.net) is a free open-source tool to test (consume) web services with.
It's easy to install and use (just create new project and load your wsdl file or url)...
With "neutral party" I meant that it is an independent system, that will help you test/validate proper working of the ServiceNow and Remedy web services.
SOAP UI is the a Nice Interface to manually test and debug Web Services.
Was using soapUI just a few hours ago to test our Remedy and xMatters integration that goes live tomorrow
Actually I happened to figure out the root cause of it.
The data of the attachment is being stored in the form in base64 format and the field data type that has been provided by the third party is a STRING.
That is why I am only able to map the attachmentName with that of the payload field of the third party, where I am supposed to find this field to map: 'attachmentData'.
I am unable to find this field in the mapping which actually contains the data.
Is there any way that I can find this field to map instead of the attachmentName. in my filter at the time of consuming the third party's WSDL?
1 of 1 people found this helpful
Attachments via Web Services for Service Now are stored in base64 "String" format, so the data you are seeing is correct.
The Attachment Data input is as follows (i.e. the base64 encoded string):
Sample Attachment Data:
You can test the Attachment by pasting the base64 encoded string into the following on-line converter:
You need to supply all the relevant information to Remedy (and to Service Now) for the attachment (i.e. Attachment Name, Attachment Size, Attachment Data):
Service Now may also want a mime type for the Attachment, this you would also need to send if it is required (and code accordingly to extract).
you will need to ask the Service Now application Administrator what data they require for attachments and map accordingly.
Service Now have made different updates regarding Attachments throughout the versions, so you need to get the required information from the Service Now Administrator.
Need your help :
Could you please guide about webservice integeration of Remedy-Servicenow?
I have tested servicenow incident webservice URL using soap UI, the tickets are getting created.
But when we are consuming the same URL in remedy filter webservice action we are getting error
ARERR  Message not in catalog; Message number = 9130 : ; nested exception is:
java.net.ConnectException: Connection refused
We are using Remedy 7.6 version.
Amagond, that could be a connectivity issue.
In case you haven't tried that already: install SoapUI on the Remedy server and test the webservice-call from there.
If the webservice-URL you're calling is using SSL (https), then you probably have to set up a certificate on the Remedy server and on the machine(s) where you'll run Dev Studio. You'll find some info on this in this thread.
I am also working the same requirement. We are trying to achieve the attachment transfer from Remedy to Service Now Via ECC queue. I have created a filter with Service Now Ecc Queue WSDL and used the Associated form as HPD:WorkLog and mapped the field like below.
Is your requirement has been completed successfully? Can you please help me on this?
While transferring the attachment to Service Now,we need to send as Base64 Encoded format. So that, ECC queue can work. Do we have any option to change the Base64 format while tranferring from remedy.
I too have same requirement .
Is there a way to convert a file to base64Binary format in remedy?
How did you managed ?