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 4 Next »

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

Installing or Upgrading to PhixFlow Version 8.3.20

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. The following special instructions apply for this release:

Special Upgrade Instructions

Important Information

None.

Improvements

DEV-13017: Geometric functions now take an optional precision parameter which is the number of decimal places in the geometry coordinates. The default is 0dp. The geoBuffer function can take a second optional parameter quadrant segments which defaults to 8.

Bug Fixes


DEV-12994: Fixed issue whereby updating records in a Stream View failed on SQL Server if there were more than 10 records selected. This was caused by in incorrect query to fetch the selected records from the database.

DEV-13264: In Analysis, on SQL Server only: where a lookup pipe has an 'is in' filter condition with more than 10 elements in the 'is in' list, lookups always return the same data even if the values in the 'is in' list are different (e.g. if the repeated lookups are driven by an input multiplier).


  • No labels