Page Comparison

Introduction

PhixFlow is pleased to announce the release of PhixFlow Version 11.2.0 This page describes the improvements and fixes in this version.

Installing or Upgrading PhixFlow

To install a new PhixFlow instance:

1. Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies. 
   1. Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
2. Follow the instructions in Installing PhixFlow.

To upgrade an existing PhixFlow instance: 

1. PhixFlow must be at version 8.3.18 or later in order to be upgraded to this version. If this is not the case please first upgrade to 8.3.18.
2. Check System Requirements and Compatibility for changes to the system requirements or supported database versions. For example, you may need to upgrade your database or Java version.
   1. Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
3. Ensure you have a backup of the database before upgrading PhixFlow.

4. Follow the Upgrading PhixFlow steps. It is important to complete any Special Upgrade Instructions for all the intermediate releases between your current version and the version to which you are upgrading.

Bug Fixes

DEV-17959 - A second, alternative, domain suffix can be configured for ActiveDirectory by setting the login.activeDirectory.alternativeDomain property. If a user is not found in Active Directory with the primary domain (login.activeDirectory.domain) then the alternative domain will be tried.

DEV-17990 - Improvements have been applied to how PhixFlow captures audit capture information to ensure that log messages can't be cannot become lost. 

DEV-18000 - Resolved the issue of import importing configuration deleting sort order Sort Order attributes when a table and references a sort order are in from a different applications application or packagespackage.

DEV-18051 - Grids showing relational attributes are now refreshed when the table for the relational attribute is updated by an Actionflow.

DEV-18056 - An optional configuration setting (, dbAuditService.haltOnDiscardCommitted) , has been added which when set will terminate PhixFlow if audit records are unable to be written to the database after extended periods of retrying (. The default time period is 24 hours, however this is configurable by setting the property dbAuditService.retryForMs, in (server.properties for PhixFlow 10.0 ) serveror in local.properties or (for version 11.0 onwards) local.properties).

DEV-18062 - Maximum Parallel HTTP Actions property field added into the System Configuration to to handle parallel HTTP actions.

DEV-18063 - Added a "new Wait " action node in Actionflows. Wait actions will hold any records passed into them until all previous action nodes have completed and then pass on a record with only a count attribute containing the sum of all records it has received.

DEV-18107 - Audit records are now also recorded in a separate audit.log file as they are being generated. This guarantees their availability even if the application is restarted before they can be written to the database.

DEV-18114 - In API Endpoints, a Timeout option has been added that allows control over the maximum time (in ms) a request will wait for before timing out. If specified, this will override the default timeout of 60s. However, the Timeout can be overridden by a timeout URL parameter.

DEV-18116 - Added 'Log Request' and 'Log Response' options to the API Endpoint properties to log its request and responses into the System Console.

DEV-18132 - Creating Grid CRUD Edit Actions now work works correctly when done performed directly after creating the Grid.

DEV-18149 - Embedded Json JSON now supports date and time values, converting them into a String representation of the timestamp.