Version 2020 Release 2
•It is possible to retry the execution of one or more steps multiple times in case of error, see Retry on Error.
•A job can execute steps in a postponed way, after returning the result, which is particularly suitable in case of jobs invoked through Web service calls, see Postponed Steps.
•A new optional Host name field is available in the setup page, see Defining the Network Settings. This makes SSL configuration more flexible, and also enables you to test run Web services directly from the job configuration page.
•It is possible to configure file system triggers to fire when new files or directories are added to a specified directory. This trigger is different from the existing "Modified date" in that it does not fire if files within the polled directory are subsequently modified.
•The AS2 partner configuration page provides a new option which makes it possible to reformat an AS2 message to its canonical form, see Interoperability settings.
•When defining a credential of type OAuth 2.0, you can configure the authorization details to be in the POST request body. This is an optional method in addition to the already supported standard method of supplying authorization details in the POST request header, see OAuth 2.0 Credentials.
•The procedure for accessing the Setup Page has been simplified.
•FlowForce Server jobs that call Web services can now authorize with the service provider using the OAuth 2.0 protocol. To this end, the "credential" entity in FlowForce has been extended to support OAuth 2.0 fields as well, see OAuth 2.0 Credentials.
•You can define credentials both in MapForce and FlowForce Server, and either embed them into the mapping at design time, or supply them as parameters to the execution step in FlowForce Server, see Credentials in Mapping Functions.
•When defining a credential object, you can restrict it to a specific domain of usage. "Usage" can be one or more of the following: job execution, FTP, HTTP.
•Portable file, folder, and database references defined in MapForce (also known as "Global Resources") can be deployed to FlowForce Server and be consumed by a mapping function. If necessary, you can change directly in FlowForce the resources (file, folder, or database references) used by a mapping function—this will affect all FlowForce jobs using that function. You can also create or edit resources directly in FlowForce Server, with some limitations, see Resources.
•When exporting job configuration data to another FlowForce Server instance or to a .zip archive, you can optionally choose to export sensitive data as well, see Importing and Exporting Configuration Data.