Hi @JMoura , 

This cannot be done easily through configuration. 

Yes, FSM can extract data in XML,JSON or CSV. 

but extracting an attachment is unfortunately not supported through configuration. 

(with custom code this can be done off course). 

Besides, for sFTP we rely on third-party software nevertheless.

For FSM on-premise the sFTP upload is done by WinSCP component, however this is not supported in the cloud though. 

I would recommend to implement such requirement outside FSM. 

You can use Business Rule Process “81” - Attachment Directory, to set the attachment folder for certain type of attachments.

Then use an external solution e.g. WinSCP  (but there should be plenty of others i think) to automatically upload the file from the FSM Attachment folder to the sftp server.

https://winscp.net/eng/docs/guide_automation

hope that helps, 

Ruben

Hi @ruben.maas,

Thank you so much for the fast response! I still have a couple of questions, if you are able to help me clarify this out.

We are using FSM on-premise, so your suggestion is to set up WinSCP (or similar) to listen to a specific folder on the machine (specified by the Business Rule Process “81”), then if WinSCP detected changes, it would upload to the client’s sFTP server in the desired folder structure, is that it?

This way, since we would be implementing the requirement outside FSM, the attachment extract limitation would not be an issue.

Best regards,

João Moura

Hi @JMoura ,

Yes you are absolutely correct.

The key here is to place the attachments, which needs to be upoaded to sftp folder, in an separate folder.

This can be done using Business Process 81 I expect. 

The rest can be configured outside FSM.

-Ruben

Thanks once again for the clarification @ruben.maas, I think this is now clear from my side.

Best regards,

João Moura