Release 8.3.4

PhixFlow Ltd. is pleased to announce the release of PhixFlow 8.3.4. This page describes the improvements and fixes in this version. This minor release includes important fixes, including a change to the database schema.

Installing or Upgrading to PhixFlow Version 8.3.4

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.

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 7

      Running the migration scripts to PhixFlow version 8.3.4 includes a required schema change to the PhixFlow database.

    • 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. There are no special instructions for this version.

Sections on this page

Features and Improvements

DEV-5911  The PhixFlow now opens the login screen in a pop-up window. This means that if your session times-out, the application is unaffected. In previous versions, session timeout caused the application to reset to the login screen and there was a risk of losing data being entered into forms.

DEV-9735  PhixFlow is quicker to load applications.

DEV-9977, DEV-10118  Previously, PhixFlow instances using Microsoft SQL Server were restricted to a limit of 2000 items in the “is in” list of a filter clause. That restriction has been removed. You can specify “is in” lists with more than 2000 items.

DEV-8206  HTTP collectors and exporters no longer strip newline characters from the returned data. 

This change may affect analysis models that use HTTP collectors or exporters. If processing in your model relies on the absence of line breaks, you can use the following attribute expression to remove \n, \r and \r\n characters:
replaceAll(in.value, "[\r\n]", "")

New Features for Charts

There are new features and improvements to bar and line charts (graphs), in the Stream View →  Chart Layout section.

  • DEV-9009  You can Force Horizontal Axis Ticks, so that PhixFlow displays all values on the horizontal axis.
  • DEV-9002, DEV-8999  The value axis has new options to specify:
    • Minimum Value: set the minimum value where the chart will start
    • Maximum Value: set the maximum value where the chart will end
    • Axis Increment: set an increment for the values on the axis
    • Axis Number Format: specify the format for the numbers that appear on the axis.

Bug Fixes

Fixes for Charts

DEV-9001  A chart legend positioned below a chart no longer overlay the data.

DEV-9010  The line graph right axis is now working. This means you can display multiple charts on one chart.

DEV-9006, DEV-10046  The Date and DateTime format is now correctly applied to a chart horizontal axis. This means there is no longer excessive whitespace under a date or date/time axis.

DEV-10047  For charts, the angle setting for the horizontal axis now works correctly.

DEV-10121  The labels on a chart's vertical or angled axis now have labels in the correct positions, rather than overlapping the chart. 

DEV-10052  Line and bar charts now work correctly when the Show Legend is not ticked.

DEV-9694  The axis scale on a chart no longer intermittently loses the axis minimum value.

DEV-9693  On a chart, the mouse-hover tooltip now correctly displays values with decimal places.

DEV-10089  When configuring a chart, dragging stream attributes onto the view properties → View Attributes section no longer reports an error.

Other Fixes

DEV-9864  Opening the list of streams in the repository is now much faster.

DEV-9870  Opening the list of stream views in the stream properties is now much faster.

DEV-8937, DEV-9806  The system task no longer stops if one of the following error conditions occurs:

  • processing a corrupt stream
  • deleting a managed file.

The system task omits the problem case and continues processing. 

DEV-9850  Memory used when copying a configuration object is now released once the copy has completed. Previously, after many copy operations, the server could run out of memory.