Page Comparison

Introduction

Following the success of the changes to the user interface in PhixFlow 9, Version 10 continues to improve usability and expand the capabilities of PhixFlow.  

For an overview of the enhancements provided in this release visit and take a look at the Improvements and New Features section in this document:

https://www.phixflow.com/platform/whats-new-in-phixflow-10/

PhixFlow is pleased to announce the release of PhixFlow Version 11.0.1. 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 10.0.0 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.24 or later in order to be upgraded. If this is not the case please first upgrade to 8.3.24.
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 10.0.1 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 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.

   This release includes changes that affect the PhixFlow database. After upgrading, remember to republish the PhixFlow data as described in Step 10 of Upgrading PhixFlow

Schema Changes

Improvements and New Features

None.

Bug Fixes

DEV-

17403 - Fixed problem with positioning windows when they are configured with a percentage size.

DEV-15421 - Added a prompt for deleting a form field that a filter refers to Added a prompt for deleting a form field that an actionflow uses as a mapping. Added a prompt when Adding a primary key attribute to a form that already has it.

DEV-16040 - Improvements to messages returned to the user where there are errors in filtering. 

DEV-16064 - Actionflow Email nodes are now passthrough.

DEV-16096 - Cancelled/failed actions are now correctly removed from the active section of the console in all circumstances.

Bug Fixes

DEV-16004 - Table actions now respond to cancellation by the user; new record sets are marked as incomplete.

DEV-16007 - Fixed rollback not working when “Only allow restricted task plan run permission users” is ticked

DEV-16075 - Table attributes that are flagged as 'Foreign Key' are now automatically considered to be 'Indexed'.

DEV-16097- Fixed memory leak in requested actions (lookups).

DEV-16135 - The grid to show log messages for the currently selected running tasks now automatically refreshes to show new messages17465 - In an Actionflow, using a Save Action to insert a record into a table that has already had a record inserted by a different Save Action within the same Actionflow will no longer error.

DEV-17480 - Fixed Actionflow Loop nodes sometimes generating "state was 'CLOSED'" errors.

DEV-17498 - Fixed embedded Actionflow node Connection Points not showing.

DEV-17499 - Fixed not always being able to drag from Actionflow Input Connection Points onto action nodes.

DEV-17516 - Resolved issue where deselecting all rows on grids was no longer working.

DEV-17521 - Fixed problem with resizing relational grid columns which caused reopening the screen to display an error.

DEV-17541 - Added a loading spinner and duplicate protection when dragging an actionflow node between two existing actionflow nodes.

DEV-17571 - PhixFlow will now write an entry to the System Console → Audit Summary each time it starts with its version number and details of any database patch scripts that executed. The Action description starts with “Executing db\upgrade”.