• RSS Feed

  

Release Notes for Floe 210

Table of Contents
  1. Introducing Floe and Stelo integration.
  2. Bugs Fixed
  3. Enhancements
    1. Inbound Email Processing
    2. PDF Generation
    3. Attachment Improvements
    4. Low code logic
    5. General Improvements
  4. Floe 200 -> Floe 210 Upgrade Notes
    1. Requirements:
    2. Installation Tasks:
    3. Post-Installation Configuration Tasks:

Introducing Floe and Stelo integration.

FloeFloe 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

Bugs Fixed

  • Floe Note 6: You are using FLOE to send a Workflow email.

Enhancements

Inbound Email Processing

  • A big step forward for workflow and relationship management is that Floe now supports decision capture in email. The Floe Designer now supports the addition of html buttons in the email body that will return an email to the sender for SAP inbound processing via the Floe Inbound user-exit.
  • The “Inbound Processing Engine Log” can be used to track Floe inbound e-mail processes.
  • Floe has new security improvements and makes several security related checks before passing the inbound decision capture to the user-exit which ultimately will be responsible for making any SAP updates. These include the email DKIM signature validation, the recipient address and an encrypted identifier inside the return email body.

PDF Generation

  • Email content created or maintained via the Email Designer app can now be easily be converted to PDF using Renda.io and then automatically attached to an outgoing email.
  • The Email Builder also has a number of new PDF specific settings like margin, orientation, and encryption password.
  • A new function module /FLOE/PDF_OUT can be called to return a pdf using Renda.io.

Attachment Improvements

  • Attachments can now be added to emails without the need for any coding in the Email Designer app or in the ABAP backend attachment user-exit. The attachments can be “static”, that is files uploaded from a local machine to be included with the email type or “dynamic” where the generated email body is also included as an attachment in HTML or PDF format.
  • Any email type in Floe can be added to another email type as an attachment by simple configuration either as html or as PDF files. Dynamic PDF attachment handling requires Renda.io.

Low code logic

  • With the integration of low-code logic, developers and business users with varied experience levels can create emails using drag-and-drop components and model driven logic. This allows for the inclusion dynamically built emails with the use of simple logic in the email template blocks allowing for blocks to be included or excluded based on the logic statement without writing any ABAP. 

General Improvements

  • New email types can be created by copying an existing email type so speeding development.
  • New email types can be created directly via the Designer app without needed to pre-configure in the SAP backend.
  • Email type specific variables can now be configured in the back-end. These, along with global variables, can be added to the email content via a new button in the Email Designer rich-text editor
  • A new button allows users to fill the “Variables” section of the “Test Trigger” app view with the variables from the email content and block determination logic.
  • A new button allows users to create instances of repeating and nested repeating variables in the “Variables” section of the “Test Trigger” app view.
  • Library blocks can be classified as “Favourites”. This user-specific setting ensures that they appear at the top of the list.

 

Floe 200 -> Floe 210 Upgrade Notes

Requirements:

Floe 210 now has an addtional requirement for the WEBCUIF component which is included by default in most SAP configurations.

The upgrade will proceed without this component in place but be aware that inbound email processing and decision capture will not function correctly without it.

Installation Tasks:

Activities 1-3 must to be carried out in each system.

  1.     Apply the Floe_INST_210.SAR ABAP Add-On with SAINT
  2.     Run SGEN on FLOE after the upgrade has been applied via SAINT.
  3.     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 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
  • Add a new number range interval:
    • In transaction SNRO create a new number range interval for object /FLOE/ATID  
    • Create a number range interval: 01    0000000001    999999999
    • Save and create the interval in each system.
  • If you wish to use the new Inbound Email functionality you must set-up inbound email processing:
    • In transaction scot, go to Settings->Inbound Processing and create the following entry:
    • Communication Type: Internet Mail
    • Recipient Address: The address to which inbound FLOE emails are to be sent. This address will likely need a rule on the corporate email network that forwards it to the SAP system via a Send Connector or other method.
    • Document Class: *
    • Exit Name: /FLOE/INBOUND_HANDLER


For more information on how to configure and test the SAP SMTP configuration please see:  SAP SMTP (Offline) Configuration
This should be set-up on every system in your landscape.

Next go to IMG transaction Floe->Administration->System Settings and maintain the Inbound Settings section for each system:

  • Error Email Type: When an inbound email process fails, FLOE attempts to send an email back to the initial sender with the error details. Here you can select the email type to be used for that email (more details can be found here).
  • Recipient Email Address: Insert the email address configured in the above step.
  • Ignore Attachments: Set this flag if you wish attachments on inbound emails to be discarded and not processed by the system.
  • If you wish to use FLOE in German you should refresh the area menu buffer in order to see the new area menu transactions in German. To do this: Go to transaction se43n, type "/FLOE/MAIN" in the "Area Menu" field and then in the toolbar select Edit->Refresh Buffer
     
 

Last modified on 8/12/2020 9:49 AM - Copyright Arch 2022.