Hello Ramanee Samal,

Sorry, Still it's challenging. Probing the option to achieve this requirement.

Regards,

Suresh

Suresh,

I have a version of my Restful plugin (Restful API Plugin – A Programming Legacy ) coming out by the end of the month that supports Attachments both to and from Remedy....this might help solve this problem.

Hi Lj,

Will that be supported in Remedy ITSM 8.1?

Thanks,

Ramanee

Yes...my plugin supports > 7.1 I believe....I forget exactly what version BMC switched away from native api's.....certainly doesn't work on 6.x....but 8.1 is no problem.

Thanks LJ,

This will be very much helpful for me.

Please update me once it is ready for use.

Thanks,

Ramanee Samal

Hello LongWing,

Thanks for your reply. Waiting for the date and your update.

Hope, it will helpful for more people.

Regards,

Suresh L

I have now published version 3.0

Restful API Plugin – A Programming Legacy

Thanks for the update LJ. Will try to do in my environment. Hope, it will resolve the attachment issue.

Regards,

Suresh L

I hope it will as well

Hi LJ,

I tried importing the attachment and I am getting the following error. Can you please help?

Version : 7.6.04 SP5

Thanks,

Suresh

Suresh,

My sincerest apologies, I work really hard to try and get rid of all of the darn __c from all of my forms...I missed a few in this sample.  I have re-published 3.0 with the updated sample, please re-download and verify.

Thanks LJ now I am able to import the form successfully.

My requirement is to push the attachments when added to the worklog of an incident to service now.

1. So to accomplish this, when I add an attachment to the worklog,I will be pushing the attachment to vendor form as well.(Assume APL:Sample Attachment in our case)

   Is my understanding correct ?

2. Once I push it to that form, plugin will push the attachment contents in base64encoding format to mentioned endpoint in the APL:RestfulVendorForms:Table for that vendor form.

Appreciate your help and efforts towards this.

Thanks,

Suresh.

Suresh,

The samples are just that....samples...they are functional examples of various aspects of the tools capabilities.  With that said, the samples won't do ANYTHING with ServiceNow....you will need to build out a Table record that corresponds properly with your ServiceNow instance, build out the fields, then create a Vendor form that utilizes the Table/Field records....then, once you have all of that built out and tested, you can start utilizing the Vendor form to push attachments out to ServiceNow.

You will need to read the user manual, likely many times, to understand how the plugin works....restful communication is an exceedingly complex subject and takes awhile to get your head wrapped around it

Since you are using SOAP...   When you put your cursor over the "payload" element (in Developer Studio while mapping) what type does it say that element is?

Remedy already uses base64Binary for an attachment.   If the Service Now WSDL is describing the payload element as a String then the Service Now WSDL needs to be corrected.   Sometimes you can cheat and save the WSDL to your local PC, edit the WSDL in Notepad changing the payload element to be type base64Binary and use that as the WSDL source of your Set Fields call.  You will then be able to map the Attachment data to the payload. (Size is not required to be mapped to them)

Be careful as Service Now has in the past had a limit on the size of an attachment (something around 60k) due to their using of a string internally.

Fred

I completely  agree and understand LJ what you have said.

My point was to say that once I have my new vendor form configured with URL which I need to post, authentication and template defined for request along with an attachment field, only think to achieve later will be to create a new record in my vendor form is to push the attachment name from my workflow. Once a record is created PLUGIN would push to the URL specified as in the table for that vendor form. Is that correct?