Send smartforms to email using CPI

[#1]

Hi experts,

I have a report that generates some smartforms, and I have to send them to an email using the plataform cloud integration. I don`t know if I am in the right way, but I think that I have to convert the smartforms to XSTRING and send them to the CPI, but I don't know how to send it from my report and which communication channel should I use.

I had made some integrations using "Postman" like the 'sender' to send a simple email with CPI to my own account, but nothing else like that. I really need some light about this.

Thank you!

[sumanth171]

Hi vanessa,

As per the error given it is the issue with proxy side, I am not really sure on ABAP end how to resolve this but you can try below link if helps.

https://archive.sap.com/discussions/thread/1351392

Moreover, as per my understanding you are exposing the proxy as a webservice for connecting to CPI. If the original pdf files to be placed in the SFTP sever, you still need to use Base64 decrypt function in CPI.

Regards,

Anil

[VanessaHayakawa]

Hello Anil,

Thanks for your response. I made the conversion to base64 like you told me to and now I`m trying to send it to CPI.

I`ll get back to you with the outcome as soon as I have one.

Kind regards.

[sumanth171]

Hi Vanessa,

You can encode the smart form as Base 64 string and then assign that string value to your xml structure. CPI team can decode that and send that content as mail attachment.

[VanessaHayakawa]

Hello Anil,

I created a iflow using soap connector in sender as you can see below, and I had to change to SFTP (no more mail).

When I try to generated the proxy in abap occurs the error: "CX_XSDANY_PARSE_ERROR:XSLT exception.An error occurred during serialization in the simple transformation program /1SAI/TAS155709B28D5CD8AF9820.The error 'value expected at '%PDF-1.3'' ocurred when parsing an XML fragment".

I am converting the OTF to XSTRING because the proxy created a structure with parameter type "XSDANY".

Testing the iflow in SOAPUI the connection works, so I really think that I am doing something wrong in proxy side.