Release 11.1.4

Introduction

PhixFlow is pleased to announce the release of PhixFlow Version 11.1.4. 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.


Special Upgrade Instructions

None for 11.1.4. Please check the Special Upgrade Instructions for all the intermediate releases between your current version and this one.

Bug Fixes

DEV-17473 - Memory leak fix applied to Analysis Models and Actionflows providing improved processing performance.

DEV-18002 - Validations with an invalid regular expression will no longer fail silently. An invalid regular expression message will be displayed in the Validation tooltip for the associated Form Field(s).

DEV-18007 - Fixed the "hide loading spinner" option for Actionflows which was not working. When the loading spinner is not hidden it will now display after half a second instead of immediately.

DEV-18020 - Fixed run analysis failing on tables if the table configuration was changed during the analysis run.