How does the LOE compare using Floe for email creation vs SAP standard tools?
With Floe you get much further, more quickly, with much less custom code. This table describes where the effort is required:
Does Floe support email attachments?
Yes, although of course in many scenarios, using Floe replaces the need for a separate attachment. Floe supports both "static" attachments (where the attachment is pre-uploaded and not personalised) and "dynamic" attachments, which are generated by Floe using an output template and SAP data. Dynamic attachments can be generated as HTML or as PDF*. Alternatively, Floe [...]
Can Floe email include PDFs?
Yes, although of course in many scenarios, using Floe replaces the need for a separate PDF attachment. Floe supports both "static" attachments (where the attachment is pre-uploaded and not personalised) and "dynamic" attachments, which are generated by Floe using an output template and SAP data. Dynamic attachments can be generated as HTML or as PDF*. Alternatively, [...]
Is SAP Workflow user decision capture supported?
Floe supports the addition of buttons to capture user decisions which are sent back to SAP by email. The buttons generate a return email that can be processed by Floe and trigger the ongoing process within SAP.
How does Floe handle security of emails when used for decision capture?
It is important to protect your core SAP system from suspicious inbound emails, and Floe helps this by performing various security-related validations. The validations occur 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 [...]
Is Floe certified by SAP?
Yes! Floe is a certified add-on for SAP S/4HANA, and works with any NetWeaver ABAP stack from 700 upwards.
What is the technical architecture for Floe?
Floe is comprised of: A back-end 'SAP Add-on' component, installed into your on-premise SAP system. A Fiori app Template Designer, which can be deployed to your front-end server or the SAP cloud. A cloud-based image repository (no installation component required) Floe integrates with Renda.io cloud services for the generation of PDF documents and for the sending [...]
Right now we use SAP output forms. Can we replace them with Floe emails?
Floe can be used to replace legacy Adobe forms, SMARTFORMs and SAPscripts. In many cases, where these legacy technologies create a PDF document this can be replaced by email content with no attachment. Since Floe can be used for attachment generation too, it provides a single Design Tool for all types of SAP output: Email SMS [...]
Can I populate email content from a SAP internal table?
Yes this is easy with Floe, and used often for many types of output. 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. Pass the internal table into the Floe API [...]
We have an interfaced emailing product, why would we want or need Floe?
Many SAP customers have looked outside SAP for a solution to maintain output templates. This can include the print output template design, the printing, the email design, and the emailing process. With Floe you can bring this back inside SAP to make significant savings. Floe is integrated into SAP, not interfaced. This means any data in [...]