Version 2020 Release 2 of Altova FlowForce Server was released on March 17, 2020. Learn about all the new features below and update to the latest version.
|FlowForce® Server 2020r2 (March 17, 2020)||Advanced Edition||FlowForce Server|
|Option to retry blocks on error|
|File trigger option for new files|
|Ability to convert incoming AS2 messages and MDNs to canonical|
|Support for OS X 10.15|
A new Retry on Error option makes it possible to retry the execution of one or more steps multiple times when an error is thrown. For instance, if a process requires a connection to a web service or API that may have an intermittent connection issue, trying multiple times can often solve the problem without needing to abort the process altogether on the first error.
You can configure the number of times to retry a block, and if the maximum number of retries has been reached and the block still encounters an error, the job will fail.
Retry blocks also let you configure additional steps to complete before retrying the process, such as resending an authentication token, or even completing other steps before retrying the step.
A job can set aside steps to be executed at a later point in time, after returning the result, which is especially applicable for jobs invoked through Web service calls.
A typical FlowForce job returns a result only after all processing steps have finished. As long as there are running steps, the job must wait for them to finish before returning the result. For jobs exposed as Web services, this means that the HTTP transaction must be kept open for the entire duration of the job execution, which may take several minutes or even hours in some cases, depending on the volume of processed data.
To handle such cases gracefully, developers can use a special kind of FlowForce step called a postponed step. Postponed steps do not prevent a job from returning a result right away, because their processing will take place only after the job has returned a result. When a job contains postponed steps, FlowForce will first process all non-postponed steps, then it will return the job result, and only afterwards proceed to running any postponed steps.
FlowForce Server supports file system triggers that monitor a file or directory for changes to execute a job when the defined criteria are met. It is now possible to configure file system triggers to fire when new files or directories are added to a specified directory. It’s easy to configure the directory polling interval (e.g., every 60 seconds), and you can optionally set the start and expiration date of the trigger. Wildcards can be used to filter specific files of the directory.
FlowForce Server Advanced Edition supports sending and receiving secure AS2 messages to/from partners.
To improve interoperability of signature checks between different platforms, in v2020r2 the FlowForce Server AS2 partner configuration page provides a new option to reformat an incoming AS2 message or MDN return receipt to its canonical form.
upport for running FlowForce Server on Mac OS has been updated to include OS X 10.15.
Learn about all the additional functionality that has been added in each release of StyleVision Server.
|FlowForce® Server 2020 (October 9, 2019)||Advanced Edition||FlowForce Server|
|Support for Global Resources|
|Support for OAuth 2.0 in Web services calls|
|FlowForce® Server 2019r3(April 2, 2019)||Advanced Edition||FlowForce Server|
|New option to customize logging of step parameter values|
|Ability to handle raw body content as a job parameter|
|Support for Windows Server 2019|
|Support for OSX 10.14|
|FlowForce® Server 2019 (October 17, 2018)||Advanced Edition||FlowForce Server|
|Support for job distribution among multiple servers|
|FlowForce® Server 2018r2 (April 17, 2018)||Advanced Edition||FlowForce Server|
|Completed implementation of AS2|
|FlowForce® Server 2018 (October 3, 2017)||Advanced Edition||FlowForce Server|
|New Advanced Edition with support for AS2|
|FlowForce® Server 2017 Release 3 (April 4, 2017)|
|Windows Server 2016 Support|
|OSX 10.12 (Sierra) Support|
|Support for RaptorXML+XBRL Server 2017r3, MapForce Server 2017r3, and StyleVision Server 2017r3|
|FlowForce® Server 2017 (October 4, 2016)|
|Support for RaptorXML+XBRL Server 2017, MapForce Server 2017, and StyleVision Server 2017|
|FlowForce® Server 2016 Release 2 (February 16, 2016)|
|Support for pending server licenses to automatically transition to a new license when a current license expires|
|Support for RaptorXML+XBRL Server 2016r2, MapForce Server 2016r2, and StyleVision Server 2016r2|
|FlowForce® Server 2016 (September 30, 2015)|
|Support for RaptorXML+XBRL Server 2016, MapForce Server 2016, and StyleVision Server 2016|
|Support for Windows 10|
|Support for new Linux versions: Debian 8 & Ubuntu 15|
|FlowForce® Server 2015 (September 17, 2014)|
|Ability to move configuration objects (jobs, deployed mappings, credentials, etc.) from one FlowForce Server to another – Simplifies migration from a development server to the production environment|
|Feature to abort job execution – Administrators can easily abort execution of an individual job without impacting other tasks in process|
|Active Directory integration – FlowForce can now optionally use Windows Active Directory to authenticate users, simplifying administration|
|User password management extensions – Administrators can reset user passwords, enforce password complexity, or require new users to create a password at the first login|
|User privileges report – Permits easier management of users and resources|
|FlowForce® Server 2014 Release 2 (March 19, 2014)|
|Job cache enhancements – New Cache Purge and Cache Refresh triggers are available, and caching can be enabled for jobs with parameters|
|Support for macOS 10.9 – Adds to previous support for Mac OS|
|FlowForce® Server 2014 (October 29, 2013)|
|Cache job results – Administrators can cache results of time-consuming tasks to speed response for HTTP jobs|
|FlowForce® Server 2013 (April 29, 2013)|
|Cross-platform support – FlowForce Server 2013 is announced in versions for Windows, Linux, and Mac OS platforms|
|Support for StyleVision Server – FlowForce Server jobs can execute StyleVision Server to render XML and XBRL data into HTML, RTF, PDF, OOXML documents, and forms|
|FTP support – Direct read/write support for FTP servers with stored login credentials when required|
|Flow control for jobs – Loops, conditions, result evaluation, and error handling can all be applied to control execution of job steps|
|Email support – Configurable email notification for job steps and errors|
|FlowForce® Server Beta 3 (August 28, 2012)|
|Beta period extended – the beta test period for existing customers using MapForce® 2012 or later Enterprise or Professional Edition is extended until March 31, 2013.|
|Remote Job Requests – Requests can be sent to FlowForce Server from any remote machine using an HTTP client that allows to the user to send requests under the control of the FlowForce permission system, so that job execution via the request interface can be restricted to specific users.|
|Job Parameters – Job parameters can be defined, allowing values to be passed to individual steps of a job.|
|Sub-Jobs – Jobs can be called by other jobs. It is now possible to use any job as a single step in another job.|
|Time Trigger Enhancements – Timer triggers now allow selection of the time zone and a default time zone can be configured.|
|Enhanced Job Timing – Timer triggers have now separate settings for overall starting time and ending time, and for unique starting and ending times on each day for repetitions.|
|Individual Job Queues – Jobs each have their own queue, allowing job instances to run in parallel. Every job has its own queue that controls how many instances of the job may run in parallel, and how much time must pass between executions.|
|New Authentication Options – A new system role, "Authenticated", is automatically assigned to all users who log on to FlowForce.|
|Enhancements and Revisions to Existing Features – The user interface is simplified and operations related to configuration objects are centralized on one page, along with numerous other enhancements.|
|FlowForce® Server Beta 2 (March 28, 2012)|
|Beta period extended – the beta test period for existing MapForce® 2012 or later Enterprise Edition and MapForce® 2012 or later Professional Edition customers is extended until September 1, 2012.|
|Access control – defined Users and Roles, Object Permissions, and Credentials are implemented so departments can work independently without seeing or overwriting each other’s data.|
|Web interface enhancements – provide quicker access to job schedules, active triggers, and more.|
|FlowForce Beta 2 available in 64-bit version – allows the MapForce Beta 2 module to process very large data files and provides compatibility with 64-bit database drivers.|
|FlowForce® Server Beta 1 (December 14, 2011)|
|First public beta edition – for free trial during the beta period by existing MapForce® 2012 or later Enterprise Edition and MapForce® 2012 or later Professional Edition customers.|