I have tried the testing like below and there is no error is occuring but the data flow is not happen from Remedy to Service now
.1.Configured the URL, User Name, Password and Field mapping in APL:RestfulVendorForms:Table.
2. Created entry from Vendor Table (Vendor - Combination of above screenshot table entry with Mentioned Regular form).
Created a entry inside the table and tried to click "SAVE" Button. It's allowing to save. Once it saved , if i check into Service now end it doesnt hit the table.
Checked the following logs, it doesnt thrown any errors.
Can you please advise the way of test is OK or Do I need to test based on any steps. Please advise.
Ok....so, my recommendation is to look in the arjavaplugin.log, this will tell you (if you have debug enabled) all of the headers and body that's being sent over. Then test the same in a different Rest client like Postman, or any really....if it works in one but not the other, then there are differences you need to figure out...if it doesn't work in either, contact your admin on the other end and give them the details that are being handed over (headers/body) and ask for their assistance in what's going wrong and correct appropriately
I have changed few things from Remedy APL Table and tried to add some info and attachment into vendor form. It showing an error like below. With error message base64 value also appending with limited length.
The configured message template is hitting to target location. ie., sending an message to service now with below errors. Can you please help to resolve?
ARERR  Message not in catalog; Message number = 8790 : Failed : HTTP error code : 400 Method: POST - Bad Request - URL: https://devinstance.service-now.com/api/now/table/ecc_queueSUFHIEdCUyBMSU1JVEVEIFNwZWVkYmlyZCBXYXksSGFybW9uZHN3b3J0aCBXZXN0IERyYXl0b24sIExvbmRvbiBQb3N0IENvZGU6IFVCNzBHQQ==
Sending a value to service using below info template.
Ok...the URL you are showing in the error message seems to indicate that you have one of your fields set to append to URL, and it seems to be the MyAttachmentElement field from the screenshot and I'm 100% positive that can't possibly be right....I've only ever seen a restful service handle attachment data as part of the body...so if you are providing it as part of the URL, which it seems you are, that would be a malformed URL and certainly a bad request...
When dealing with complex situations like this I typically try to get it working in something like Postman, and then replicate the postman results in Remedy itself....
Why not look at the OOTB solution designed and built for ticket brokering, synch?