Release 10.0.10

Owned by Thomas Swindells
Last updated: Feb 12, 2024
3 min read


Introduction

PhixFlow is pleased to announce the release of PhixFlow Version 10.0.10. This page describes the improvements and fixes in this version.

Installing or Upgrading to PhixFlow Version 10.0.10

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 on an unsupported database version.
  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.
    1. Please email support@phixflow.com if you are planning to run PhixFlow on an unsupported database 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.

Special Upgrade Instructions

None

Schema Changes

Schema changes are required for this release.

New Features

  • DEV-17055 - If a field is backed by an Attribute, the Attribute's type is used during the field validation. It ensures that input fields backed by Attributes can accept only values valid for the Attribute. Fields backed by Integer attributes now check if the value provided is a valid Integer without any decimal numbers. Fields backed by Float or Decimal attributes now check if the value provided is a valid Number.
    This can be overridden by setting a custom Validation Type on the field.

Bug Fixes

  • DEV-17153 - Reusing a nested actionflow which contains a loop will no longer intermittently cause values to be applied incorrectly.

  • DEV-17134 - Table filters are now shown in the filter dropdown on the properties for relational fields.

  • DEV-17118 - Using 'is in' in a filter on a View Action on SQL Server now works without errors when using lists longer than the value of sqlserver.filter.maxInlineListSize=10 in the server.properties file.

  • DEV-17109 - Fixed problem with setting new form after deleting the old one, if the old had a background filter rule set on the element.

  • DEV-17108 - PhixFlow now correctly displays the Home Screen Message HTML (rather than the default text) on the login screen which is displayed after a logout.

  • DEV-17107 - Fixed error in oracle migration script (oracle/migration/9.0/migrate_schema_from_8_3_24_to_9_0_0.sql) caused by missing semicolon.

  • DEV-17103 - Improved performance of running confirmation actions.

  • DEV-17099 - System Console grids now correctly display the 'Restore files' option.

  • DEV-17091 - Dropdown Fields backed by a foreign key now correctly update form's records.

  • DEV-17086 - Form fields backed by Table Attributes now correctly have the Aggregate Function and Filter options available in their properties.

  • DEV-17076 - Filters can now be applied to relational aggregate views.

  • DEV-17074 - Preferred Parent Type in nested components are now correctly copied when creating new components.

  • DEV-17063 - Fixed cause of error message 'Could not copy property filterId' shown when adding a new form after deleting the old one. This occurred if the element had a default filter set.

  • DEV-17061 - Fixed issue where fields having number formats configured with 'suppress trailing zeros' would sometimes ignore the decimal places setting. This resulted in ".0" being displayed for whole numbers when decimal places was set to 0.

  • DEV-17038 - More descriptive error message added when failing to read data from a table due to configuration issue.

  • DEV-17032 - Importing a package that contains an action will no longer delete mappings to instances of that action that exist in other applications.

  • DEV-17022 - Editing Card Components and Views no longer displays a 'cannot cast to class' error for users without the VIEW_PRIVATE_CONFIG permissi

  • DEV-15395 - Double clicking on a record is now disabled whilst the record is being autosaved.