Introducing Floe and Stelo integration.
Floe delivers outstanding e-mails using HTML content that are fully integrated with data from your SAP systems. Arch Floe can be used for any SAP e-mail communication and can be incorporated into existing business processes easily. Arch Floe provides impressive SAP integration, so that any data from SAP systems can be incorporated into the body of the e-mail. Moreover, recipients, images and attachments can be determined from business logic stored within the SAP system.
As organisations move to the SAP Fiori paradigm for user interaction the need arises to manage tailor-made processes and user interfaces, beyond simply adding a new front-end to a SAP transaction or BAPI. Arch Stelo provides the framework for the development and management of custom Fiori processes, enabling organisations to easily build and maintain a suite of Fiori applications and the related business processes.
Learn More about Floe and Stelo
Standards Compliance
- Floe is SAP certified to run on SAP S/4 HANA.
Bugs Fixed
- Floe Note 8: Runtime error GENERATE_SUBPOOL_DIR_FULL occurs when the FLOE API is run multiple times in the same internal session.
- Floe Note 9: You get the following error when attempting to generate a PDF: "Renda.io 400 error. Bad Request".
- Floe Note 10: You are not able to change block properties via the "FLOE Designer" application.
- Floe Note 11: Emails appear with a blank email subject in transaction SOST.
Enhancements
- Integration with Renda.io SMS service: Users can now maintain SMS content via the Designer app and send an SMS from the back-end by calling function module /FLOE/SMS_OUT.
- Images can now be uploaded to a cloud repository via the Floe Designer app. These images are then available when maintaining and sending FLOE emails.
-
The default theme for the version of the Floe Designer app which uses the ui5 libraries from the sap cloud (/floe/ebuildercloud) has been changed to “Quartz”. The default theme for the version which uses the local libraries (/floe/ebuilder) is still “Belize” so as not to increase the requirements for using Floe. These default themes can be overwritten by adding the sap-theme parameter to the URL used to launch the app. For example:
- <protocol>://<host>:<port>/sap/bc/ui5_ui5/floe/ebuildercloud?sap-theme=sap_fiori_3_dark
- When the app is embedded in the Fiori launchpad, the launchpad theme will be used.
- A new field “PDF Class” has been created for content blocks. When content is converted to PDF using Renda.io, this field will determine whether the block is a header or a footer (or neither). Headers/footers repeat at the start/end of every page of the PDF.
- The email subject and description can now be maintained via the Floe Desiner app in the different languages content has been configured in, rather than only in the log-on language as was previously the case.
- A number of new fonts have been added to the app rich text editor. Users can add extra fonts by running the “Add fonts to FLOE Designer” app IMG transaction.
Floe 210 -> Floe 220 Upgrade Notes
Installation Tasks:
Activities 1-3 must to be carried out in each system.
- Apply the Floe_INST_220.SAR ABAP Add-On with SAINT
- Run SGEN on FLOE after the upgrade has been applied via SAINT.
- Apply relevant Floe Notes and Transport.
If the Floe Email Designer is to be deployed in a Hub or Cloud scenario please reference the following guide.
Post-Installation Configuration Tasks:
-
When upgrading a production server, a new Floe license key will be required.
- To request a license key click on the "Get Floe" button on https://www.floe.com and submit the form.
- To install the license key use activity IMG -> Cross Application Components -> General Application Functions -> Floe -> Administration -> Install License Key
- Optional: If you wish to use FLOE to send SMS, create an RFC destination to the Renda.io SMS service and maintain the “Renda.io SMS Service Settings” fields in the “System Settings” IMG transaction as described in https://documentation.renda.io/integrations/floe
- Optional: In order to use the Image Repository, enter the API Key for this service in the “Image Cloud Repository Settings” section of the “System Settings” IMG transaction. If you have not been provided with an API Key for this service, please contact Arch support at Support@arch-global.com.