Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

Installing or Upgrading to PhixFlow Version 8.2.10

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.


Panel
borderColor#7da054
titleColorwhite
titleBGColor#7da054
borderStylesolid
titleSections on this page

Table of Contents
indent12px
stylenone


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.

  4. After upgrading, we recommend you republish the PhixFlow data as described in Step 10 of Upgrading PhixFlow.

Improvements

DEV-7986  If a datasource has an unsupported JBDC JDBC 4 or 4.1 driver, PhixFlow no longer prevents it being used by reporting an error. PhixFlow will continue to report an error errors for JDBC 3 and earlier drivers.

Bug Fixes

DEV-7989  The  _prompt function now correctly allows only alpha-numerical values and the underscore character in filter field names.

DEV-7088  When exporting Excel files from the console, the Created Date is displayed7088  When downloading data from the Imported/Exported Files tab in the system console, the Excel output file will now correctly display the Created Date column.

DEV-8000  Fixed an issue in which fields on a form were not being correctly updated. The issue only occured whenForm fields are now correctly updated in the following circumstances:

  • a grid was driving drives a second grid, that was driving drives a form
  • and the record selected on the first grid caused causes the second grid to return no records. The
    Previously, the form fields were not being updated to show blank values.