Yes, Floe supports static attachments. As well as dynamically, generated HTML or PDF attachments based on the email body or any other email type. This can mostly be done in the configuration without any coding.
Yes, Floe supports adding an HTML button (or buttons) to an email body which will generate a return email that is then processed via SAP email Inbound Processing and the Floe Inbound user-exit.
Floe performs several security-related validations before passing the inbound decision capture to the user-exit which ultimately will be responsible for making any SAP updates. These validations include the email DKIM Signature, Recipients Address, and returned email identifier is 256 AES Encrypted.
The Floe back-end component installs on an ABAP stack (SAP NetWeaver or S/4HANA). Floe Email Builder is a SAPUI5 app that can be deployed like any other Fiori app
Yes this is possible. Floe can be used to replace Adobe forms / SMARTFORMs / SAPscripts. The steps are: Create an email template in Floe. Again, this will need to be made up of several sections in order to handle the repeating rows. Change (or clone) the SAP output program so that it calls the Floe [...]
Yes this is possible with Floe. The steps are to: Create an email template in Floe. You will either define a table or a ‘repeating section’ with the fields from the table. Give each field a name in the template. (Use a unique name – the SAP field name is normally fine.) Pass the internal table [...]
For three great reasons: Floe is really low cost and has a flat rate charge. If you can move some of your workload to Floe and reduce a pay per email service charge by more than the Floe subscription you have a business case. Floe is integrated into SAP, not interfaced. This means any data in [...]