Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

PhixFlow Ltd. is pleased to announce the release of PhixFlow 8.3.1. This page describes the improvements and fixes in this version. This minor release includes important fixes.

Installing or Upgrading to PhixFlow Version 8.3.1

To install a new PhixFlow instance:

  1. Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies.   
  2. Follow the instructions in Installing PhixFlow.
Sections on this page

To upgrade an existing PhixFlow instance: 
  1. 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.
  2. Ensure you have a backup of the database before upgrading PhixFlow.

  3. Follow the Upgrading PhixFlow steps. It is important to complete Step 8, in which you apply any Special Upgrade Instructions for all the intermediate releases between your current version and the version to which you are upgrading. We also recommend that you republish the PhixFlow data as described in Step 10 of Upgrading PhixFlow.

Improvements

DEV-8256  The following modelling objects no longer include passwords when exported.

  • file collectors
  • file exporters
  • FTP sites.

This means passwords are not transfered to another instance. When importing to:

  • a new instance, you must update the modelling object to set the password.
  • an existing instance where the modelling object already exists, PhixFlow preserves the existing password field. 

Bug Fixes

DEV-8229  Setting a number format in PhixFlow no longer affects how a value is saved to the database.

DEV-8235  You can now type only 15 digits into a floating point field, as this is the maximum number of significant digits allowed. 

DEV-8283  When running the upgrader, a database connection leak could occur. This has been resolved. The leak could cause errors such as "too many files".

  • No labels