Release Notes
- Former user (Deleted)
- Thomas Swindells
- Lee Smith
PhixFlow new features and fixes are described in release notes. Each release has a version number with the format X.Y.Z, for example 7.9.3. Numbers ending in zero, for example 9.0.12, indicates a major release with significant changes. If Z is 1 or more, it indicates a minor release that contains security updates and bug fixes.
This page includes the release notes for:
Release 11.2.2
Introduction
PhixFlow is pleased to announce the release of PhixFlow Version 11.2.2 This page describes the improvements and fixes in this version.
Installing or Upgrading PhixFlow
To install a new PhixFlow instance:
- Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies.
- Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
- Follow the instructions in Installing PhixFlow.
To upgrade an existing PhixFlow instance:
- PhixFlow must be at version 8.3.18 or later in order to be upgraded to this version. If this is not the case please first upgrade to 8.3.18.
- 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.
- Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
- Ensure you have a backup of the database before upgrading PhixFlow.
Follow the Upgrading PhixFlow steps. It is important to complete 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 for 11.2.2. Please check the Special Upgrade Instructions for all the intermediate releases between your current version and this one.
Bug Fixes
DEV-18301 - Background image position for component styles will now copy the vertical position to the horizontal position if the vertical position is not set. Additionally it will again accept numbers without "px" at the end
DEV-18295 - In Actionflows, on tables configured to keep audit history, having two save nodes that modifies the same record no longer duplicates it.
DEV-18266 - Resolved failure on SQL Server to load application translation maps.
DEV-18233 - XML Namespace creations no longer throw an error
DEV-18229 - Resolved issue where frozen columns on grids could cause the grid to be displayed incorrectly.
DEV-18190 - Fixed issues with hover popup not appearing on Analysis Models, Workflows, Actionflow and ERDs when zoomed out.
DEV-18184 - Fixed a publishing error caused by importing a table that previously existed and was deleted.
DEV-18177 - In Analysis Modelling, the issue of emails with long subjects being omitted from processing has been resolved.
DEV-18118 - Improved GUI response times after updating a screen.
DEV-18117 - On startup the audit log files are reread and audit events that were not successfully persisted will be replayed into the database.
Release 11.2.1
Introduction
PhixFlow is pleased to announce the release of PhixFlow Version 11.2.1 This page describes the improvements and fixes in this version.
Installing or Upgrading PhixFlow
To install a new PhixFlow instance:
- Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies.
- Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
- Follow the instructions in Installing PhixFlow.
To upgrade an existing PhixFlow instance:
- PhixFlow must be at version 8.3.18 or later in order to be upgraded to this version. If this is not the case please first upgrade to 8.3.18.
- 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.
- Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
- Ensure you have a backup of the database before upgrading PhixFlow.
Follow the Upgrading PhixFlow steps. It is important to complete 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 for 11.2.1. Please check the Special Upgrade Instructions for all the intermediate releases between your current version and this one.
Bug Fixes
DEV-18117 - On startup the audit log files are reread and any audit event that was not successfully persisted will be replayed into the database.
DEV-18118 - Improved GUI response times after updating a screen's content.
DEV-18177 - In Analysis Modelling, the issue of emails with long subjects being omitted from processing has been resolved.
DEV-18184 - Fixed a publishing error caused by importing a table that previously existed and was deleted.
DEV-18190 - Fixed issues with hover popup boxes not appearing on Analysis Models, Workflows, Actionflow and ERDs when zoomed out.
DEV-18233 - XML Namespace creations no longer throw an error.
DEV-18266 - Resolved the failure issue when using SQL Server to load application translation maps.
Release 11.2.0
Introduction
PhixFlow is pleased to announce the release of PhixFlow Version 11.2.0 This page describes the improvements and fixes in this version.
Installing or Upgrading PhixFlow
To install a new PhixFlow instance:
- Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies.
- Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
- Follow the instructions in Installing PhixFlow.
To upgrade an existing PhixFlow instance:
- PhixFlow must be at version 8.3.18 or later in order to be upgraded to this version. If this is not the case please first upgrade to 8.3.18.
- 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.
- Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
- Ensure you have a backup of the database before upgrading PhixFlow.
Follow the Upgrading PhixFlow steps. It is important to complete 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 for 11.2.0. Please check the Special Upgrade Instructions for all the intermediate releases between your current version and this one.
Bug Fixes
DEV-17959 - A second, alternative, domain suffix can be configured for ActiveDirectory by setting the login.activeDirectory.alternativeDomain property. If a user is not found in Active Directory with the primary domain (login.activeDirectory.domain) then the alternative domain will be tried.
DEV-17990 - Improvements have been applied to how PhixFlow captures audit information to ensure that log messages cannot become lost.
DEV-18000 - Resolved the issue of importing configuration deleting Sort Order attributes when a table references a sort order from a different application or package.
DEV-18024 - Resolved stability issues when rate limiting was configured on multiple HTTP collectors or HTTP exporters. HTTP Exporters now throttle per batch of records being processed.
DEV-18051 - Grids showing relational attributes are now refreshed when the table for the relational attribute is updated by an Actionflow.
DEV-18056 - An optional configuration setting, dbAuditService.haltOnDiscardCommitted, has been added which when set will terminate PhixFlow if audit records are unable to be written to the database after extended periods of retrying. The default time period is 24 hours, however this is configurable by setting the property dbAuditService.retryForMs, in server.properties for PhixFlow 10.0 or in local.properties for version 11.0 onwards.
DEV-18062 - Maximum Parallel HTTP Actions property field added into the System Configuration to handle parallel HTTP actions.
DEV-18063 - Added a new Wait action node in Actionflows. Wait actions will hold any records passed into them until all previous action nodes have completed and then pass on a record with only a count attribute containing the sum of all records it has received.
DEV-18107 - Audit records are now also recorded in a separate audit.log file as they are being generated. This guarantees their availability even if the application is restarted before they can be written to the database.
DEV-18114 - In API Endpoints, a Timeout option has been added that allows control over the maximum time (in ms) a request will wait for before timing out. If specified, this will override the default timeout of 60s. However, the Timeout can also be overridden by the timeout URL parameter.
DEV-18116 - Added 'Log Request' and 'Log Response' options to the API Endpoint properties to log its request and responses into the System Console.
DEV-18132 - Creating Grid CRUD Edit Actions now works correctly when performed directly after creating the Grid.
DEV-18149 - Embedded JSON now supports date and time values, converting them into a String representation of the timestamp.
Release 11.1.4
Introduction
PhixFlow is pleased to announce the release of PhixFlow Version 11.1.4. This page describes the improvements and fixes in this version.
Installing or Upgrading PhixFlow
To install a new PhixFlow instance:
- Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies.
- Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
- Follow the instructions in Installing PhixFlow.
To upgrade an existing PhixFlow instance:
- PhixFlow must be at version 8.3.18 or later in order to be upgraded to this version. If this is not the case please first upgrade to 8.3.18.
- 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.
- Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
- Ensure you have a backup of the database before upgrading PhixFlow.
Follow the Upgrading PhixFlow steps. It is important to complete 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 for 11.1.4. Please check the Special Upgrade Instructions for all the intermediate releases between your current version and this one.
Bug Fixes
DEV-17473 - Memory leak fix applied to Analysis Models and Actionflows providing improved processing performance.
DEV-18002 - Validations with an invalid regular expression will no longer fail silently. An invalid regular expression message will be displayed in the Validation tooltip for the associated Form Field(s).
DEV-18007 - Fixed the "hide loading spinner" option for Actionflows which was not working. When the loading spinner is not hidden it will now display after half a second instead of immediately.
DEV-18020 - Fixed run analysis failing on tables if the table configuration was changed during the analysis run.
Release 11.1.3
Introduction
PhixFlow is pleased to announce the release of PhixFlow Version 11.1.3. This page describes the improvements and fixes in this version.
Installing or Upgrading PhixFlow
To install a new PhixFlow instance:
- Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies.
- Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
- Follow the instructions in Installing PhixFlow.
To upgrade an existing PhixFlow instance:
- PhixFlow must be at version 8.3.18 or later in order to be upgraded to this version. If this is not the case please first upgrade to 8.3.18.
- 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.
- Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
- Ensure you have a backup of the database before upgrading PhixFlow.
Follow the Upgrading PhixFlow steps. It is important to complete any Special Upgrade Instructions for all the intermediate releases between your current version and the version to which you are upgrading.
Special Upgrade Instructions
If upgrading please review Special Upgrade Instructions for details of any additional Special Upgrade instructions for intermediate releases between your current version and the version which you are upgrading.
Template Package
A new version of the Template Package Serene Grey is available as part of this release. To get the best from your PhixFlow system we recommend downloading and installing this version:
- Download: Serene_Grey.zip
- Instructions: Installing Template Packages
Bug Fixes
DEV-17323 - Setting the default values on form fields now works correctly on Cards.
DEV-17629 - The Table Attribute Picker is no longer limited to the first 250 attributes, it now displays all available attributes.
DEV-17945 - Fixed various issues with display and filtering of values in dropdown fields.
DEV-17952 - Copying Annotations now works using Ctrl+drag on Actionflows.
DEV-17971 - Within Actionflows a fix has been applied to ensure all Save Action attributes are visible after an upgrade.
DEV-18005 - Fixed the issue of not being able to reference pull pipes going into a table within the expressions of collectors connected to the table via a lookup pipe.
DEV-18014 - Running actionflows directly, using the Run Action feature, didn't always pass in the user defined values for attributes that didn't have a default value set. This is now fixed.
Release 11.1.2
Introduction
PhixFlow is pleased to announce the release of PhixFlow Version 11.1.2. This page describes the improvements and fixes in this version.
Installing or Upgrading PhixFlow
To install a new PhixFlow instance:
- Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies.
- Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
- Follow the instructions in Installing PhixFlow.
To upgrade an existing PhixFlow instance:
- PhixFlow must be at version 8.3.18 or later in order to be upgraded to this version. If this is not the case please first upgrade to 8.3.18.
- 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.
- Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
- Ensure you have a backup of the database before upgrading PhixFlow.
Follow the Upgrading PhixFlow steps. It is important to complete any Special Upgrade Instructions for all the intermediate releases between your current version and the version to which you are upgrading.
Special Upgrade Instructions
If upgrading please review Special Upgrade Instructions for details of any additional Special Upgrade instructions for intermediate releases between your current version and the version which you are upgrading.
Template Package
A new version of the Template Package Serene Grey is available as part of this release. To get the best from your PhixFlow system we recommend downloading and installing this version:
- Download: Serene_Grey.zip
- Instructions: Installing Template Packages
Bug Fixes
DEV-17608 - Warning messages about mixing shorthand CSS properties now display the correct component's name.
DEV-17928 - Pasted images now correctly render in HTML form fields.
DEV-17947 - Resolved issues when upgrading from 9.0.10 whilst using a clustered setup of MySQL 8.
DEV-17948 - Resolved issues where some external database connections would fail with the error “Unable to validate object”.
DEV-17949 - Resolved an issue where HTTP header expressions within Analysis Models would return empty values.
DEV-17956 - When the View option, Show Brush on Charts is disabled, the brush no longer shows.
DEV-17958 - Fixed an issue where the Maximum Rollover Requests in the Rate Limiting of an HTTP Connection was being treated as the total maximum number of new tokens, not the maximum number of rolled over tokens, causing issues when the maximum was configured as 0.
Release 11.1.1
Introduction
PhixFlow is pleased to announce the release of PhixFlow Version 11.1.1. This page describes the improvements and fixes in this version.
Installing or Upgrading PhixFlow
To install a new PhixFlow instance:
- Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies.
- Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
- Follow the instructions in Installing PhixFlow.
To upgrade an existing PhixFlow instance:
- PhixFlow must be at version 8.3.18 or later in order to be upgraded to this version. If this is not the case please first upgrade to 8.3.18.
- 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.
- Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
- Ensure you have a backup of the database before upgrading PhixFlow.
Follow the Upgrading PhixFlow steps. It is important to complete any Special Upgrade Instructions for all the intermediate releases between your current version and the version to which you are upgrading.
Special Upgrade Instructions
If you are upgrading from a version that is pre version 11 then please also see Special Upgrade Instructions for details of additional Special Upgrade instructions for your version inwards.
(DEV-16708) HTTP Headers on HTTP actions have been updated to ensure correct capitalisation e.g. contenttype will become Content-Type. Due to this amendment existing Actionflows should be reviewed and any access to returned HTTP Header values should be adjusted to use the correct capitalisation if they do not currently use standard header capitalisation.
(DEV-17452) As part of the upgrade, all Actionflows that previously were configured as API Endpoints have been converted to the new API Endpoint type Actionflow. For the endpoint to return data, the response body needs to be mapped to the output body attribute in the new API Endpoint.
Template Package
A new version of the Template Package Serene Grey is available as part of this release. To get the best from your PhixFlow system we recommend downloading and installing this version:
- Download: Serene_Grey.zip
- Instructions: Installing Template Packages
Improvements and New Features
Screens
DEV-16698 - It is now possible to set custom tooltips on grid cells aka table cells, such as displaying details of the action that will be run on-click.
DEV-17352 - It is now possible to not specify the size of a Screen, when unset it will adjust its size to the content automatically.
DEV-17527 - It is now possible to fire button actions or change true/false fields values when a Screen is unlocked by using alt+click.
Actionflows
DEV-17075 - Added the ability to throttle the rate at which requests to external systems are made for a HTTP Action within an actionflows.
DEV-17445 - In Actionflows, it is now possible to share settings between different HTTP Actions using the HTTP Configuration setting.
DEV-17579 - Added an option to run an Actionflow directly from the property editor, Actionflow toolbar, and right-click menu of the repository. This option will show a prompt form to enter any input parameters and will open a grid to display any output records.
DEV-17641 - Added default value expressions to Actionflow attributes. When set, if no mapping is made to that attribute or if that value provided is null or unavailable (for example if the initiating user did not have permission to see it) then the default value expression will be evaluated and the value set to its result. Default value expressions do not use sequence and are automatically resolved in the appropriate order based upon other attributes they reference.
DEV-17729 - Actionflows can now have custom icons assigned.
Performance
DEV-17013 - Improved configuration export performance.
DEV-17507 - Images fetched by File Display components on a screen will now be cached, improving performance.
DEV-17706 - For performance reasons, grids in the system console will no longer show the row count by default. Clicking the ... will display the count.
Charting
DEV-17433 - It is now possible to create multi-layers hierarchical graphs by setting Background Filter Rules using chart selection. Line charts can now indicate which data point is selected.
DEV-17438 - Cumulative sum and cumulative percent are now available as aggregate functions. This allows Pareto graphs to now be generated.
DEV-17456 - It is now possible to create Custom Series on charts, which include fixed values, percentile, and other statistical functions including expressions.
DEV-17811 - Disabling vertical axis on charts now correctly hides the labels.
DEV-17877 - In Charting when grid lines (guides) are disabled the axes lines remain visible. In addition horizontal grid lines are now shared between the left and right axis to avoid overlapping.
Integration
DEV-17302 - A new Private Secrets section has been added to the full repository that enables the management of Private Secret Keys.
DEV-17452 - API actions are now a separate type of Actionflow called API Endpoints. API Endpoints have fixed input attributes (body, headers, contentType and url), and fixed output attributes (body, headers, contentType and statusCode).
DEV-17496 - Native support to easily create JSON documents within expressions is available. Additionally new functions have been added to allow the conversion of these into XML documents. See help, toJson, toXml and JSON Support.
DEV-17888 - New transpose() Function added.
Bug Fixes
DEV-16708 - The headers returned by HTTP Actions are now normalized to follow standard header naming rules (e.g. Content-Type).
DEV-17255 - Data Points are now correctly displayed on Line Charts when the option is selected.
DEV-17319 - Improved performance when adding new components to a screen.
DEV-17501 - Line Charts and combined bar and line charts now work for x-axis attributes of type String.
DEV-17503 - Sorting by x-axis now works for charts when the x-axis attribute is of type String.
DEV-17551 - Sorting graphs with horizontal axis attributes of number types now works correctly.
DEV-17650 - Bulk delete Actionflow nodes now pass through record attributes.
DEV-17697 - Formatting Rules can now refer to the _user internal variable.
DEV-17708 - Improved performance when displaying the audit summary on the Console screen.
Release 11.0.2
Introduction
PhixFlow is pleased to announce the release of PhixFlow Version 11.0.2. This page describes the improvements and fixes in this version.
Installing or Upgrading PhixFlow
To install a new PhixFlow instance:
Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies.
Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
Follow the instructions in Installing PhixFlow.
To upgrade an existing PhixFlow instance:
PhixFlow must be at version 8.3.18 or later in order to be upgraded. If this is not the case please first upgrade to 8.3.18.
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.
Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
Ensure you have a backup of the database before upgrading PhixFlow.
Follow the Upgrading PhixFlow steps. It is important to complete any Special Upgrade Instructions for all the intermediate releases between your current version and the version to which you are upgrading.
Schema Changes
Handled automatically from PhixFlow Version 11.
Improvements and New Features
Minor patch release only containing bug fixes.
Bug Fixes
DEV-17731 | Resolved issue where HTTP Collectors and Database collectors would error with "illegal group reference" if the substituted value contains $. |
DEV-17718 | Filters created on a Card Components now included in its list of filters. |
DEV-17699 | Fixed delete actionflow nodes displaying an unhelpful error message when the primary key is not mapped, with a more informative error message. |
DEV-17640 | Improved performance of analysis tasks. |
DEV-17621 | Field Containers now correctly set the name of the first input field to match the name of the Field Container. |
DEV-17606 | Fixed auto-save actions on Views not having their auto save action method set to Table Action if they were previously configured. |
DEV-17599 | Fixed null pointer exception when a Database Collector query returns zero records. |
DEV-17592 | Bottom axis of bar charts are now aligned consistently with other types of graph, and the alignment of labels has been Improved, |
DEV-17590 | Analysis Models now correctly display pipes after dragging the Modelling Pane. |
DEV-17532 | Fixed Actionflows sometimes not displaying configuration changes until the Refresh button is clicked. |
DEV-15967 | Changing a View Attribute's name now automatically refactors the parent View's Formatting Rules expressions referencing that attribute. |
Release 11.0.1
Introduction
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:
- Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies.
- Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
- Follow the instructions in Installing PhixFlow.
To upgrade an existing PhixFlow instance:
- 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.
- 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.
- Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
- Ensure you have a backup of the database before upgrading PhixFlow.
Follow the Upgrading PhixFlow steps. It is important to complete any Special Upgrade Instructions for all the intermediate releases between your current version and the version to which you are upgrading.
Schema Changes
Handled automatically from PhixFlow Version 11.
Improvements and New Features
None.
Bug Fixes
DEV-17403 - Fixed problem with positioning windows when they are configured with a percentage size.
DEV-17465 - 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”.
Release 11.0.0
What's New
You requested, we listened! Welcome to PhixFlow Version 11.
We’ve made a whole host of usability and performance enhancements to make PhixFlow more powerful than ever. Over 70 significant improvements and new features have been added, for more information visit phixflow.com/whats-new-in-phixflow-11
Installing or Upgrading to PhixFlow Version 11
A significant change has been made to the installation process of PhixFlow which simplifies the process. Please read the new instructions before installing or upgrading.
PhixFlow systems running on a MariaDB database will not work with version 11, support for this database has now ceased. If you require help switching to a supported database please get in touch with our support team support@phixflow.com
To install a new PhixFlow instance:
- Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies.
- Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
- Follow the instructions in Installing PhixFlow.
To upgrade an existing PhixFlow instance:
- 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.
- 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.
- Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
- Ensure you have a backup of the database before upgrading PhixFlow.
Follow the Upgrading PhixFlow steps. It is important to complete any Special Upgrade Instructions for all the intermediate releases between your current version and the version to which you are upgrading.
Special Upgrade Instructions
Configuration Files
The previous configuration files e.g. phixflow-datasource.xml, have been replaced with two new files. Full details are provided in the installation/upgrade instructions:
- local.properties
- logback.phixflow.xml
Database Upgrader
The database schema installation/upgrade is run automatically as part of the installation/ upgrade when upgrading from version 8.3.18 onwards to version 11 or later.
File Table Upload Location
To use the new File Display component which facilitates the uploading of files by dragging and dropping files onto a PhixFlow screen, the following setup is required:
- On your PhixFlow server, create a directory where the files can be stored. This should be created alongside the other System Directories and be accessible to the application. See Minimum Setup for configuring System Directories.
- For example, /opt/phixflow/data/file
- In PhixFlow, from the Administration menu, open System → Configuration
- In the System Directories section → File Table Upload Location field, add the address of the directory setup in the first step, e.g. /opt/phixflow/data/file
- save your changes
- All uploaded files will now be placed in this directory. The directory should be backed up in line with your local policy.
Schema Changes
Significant schema changes are required for this release.
Discontinued Features
PhixFlow systems running on a MariaDB database will not work with version 11, support for this database has now ceased. If you require help switching to a supported database please get in touch with our support team support@phixflow.com
Changes to Privileges
None.
Improvements and New Features
Actionflows
DEV-9373 - Added Converge Action node to Actionflows. Converge actions have many inputs and one output.
DEV-12229 - Added the ability to extract actions to a new Actionflow in the Actionflow node context menu. This will create a new Actionflow and transfer all selected nodes into that Actionflow. All extracted nodes must be connected and not include any start phase nodes. If a start loop is extracted its corresponding end loop must be extracted too and vice-versa.
DEV-13875 - Added a Bulk Update Actionflow node, which can be used to set values on a table in bulk.
DEV-14196 - Added an XML Actionflow node, which can be configured with a path to extract values from an XML string.
DEV-14197 - Added a For Each Actionflow node, which will produce one output record for each entry in an input list or record set.
DEV-14907 - Added "Minimum records" and "Maximum records" to connection points on Actionflows, when set it will cause the Actionflow to error if the number of records received by the Actionflow is less than the minimum or greater than the maximum.
DEV-16096 - Cancelled/failed actions are now correctly removed from the active section of the console in all circumstances.
DEV-16411 - Added a Bulk Delete Actionflow node, which will delete data from a table using a filter or may be configured to delete all data from a table.
DEV-16746 - The Save action has been split into separate Save and Delete actions in the Actionflow screen.
DEV-16801 - Actionflow loops will now wait until all branching nodes are finished before beginning the next iteration of the loop.
DEV-16819 - HTTP Actions now support configuring the timeout, which can be configured in advanced properties.
DEV-16976 - Error messages for actionflows will now include the name of the action node and all parent Actionflows to make it easier to diagnose which node has generated the error.
DEV-16986 - It is now possible to control if an Actionflow can be triggered multiple times in parallel from the same client, i.e. can another run be started while the previous is not finished yet.
DEV-16995 - Added new options for API Actionflows. API Mode allows API Actionflows to be changed to "poll for result", where subsequent API calls can be used to fetch the result of the action when it is finished instead of waiting until it is finished before carrying on. Additionally, the URL will be displayed in the Actionflow property editor for API actions.
DEV-17094 - Converge Action has an "Input Connection" section added.
DEV-17127 - Actionflow phases will now wait for all nodes to finish before beginning the next phase.
DEV-17183 - Added the ability for the Delete action to delete files when a record from a file table is deleted. The behaviour can be configured to delete the file, archive the file to a specified directory or only delete the record but not remove the file from the server.
DEV-17216 - Bulk Update and Bulk Delete actions have an option to allow audited tables. Only non-audited tables can be updated or deleted if this is not ticked.
Administration
DEV-359 - Automatic schema installation is now implemented, no longer requiring the manual running of schema migration scripts.
DEV-6875 - Audits of automatic schema upgrades can be found in the DATABASECHANGELOG table.
DEV-7267 - The installation and upgrade process has been streamlined.
DEV-10952 - The installation and upgrade processes have been simplified and automated to no longer require manual running of database migration scripts.
DEV-11465 - System configuration can now be done via properties files rather than having to edit xml files directly.
DEV-14548 - The System Console Completed Tasks grid now includes the duration of the task.
DEV-16649 - The default password policy for new installs has been updated. The minimum length is now 12 with at least 1 each of uppercase, lowercase, numeric and special characters. The policy has not changed on existing installations.
DEV-16994 - Added a button to the System Console to take a snapshot of a running Actionflow, this will provide information about its current status. A snapshot is also provided upon Actionflow completion.
DEV-17050 - When "Only allow restricted task plan permissions users" is checked in the System Configuration, any scheduled task plan that attempts and is prevented from running will now appear in the console as a Warning rather than an Error.
DEV-17143 - System Configuration and System Logging have been removed from the Repository browser. They can still be accessed via the Administration menu with the rest of the options.
Analysis Models
None.
Applications
DEV-16233 - When connecting to a default-configured MySQL 8.0 database, it is necessary to specify either serverRsaPublicKeyFile or allowPublicKeyRetrieval on the URL. See https://mariadb.com/kb/en/about-mariadb-connector-j/ for detailed descriptions of these options.
Common Features
DEV-13336 - Email accounts can now be configured to use OAuth 2 authentication.
DEV-14575 - The PhixScript hash function will now handle secret values.
A new expandSecrets(value) function has been added, this takes a single string parameter and expands any secret tokens into their values.
DEV-15001 - A new System Configuration option "Default Template Package" has been added. Applications being created without a selected template package will use this value for the new application.
DEV-16040 - Improvements to messages returned to the user where there are errors in filtering.
DEV-16284 - Views with two aggregations to the same table now display correctly.
DEV-16322 - When connecting to a default-configured MySQL 8.0 database, it is necessary to specify either serverRsaPublicKeyFile or allowPublicKeyRetrieval on the URL. See https://mariadb.com/kb/en/about-mariadb-connector-j/ for detailed descriptions of these options.
DEV-16403 - Added new geometric functions:
geoUnion which computes a Geometry representing the point-set which is contained in two provided geometries.
geoGetNum which returns the number of Geometries in a GeometryCollection or Multipolygon.
DEV-16556 - Fixed stop() method so only a warning message is generated and it no longer incorrectly triggers an error message.
DEV-16589 - Improvements to the display of 'system errors' to make them more accessible by combining them into a single popup and revising the message.
DEV-16707 - In the Table properties, the option "Audit Manual Changes" has been moved from the Analysis Options section to the Advanced section.
DEV-16922 - The order of the home screen menu options (ERD, Screens etc.) has been revised.
DEV-17019 - There is a new 'Annotation' option in Analysis Models and Actionflow which allows the user to add notes to Models.
DEV-17038 - More descriptive error message added when failing to read data from a table due to configuration issue.
DEV-17185 - A new sql function has been added to PhixScript to facilitate the writing of SQL queries including the "?" query parameter markers so a list of corresponding parameters can be programmatically passed in.
DEV-17227 - Improved layout of the Applications screen to increase the size available for application titles and improved the tooltip.
ERD
DEV-12871 - A new type of table a File Table has been added to ERDs to support the uploading of files using the new File Display component on screens.
Performance
DEV-17103 - Improved performance of running confirmation actions.
DEV-17168 - Improved screen performance when editing screen component properties.
Screens
DEV-9335 - Improvements have been made to simplify how components are added to the screens or in the layers.
DEV-11222 - A default menu button option has been added in default components, used when a screen is dragged onto a menu, allowing for automatic button creation to open the screen.
DEV-12667 - Added right-click options to all major touchpoints where backing attributes can be set, and added icons to distinguish whether a backing attribute has or could be set.
DEV-12756 - Improved consistency of mouse cursors over active screen elements.
DEV-12871 - Added a new type of layout component, the "File Display". This can be used to upload/display previews of files linked to the new File Tables. Dragging a file onto the component will upload it.
DEV-13197 - It is now possible to set a “Default Sort Order" for dropdown components. It allows users to specify the order in which the data of the dropdown is displayed. Sort orders used in this field are saved against the field's backing attribute table.
DEV-14054 - Palettes now have a search box to quickly locate templates.
DEV-14767 - Grids that have no size, and are not set to Fit to available space will now automatically grow to the size of their content.
DEV-15382 - After creating a screen via the Screen window, the user is prompted to select a table to back the screen and also choose any required attributes to be displayed on the screen. In addition, screens can now be created via a new Create Screen button on the ERD toolbar.
DEV-15583 - Input fields cannot be moved inside data-bound components (e.g. Cards, Forms) backed by a table to the table backing the component.
DEV-15585 - Added Actionflow as an option for the Autosave action for views.
DEV-15743 - Layout components that are set to read-only now have an icon to identify them in the Layers and an indicator on their icon in the component properties.
DEV-16086 - Updated the way relation names are displayed.
DEV-16185 - Child components on a screen will now correctly be non-read-only in the case where the 'read-only' override tick box is selected and the read-only option is not set.
DEV-16283 - Improved relationship names on the Available Attribute selector.
DEV-16304 - Kanbans now allow multiple consecutive items to be selected using shift-clicking.
DEV-16473 - Changing a component's name now also updates all expressions referring to the component.
DEV-16489 - When adding a new component to a screen via a template, child objects are given unique names based on the parent and all expressions in the copied template are adjusted to use these names.
DEV-16537 - It is now possible to choose to sort Kanban columns by their column headings and reverse the Kanban column's sequence.
DEV-16558 - When clicking on an existing component on the canvas, the Style tab now opens by default rather than the Properties tab in order to streamline styling. When creating a new component the Properties tab is opened.
DEV-16561 - The component styles section has been improved by renaming "Autosize/grow" to "Fit to available space" and some related settings have been reordered.
DEV-16664 - Form field validation will be enforced by default when corresponding actions are run on newly created actions.
DEV-16667 - Deleting a screen when it is the only screen to use an area will now also delete that area (does not affect the template version)
DEV-16782 - The following alterations have been made to items in the Serene Grey template package:
* The minimum width of Tiles has been increased from 130px to 260px. This still supports viewing on mobile devices. The content which overflows outside of a tile is also now hidden so it does not exceed the borders of the tile.
* Horizontal and Vertically expanding tiles have been reworked to simplify the CSS used to achieve this mechanism. The Chevron direction has also been changed to better indicate the direction of expansion.
* There is a new Concertina Tile that provides several expanding areas in a single tile space.
* Tab headers text has been set up so the text which is too long to fully display will have ellipses added to the end. For example: "PhixFlow Inv..."
* The UID form field template has been removed from all card containers.
* The labels on form fields have been moved left to better align with the input field.
DEV-16844 - There is a new option for Dropdown Fields: Do Not Trigger Automatic Data Refresh in the advanced section. Ticking it stops any data-bound components (Grids, Cards) driven by the Dropdown from automatically refreshing when the value in the Dropdown changes.
DEV-16845 - There is a new option for Date and DateTime Fields: Do Not Trigger Automatic Data Refresh. Ticking it stops any data-bound components (Views, Cards) driven by the Field from automatically refreshing when the value in the Field changes.
DEV-16898 - The names of the "Add new" and "Create Menu" buttons on the Screens page have been revised to "Add Screen" and "Add Menu" respectively.
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.
DEV-17058 - Improved performance of copying components/saving components as templates.
Workflow
None.
Bug Fixes
Actionflows
DEV-15855 - Using a View action to find a record that has just been inserted by a Save action will no longer give a type conversion error.
DEV-15897 - Fixed some action nodes not being able to connect directly to the output points.
DEV-16064 - Email actions are now passthrough.
DEV-16117 - Resolved rare null pointer exception when using Actionflows.
DEV-16229 - Improved performance of opening the Mapping Configuration screen for Actionflows.
DEV-16302 - Dropping an Actionflow output point onto an end loop action now creates the connector to the driving output of the end loop node.
DEV-16470 - Deleting the screen backing an Actionflow 'Open Screen' node will no longer cause the action to fail due to mapping issues.
DEV-16517 - Opening an application while another application is opening will no longer sometimes cause both applications startup screens to display.
DEV-16638 - Actionflows will now ignore incomplete recordsets except those created in the same Actionflow.
DEV-16658 - Deleting an Action Task from a Task Plan will now correctly delete the associated instance of the Actionflow.
DEV-16712 - Embedded Actionflows will always run their first phase regardless of the phase they are embedded within. It is not valid for the embedded Actionflow to trigger other phases.
DEV-16847 - Resolved an issue where highlighting an action connector would sometimes cause the arrowhead to display in the wrong place.
DEV-16970 - Actionflow lookups will no longer fail if the action is run from a confirmation button and no record was selected for that input on the original action run.
DEV-16993 - By default the order of processing of Actionflows will maintain record order. Added a new option to Actionflow nodes to process the records in parallel, if checked the action may process faster but the order of records will not be deterministic.
DEV-17007 - Fixed action nodes not moving vertically above the top boundary of the canvas.
DEV-17027 - Within an Actionflow, where the first action of a nested Actionflow is a start loop action, it will no longer prevent passthrough of attributes on the outer action.
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-17153 - Reusing a nested Actionflow which contains a loop will no longer intermittently cause values to be applied incorrectly.
DEV-17201 - Added autocomplete for attribute names in expressions to all Actionflow nodes.
DEV-17205 - Dragging a Screen onto an Actionflow will now always correctly display the Open Screen node without waiting for a manual refresh.
DEV-17280 - Fixed an issue where Actionflows that open multiple screens would sometimes not open all of them.
DEV-17305 - Fixed an error when HTTP Actionflow nodes received nothing back as the response of an HTTP request.
DEV-17316 - When moving multiple action nodes in a short time span the nodes will no longer change location erratically.
Administration
DEV-15639 - Sorting the system console and other similar grids will now sort based on all records not just the current page.
DEV-16007 - Fixed rollback not working when “Only allow restricted task plan run permission users” is ticked.
DEV-16070 - A new tab has been added to the System Console which filters to only display Daily Logs.
DEV-16135 - The grid to show log messages for the currently selected running tasks now automatically refreshes to show new messages.
DEV-16281 - When an application containing scheduled task plans has been deleted, PhixFlow will no longer attempt to run those task plans.
DEV-16524 - Fixed migration script not running properly for Oracle databases with data in the font_size column for style.
DEV-17021 - Fixed post-migration issue, resulting in a 'QuerySyntaxException' triggered after editing custom logfile filters.
DEV-17099 - System Console grids now correctly display the 'Restore files' option.
Analysis Models
DEV-15070 - Analysis actions now only allow transactional tables to be included to ensure correct model operation.
DEV-16160 - Previously, when a database exporter was connected to multiple pull pipes, the input multiplier was evaluated for the driving push pipe and then re-evaluated for each of the pull pipes in turn. Now, the expression is evaluated only once, for the driving push pipe, and the result is re-used for each of the pull pipes without re-evaluating the expression.
DEV-16477 - Saving an Analysis Model after having moved the view and then adding a new object will no longer cause that object to move.
DEV-16534 - Fixed bug when processing JSON with arrays of objects from an HTTP Collector.
DEV-16697 - Fixed comments stripping within SQL expressions so that the comments are correctly removed after an escaped quote mark or double quote mark. For example, strings of the form 'Wouldn\'t it be nice', the apostrophe in the text is escaped and included in the comment now.
Option added on database exporters and collectors to choose whether to strip white space.
For migrated nodes the setting is enabled to match current behaviour.
For newly created nodes this defaults to false as it can cause issues when some styles of comments are used (e.g -- comment).
Applications
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.
Common Features
DEV-16004 - Table actions now respond to cancellation by the user; new record sets are marked as incomplete.
DEV-16154 - Exporting Audit Records to Excel now works correctly.
DEV-16294 - For views, in app mode, it will now only show the filters listed on the view in the section App Mode Filters. If you create the filter on the view grid then it will be visible in app mode but if it is created elsewhere then it will not be available in app mode by default.
DEV-16344 - Missing error messages in import.
DEV-16400 - Fixed error refreshing data on aggregate view with missing attributes.
DEV-16594 - User Detail view of a User Group now includes the last activity time.
DEV-16656 - Default Application and Default Screen have been removed from user configuration as they weren't functional. Startup actions can be used to control which screen an application initially displays.
DEV-16673 - Setting the locale when creating a user no longer errors.
DEV-16685 - Pie charts now export correctly.
DEV-16862 - Deprecated drivers have been removed from the available drivers list where they are not in use.
DEV-16883 - Fixed a bug where the first parameter of an AND function was ignored if it evaluated to null whereas if any other parameter evaluated to null it was treated as false. All parameters to the AND function, including the first one, are now treated as false if they evaluate as null.
DEV-16948 - Resolved an issue where sort order directions were not being applied on pipes configured with aggregating attributes. Sort-order directions are now correctly applied.
DEV-16949 - Fixed regression with displaying legacy Form Views.
DEV-17000 - Fixed error when opening a view with a relationship to a table with invalid data.
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 were set to 0.
DEV-17063 - Fixed the cause of the 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-17076 - Filters can now be applied to relational aggregate views.
DEV-17086 - Form fields backed by Table Attributes now correctly have the Aggregate Function and Filter options available in their properties.
DEV-17104 - Improved support for language translation of the main PhixFlow interface.
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-17133 - HTTP Collector and Exporter timeouts can now be specified on the HTTP Datasource. This value will override the default connection timeout, request timeout and socket timeout set in server.properties. The non-working timeout settings on the HTTP Collector and HTTP Exporter have been removed.
DEV-17134 - Table filters are now shown in the filter dropdown on the properties for relational fields.
DEV-17211 - Formatting and Actionflow nodes now all support autocomplete in expression editors.
DEV-17225 - Changed filter expression fields to use a new expression editor, allowing autocomplete of fields and functions. These fields are now highlighted by a green border.
DEV-17298 - PhixFlow now correctly supports special characters in translation files.
ERD
DEV-16075 - Table attributes that are flagged as 'Foreign Key' are now automatically considered to be 'Indexed'.
DEV-16186 - Setting Return All Attributes no longer causes an error for Tables with Local attributes.
DEV-16256 - ERD connectors are now correctly directed.
DEV-16694 - Resolved issue where connectors on ERDs would sometimes appear to point into empty space.
Performance
DEV-16380 - Improved performance of opening / refreshing Screens.
DEV-16423 - Improved performance of opening Screen properties.
DEV-16498 - Reduced PhixFlow memory usage at an overall architectural level.
DEV-17089 - Changing user group membership will no longer have a performance impact on opening screens.
Screens
DEV-15395 - Double-clicking on a record is now disabled whilst the record is being autosaved.
DEV-15778 - Sort order attributes are now sorted by their display label.
DEV-15832 - When creating a screen within a package, the list of available templates is restricted to only show those in the package.
DEV-15956 - Resolved an issue where the Read-only setting was applied even when the apply read-only checkbox was unchecked.
DEV-16085 - Empty numeric form fields no longer incorrectly show as 0.
DEV-16236 - Resolved issue with Style attributes being wrongly inherited even when they were not enabled in the parent style.
DEV-16255 - Input Fields now correctly inherit the 'mandatory' flag from backing Table Attributes.
DEV-16267 - The On Click Event Handler on an area component now supports the option "Other". This allows action types like "screenshot" and "toggle maximise" to be set.
DEV-16268 - Driven Kanbans now display correct records after changing the driving selection.
DEV-16386 - Add the ability to define a 'Grid Row Hover Style' to apply when the mouse is over a row in a grid. This can be set at the system, application or individual grid level.
DEV-16387 - Fixed a problem with an error being displayed while editing a Screen containing Views with Table Action Menu Items.
DEV-16390 - Added the ability to define a 'Grid Alternate Row Style' to apply to 'even' rows in grids. This can be set at the system, application or individual grid level.
DEV-16391 - The Minimise button now appears on screen windows by default.
DEV-16459 - Moving fields backed by relational Table Attributes around a Screen now works correctly.
DEV-16496 - Expressions in Shared Styles are now correctly re-evaluated when a screen is resized.
DEV-16506 - Dropping Table Attributes onto Cards now works correctly.
DEV-16554 - Screen Elements with Background Filter Rules now save correctly.
DEV-16575 - Background Filter Rules now add correctly to Dropdown Fields backed by relational attributes. The 'Add Filter' button now adds correctly to Dropdown Fields backed by relational attributes.
DEV-16577 - Read-only settings are now reliably propagated to child components.
DEV-16728 - Fixed regression where the CSS property "Display: none" was being ignored, components are now correctly hidden when the CSS property is set.
DEV-16753 - Dragging Tabs now works correctly when adding/reordering Tabs.
DEV-16904 - Fixed Dropdowns now correctly display the current record's value, even if it is not one of the Dropdown's allowed values.
DEV-16914 - Screens now have an interactive floating menu that appears on components on mouseover. The new menu has been added to provide quick access to key tasks, including accessing styles, field validation and defining backing data. It is available on screens when unlocked in Design mode.
DEV-17022 - Editing Card Components and Views no longer displays a 'cannot cast to class' error for users without the VIEW_PRIVATE_CONFIG permission.
DEV-17074 - Preferred Parent Type in nested components are now correctly copied when creating new components.
DEV-17091 - Dropdown Fields backed by a foreign key now correctly update form records.
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-17172 - Fixed problem with Component Types duplicating when copying Layout Components from the palette.
DEV-17197 - A ticked style setting without a value now correctly overrides any inherited values using a default of 0. For instance, if margin or padding is ticked without any value this is equivalent to setting a value of 0.
DEV-17212 - Fixed problem with field labels being renamed when creating components from templates.
DEV-17252 - Having two table view components backed by the same table view on the same screen will no longer cause Actionflows to sometimes use incorrect records.
DEV-17272 - It is no longer permitted to change the screen configured on an Open Screen Action, instead create a new action.
DEV-15943 - Performance has been improved for opening lists of Actionflows throughout the product.
DEV-16097 - Fixed memory leak when lookups are used in Actionflows.
Workflow
None.
Release 10.0.12
Introduction
PhixFlow is pleased to announce the release of PhixFlow Version 10.0.12. This page describes the improvements and fixes in this version.
Installing or Upgrading to PhixFlow Version 10.0.12
To install a new PhixFlow instance:
- Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies.
- Please email support@phixflow.com if you are planning to run PhixFlow on an unsupported database version.
- Follow the instructions in Installing PhixFlow.
To upgrade an existing PhixFlow instance:
- 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.
- Please email support@phixflow.com if you are planning to run PhixFlow on an unsupported database version.
- Ensure you have a backup of the database before upgrading PhixFlow.
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
New settings have been added to the logback.xml.example file to enable logging of audit events to file. The applications logback.xml file should be updated with these new configuration sections.
If it is desired to terminate Phixflow if audit record writing fails for extended periods of time then the setting dbAuditService.haltOnDiscardCommitted should be set to true.
Schema Changes
Schema changes are required for this release.
New Features
Bug Fixes
- DEV-18000 - Fixed the import deleting sort order attributes when the table and the sort order are held in different applications or packages.
- DEV-18028 - In the properties of a Table View, a fix has been applied to the "allow export to Excel and CSV" option which stops PhixFlow from erroring when this feature is used.
- DEV-18056 - An optional configuration setting (dbAuditService.haltOnDiscardCommitted) has been added, which when set will terminate Phixflow if audit records are unable to be written to the database after extended periods of retrying (24 hours, configurable by setting dbAuditService.retryForMs).
- DEV-18107 - Audit records are now also recorded in a separate audit.log file as they are being generated. This guarantees their availability even if the application is restarted before they can be written to the database.
- DEV-18117 - On startup the audit log files are reread and audit event that was not successfully persisted will be replayed into the database.
- DEV-18266 - Resolved failure on SQL Server to load application translation maps.
Release 10.0.11
Introduction
PhixFlow is pleased to announce the release of PhixFlow Version 10.0.11. This page describes the improvements and fixes in this version.
Installing or Upgrading to PhixFlow Version 10.0.11
To install a new PhixFlow instance:
- Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies.
- Please email support@phixflow.com if you are planning to run PhixFlow on an unsupported database version.
- Follow the instructions in Installing PhixFlow.
To upgrade an existing PhixFlow instance:
- 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.
- Please email support@phixflow.com if you are planning to run PhixFlow on an unsupported database version.
- Ensure you have a backup of the database before upgrading PhixFlow.
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
No Schema changes are required for this release.
New Features
Bug Fixes
DEV-16782 - The following alterations have been made to items in the Serene Grey template package:
The minimum width of Tiles has been increased from 130px to 260px. This still supports viewing on mobile devices. The content which overflows outside of a tile is also now hidden so it does not exceed the borders of the tile.
Horizontal and Vertically expanding tiles have been reworked to simplify the CSS used to achieve this mechanism. The Chevron direction has also been changed to better indicate the direction of expansion.
There is a new Concertina Tile that provides a number of expanding areas in a single tile space.
Tab headers text has been set up so the text which is too long to fully display will have ellipses added to the end. For example: "PhixFlow Inv..."
The UID form field template has been removed from all card containers.
The labels on form fields have been moved left to better align with the input fields.
- DEV-17172 - Fixed the problem with Component Types duplicating when copying Layout Components from the palette.
- DEV-17212 - Fixed the problem with field labels being renamed when creating components from a template.
- DEV-17471 - Suspended jobs in the System Console are now flagged highlighted in blue as they were in previous releases.
- DEV-17521 - Fixed the problem with resizing relational grid columns which caused reopening the screen to display an error.
- DEV-17990 - Improvements have been applied to ensure that audit entries are maintained.
Release 10.0.10
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:
- Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies.
- Please email support@phixflow.com if you are planning to run PhixFlow on an unsupported database version.
- Follow the instructions in Installing PhixFlow.
To upgrade an existing PhixFlow instance:
- 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.
- Please email support@phixflow.com if you are planning to run PhixFlow on an unsupported database version.
- Ensure you have a backup of the database before upgrading PhixFlow.
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 permission.
DEV-15395 - Double clicking on a record is now disabled whilst the record is being autosaved.
Release 10.0.9
Introduction
PhixFlow is pleased to announce the release of PhixFlow Version 10.0.9. This page describes the improvements and fixes in this version.
Installing or Upgrading to PhixFlow Version 10.0.9
To install a new PhixFlow instance:
- Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies.
- Please email support@phixflow.com if you are planning to run PhixFlow on an unsupported database version.
- Follow the instructions in Installing PhixFlow.
To upgrade an existing PhixFlow instance:
- 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.
- Please email support@phixflow.com if you are planning to run PhixFlow on an unsupported database version.
- Ensure you have a backup of the database before upgrading PhixFlow.
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.
Bug Fixes
- DEV-16861 - Filtering Default Components dropdowns now work correctly for System Configuration settings
- DEV-16904 - Fixed Drop Downs now correctly display current record's value even if it's not one of the Drop Down's allowed value
DEV-16949 - Fixed regression with displaying legacy Form Views.
- DEV-17000 - Fixed error when opening a view with a relationship to a table with invalid data.
- DEV-17021 - Fixed error triggered after editing custom logfile filters
Release 10.0.8
Introduction
PhixFlow is pleased to announce the release of PhixFlow Version 10.0.8. This page describes the improvements and fixes in this version.
Installing or Upgrading to PhixFlow Version 10.0.8
To install a new PhixFlow instance:
- Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies.
- Please email support@phixflow.com if you are planning to run PhixFlow on an unsupported database version.
- Follow the instructions in Installing PhixFlow.
To upgrade an existing PhixFlow instance:
- 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.
- Please email support@phixflow.com if you are planning to run PhixFlow on an unsupported database version.
- Ensure you have a backup of the database before upgrading PhixFlow.
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
Special Upgrade Instructions
DEV-16844
Selecting a new value in a drop down now automatically trigger data refresh on any data-bound components (Grids, Cards). Existing apps should be reviewed for any exceptional cases where this behaviour is not wanted. If so the "Do Not Trigger Automatic Data Refresh" option in the advances section of the drop down field should be set to prevent the behaviour.
Schema Changes
Schema changes are required for this release.
Improvements and New Features
- DEV-16844 - There is a new option for DropDown Fields: Do Not Trigger Automatic Data Refresh in the advanced section. Ticking it stops any data-bound components (Grids, Cards) driven by the DropDown from automatically refreshing when the value in the DropDown changes.
Bug Fixes
- DEV-15036 - Changing field template now correctly uses the existing label
- DEV-16694 - Resolved issue where connectors on ERDs would sometimes appear to point into empty space.
- DEV-16753 - Dragging Tabs now works correctly when adding / reordering Tabs.
Release 10.0.7
Introduction
PhixFlow is pleased to announce the release of PhixFlow Version 10.0.7. This page describes the improvements and fixes in this version.
Installing or Upgrading to PhixFlow Version 10.0.7
To install a new PhixFlow instance:
- Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies.
- Please email support@phixflow.com if you are planning to run PhixFlow on an unsupported database version.
- Follow the instructions in Installing PhixFlow.
To upgrade an existing PhixFlow instance:
- 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.
- Please email support@phixflow.com if you are planning to run PhixFlow on an unsupported database version.
- Ensure you have a backup of the database before upgrading PhixFlow.
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
DEV-16814:
If upgrading from a previous 10.0 version the upgrade tool should be rerun with the -filters command line option. E.g.:
> java -jar upgrader.jar --url=<url> --user=<user> --pass=<password> -filters
or
> java -jar upgrader.jar --path=<path to phixflow-datasource.xml> -filters
Schema Changes
Schema changes are not required for this release.
Improvements and New Features
- None
Bug Fixes
- DEV-16154 - Exporting Audit Records to Excel now works correctly
- DEV-16673 - Setting the locale when creating a user no longer errors.
- DEV-16685 - Pie charts now export correctly.
- DEV-16814 - Resolved issues with background filters on the root dashboard element not displaying or saving correctly.
Release 10.0.6
Introduction
PhixFlow is pleased to announce the release of PhixFlow Version 10.0.6. This page describes the improvements and fixes in this version.
Installing or Upgrading to PhixFlow Version 10.0.6
To install a new PhixFlow instance:
- Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies.
- Please email support@phixflow.com if you are planning to run PhixFlow on an unsupported database version.
- Follow the instructions in Installing PhixFlow.
To upgrade an existing PhixFlow instance:
- 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.
- Please email support@phixflow.com if you are planning to run PhixFlow on an unsupported database version.
- Ensure you have a backup of the database before upgrading PhixFlow.
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
Special Upgrade Instructions
Grid/Table Styling Changes
In version 8 grid rows had alternating colours by default (white/grey). This is no longer the default since version 9. To enable alternating colours the 'Grid Row Style' and 'Grid Alternate Row Style' can be set, see Restoring Grid/Table Styling from 8.3 below.
In version 8 grid cells had borders by default. This is no longer the default since version 9. Cell borders can be created by setting the top border in 'Row Styles' and a right border on 'Column Styles', see Restoring Grid/Table Styling from 8.3 below..
In version 8 grid rows were highlighted in green when the mouse hovered over them. This is no longer the default since version 9. This can be restored by setting the background colour of the 'Grid Row Hover Style', see Restoring Grid/Table Styling from 8.3 below..
All styles are listed below.
Restoring Grid/Table Styling from 8.3
If you wish to restore the grid styling from PhixFlow Version 8.3, the following Styles can be updated in Administration → System → Configuration → Styles Tab → Style Settings, .add these styles to the Style's CSS Properties:
Grid Row Style:
height: 18px
borderRight: 1px solid #d3d3d3
Grid Alternate Row Style:
background-color: #e6e6e6
Row Selection Style:
background-color: #07e51c
Grid Row Hover Style:
background-color: #22FF37
Styling Review
Previously style attributes were wrongly being inherited even when they were not enabled in the parent style. This has been fixed. Applications should be checked to ensure their styling is still correct and that they weren't relying on the previously broken behaviour.
Read only Review
The Read only setting is now reliably inherited by child components, from their parent component. Behaviour of existing applications should be checked in case previous misconfigurations are now being applied. Any issues can be resolved by explicitly setting the read only option on the child components to override those inherited from the parent components settings
Schema Changes
Schema changes are not required for this release.
Improvements and New Features
N/A
Bug Fixes
DEV-16294 - For views, in app mode, it will now only show the filters listed on the view in the section App Mode Filters. If you create the filter on the view grid itself, then it will be visible in app mode in the filter picker but if it is created elsewhere then it will not be available in app mode by default.
- DEV-16575 - Background Filter Rules are now applied correctly to DropDown Fields backed by relational attributes. The 'Add Filter' button now correctly add to the DropDown Fields backed by relational attributes.
- DEV-16577 - Read only settings are now reliably propagated to child components.
DEV-16638 - Actionflows will now ignore incomplete record sets except those created in the same actionflow.
- DEV-16656 - Default Application and Default Screen have been removed from User Configuration as they were not functional. Startup actions can be used to control which screen(s) an application initially displays for a user.
- DEV-16658 - Deleting an Action Task from a task plan will now correctly delete the associated instance(s) of the actionflow.
- DEV-16732 - Fixed regression where items were no longer being selected in a driven grid after a selection was made.
- DEV-16712 - Embedded actionflows will always run their first phase regardless of the phase they are embedded within. It is not valid for the embedded actionflow to trigger other phases.
- DEV-16728 - Fixed regression where the css property "Display: none" was being ignored. Components are now correctly hidden when this css property is set.
Release 10.0.5
Introduction
PhixFlow is pleased to announce the release of PhixFlow Version 10.0.5. This page describes the improvements and fixes in this version.
Installing or Upgrading to PhixFlow Version 10.0.5
To install a new PhixFlow instance:
- Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies.
- Please email support@phixflow.com if you are planning to run PhixFlow on an unsupported database version.
- Follow the instructions in Installing PhixFlow.
To upgrade an existing PhixFlow instance:
- 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.
- Please email support@phixflow.com if you are planning to run PhixFlow on an unsupported database version.
- Ensure you have a backup of the database before upgrading PhixFlow.
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
Special Upgrade Instructions
Grid/Table Styling Changes
In version 8 grid rows had alternating colours by default (white/grey). This is no longer the default since version 9. To enable alternating colours the 'Grid Row Style' and 'Grid Alternate Row Style' can be set, see Restoring Grid/Table Styling from 8.3 below.
In version 8 grid cells had borders by default. This is no longer the default since version 9. Cell borders can be created by setting the top border in 'Row Styles' and a right border on 'Column Styles', see Restoring Grid/Table Styling from 8.3 below..
In version 8 grid rows were highlighted in green when the mouse hovered over them. This is no longer the default since version 9. This can be restored by setting the background colour of the 'Grid Row Hover Style', see Restoring Grid/Table Styling from 8.3 below..
All styles are listed below.
Restoring Grid/Table Styling from 8.3
If you wish to restore the grid styling from PhixFlow Version 8.3, the following Styles can be updated in Administration → System → Configuration → Styles Tab → Style Settings, .add these styles to the Style's CSS Properties:
Grid Row Style:
height: 18px
borderRight: 1px solid #d3d3d3
Grid Alternate Row Style:
background-color: #e6e6e6
Row Selection Style:
background-color: #07e51c
Grid Row Hover Style:
background-color: #22FF37
Styling Review
Previously style attributes were wrongly being inherited even when they were not enabled in the parent style. This has been fixed. Applications should be checked to ensure their styling is still correct and that they weren't relying on the previously broken behaviour.
Schema Changes
Schema changes are required for this release.
Improvements and New Features
- DEV-16283 - Improved relationship names on the available attribute selector.
- DEV-16284 - Views with two aggregations to the same table now display correct result
- DEV-16386 - Add ability to define a 'Grid Row Hover Style' to apply when the mouse is over a row in a grid. This can be set at the system, application or individual grid level.
- DEV-16390 - Add ability to define a 'Grid Alternate Row Style' to apply to 'even' rows in grids. This can be set at the system, application or individual grid level
Bug Fixes
- DEV-16236 - Style attributes were wrongly being inherited even when they were not enabled in the parent style.
- DEV-16255 - Input Fields now correctly inherit the 'mandatory' flag from backing Table Attributes
- DEV-16287 - Fixed problem with an error being displayed while editing a Screen containing StreamViews with TableAction Menu Items
- DEV-16506 - Dropping Table Attributes onto Cards now works correctly
- DEV-16524 - Fixed migration script not running properly for oracle databases with data in the font_size column for style
- DEV-16554 - Screen Elements with Background Filter Rules now save correctly.
Release 10.0.4
Introduction
PhixFlow is pleased to announce the release of PhixFlow Version 10.0.4. This page describes the improvements and fixes in this version.
Installing or Upgrading to PhixFlow Version 10.0.4
To install a new PhixFlow instance:
- Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies.
- Please email support@phixflow.com if you are planning to run PhixFlow on an unsupported database version.
- Follow the instructions in Installing PhixFlow.
To upgrade an existing PhixFlow instance:
- 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.
- Please email support@phixflow.com if you are planning to run PhixFlow on an unsupported database version.
- Ensure you have a backup of the database before upgrading PhixFlow.
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
Schema changes are required for this release. Also see special installation instruction above.
Improvements and New Features
- DEV-14575- The PhixScript hash function will now handle secret values. A new expandSecrets(value) function has been added, this takes a single string parameter and will expand any secret tokens into their values.
DEV-15778 - Sort order attributes are now sorted by their display label
- DEV-16403 - Added new geometric functions:
- geoUnion which computes a Geometry representing the point-set which is contained in two provided geometries.
- geoGetNum which returns the number of Geometries in a GeometryCollection or Multipolygon
- DEV-16423 - Improved performance of opening a Screen Editor
Bug Fixes
- DEV-16344 - Fixed missing error messages in import.
- DEV-16400 - Fixed error refreshing data on aggregate view with missing attributes
- DEV-16391 - Minimize button now appears on screens windows by default.
Release 10.0.3
Introduction
PhixFlow is pleased to announce the release of PhixFlow Version 10.0.3. This page describes the improvements and fixes in this version.
Installing or Upgrading to PhixFlow Version 10.0.3
To install a new PhixFlow instance:
- Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies.
- Please email support@phixflow.com if you are planning to run PhixFlow on an unsupported database version.
- Follow the instructions in Installing PhixFlow.
To upgrade an existing PhixFlow instance:
- 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.
- Please email support@phixflow.com if you are planning to run PhixFlow on an unsupported database version.
- Ensure you have a backup of the database before upgrading PhixFlow.
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
Schema changes are required for this release. Also see special installation instruction above.
Improvements and New Features
Bug Fixes
DEV-16248 - Deleting mappings to or from save actions will no longer sometimes fail
DEV-16268 - Driven Kanbans now display correct records after changing the driving selection
DEV-16307 - Fixed not being able to connect some action nodes directly to the Actionflow output connection points
DEV-16316 - Resolved a problem with moving and deleting components accidentally put directly into Card Components
DEV-16330 - mail Actions will no longer error when connected from a save action
Release 10.0.2
Introduction
PhixFlow is pleased to announce the release of PhixFlow Version 10.0.2. This page describes the improvements and fixes in this version.
Installing or Upgrading to PhixFlow Version 10.0.2
To install a new PhixFlow instance:
- Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies.
- Please email support@phixflow.com if you are planning to run PhixFlow 10.0.2 on an unsupported database version.
- Follow the instructions in Installing PhixFlow.
To upgrade an existing PhixFlow instance:
- 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.
- Please email support@phixflow.com if you are planning to run PhixFlow 10.0.2 on an unsupported database version.
- Ensure you have a backup of the database before upgrading PhixFlow.
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
Schema changes are not required for this release. Also see special installation instruction above.
Improvements and New Features
DEV-9335 - Improvements have been made to simplify how components are added to the screen or in the layers component.
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-16229 - Improved performance of opening the Mapping Configuration screen for Action Flows.
Bug Fixes
DEV-16117 - Fixed: "Publish All" sometimes failed, requiring server restart to resolve.
DEV-16186 - Setting Return All Attributes no longer causes an error for Tables with Local attributes.
DEV-16256 - ERD Connectors are now correctly directed.
DEV-16085 - Empty numeric form fields no longer incorrectly show as 0.
Release 10.0.1
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/
Installing or Upgrading to PhixFlow Version 10.0.1
To install a new PhixFlow instance:
- Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies.
- Please email support@phixflow.com if you are planning to run PhixFlow 10.0.0 on an unsupported database version.
- Follow the instructions in Installing PhixFlow.
To upgrade an existing PhixFlow instance:
- 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.
- Please email support@phixflow.com if you are planning to run PhixFlow 10.0.1 on an unsupported database version.
- Ensure you have a backup of the database before upgrading PhixFlow.
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
Schema changes are required for this release. Also see special installation instruction above.
Improvements and New Features
DEV-9335 - Improvements have been made to simplify how components are added to the screen or in the layers component.
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 messages.
Release 10.0.0
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/
Installing or Upgrading to PhixFlow Version 10.0.0
To install a new PhixFlow instance:
- Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies.
- Please email support@phixflow.com if you are planning to run PhixFlow 10.0.0 on an unsupported database version.
- Follow the instructions in Installing PhixFlow.
To upgrade an existing PhixFlow instance:
- 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.
- Please email support@phixflow.com if you are planning to run PhixFlow 10.0.0 on an unsupported database version.
- Ensure you have a backup of the database before upgrading PhixFlow.
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
Upgrading Step 8: Special Upgrade Instructions
Create new PhixFlow configuration files
You must create a new version of the following configuration file in your <tomcat>/webapps/phixflow/WEB-INF/classes
directory:
phixflow-instance.xml
To do this:
Rename your existing configuration file, for example by adding a
.bak
suffix.Follow the Install the PhixFlow Webapp instructions for creating a new file from the "
.example"
files provided.Copy the individual values from your existing configuration files and paste them into the new files.
Avoid copying entire XML blocks into your new configuration files, as you may overwrite a section of the configuration file that PhixFlow requires.
Database Upgrader
Run the upgrader from the command line once you have run the migration scripts and taken a suitable backup of your PhixFlow Database:
- Open the command line tool as an administrator.
- Within the Version 10 installation directory navigate to the directory holding upgrader.jar.
- For example,
\desktop\PhixFlow10\install\bin
- For example,
- Run the following command:
java -jar upgrader.jar --upgrade --path=<tomcat>\webapps\phixflow\WEB-INF\classes
- Where <tomcat> is the location where tomcat is installed.
JWT Token for API Authentication (Optional)
PhixFlow Version 10 supports incoming API access, this can be either anonymous or authenticated. To use Authentication for an API coming into PhixFlow, a signing key is used to generate the PhixFlow API key and this is stored on the server to ensure secure access.
Using the page Configure a Keystore and Aliases, configure phixflow-api-key to be used as the signing key for PhixFlow API Keys in the same way as pepperKey is configured. This secret string must be a minimum of 32 bytes length. Full API details can be found on PhixFlow Incoming API.
Application Template Package (Optional)
To be able to use the new features in Version 10 it is recommended that you install the Serene Grey Template Package. See Installing Template Packages.
Schema Changes
Significant Schema changes are required for this release. Also see special installation instruction above.
Discontinued Features
The following are now deprecated/out of support:
DEV-3862 - 3D Pie Charts and 3D Bar Graphs have been deprecated. It is recommended that users switch to the Pie Chart and Bar Graph using the same setup.
Changes to Privileges
New Privileges
UseApiKey - is a new privilege that enables a user to generate an encrypted JWT token which is used to authenticate the user within a PhixFlow Web Hook (API into PhixFlow).
Privilege Changes
DEV-15283 - System Console is no longer visible for users without the required 'View System Console' permission.
A number of privilege changes were introduced in Version 9, if you have migrated from a Version 8 release it is recommended that you review the Changes to Privileges section of this page: Release 9.0.0
Improvements and New Features
Performance
DEV-15281 - Import performance has been improved. Configuration import, and related copy functions now create audit records in the background so these records may continue to be created after the import has been completed.
Common Features
DEV-8521 - It is now possible to filter on the action summary column of audit summary and audit detail grids.
DEV-12984 - It is now possible to export from the audit summary tab.
DEV-13005 - StreamItemId and supercededDtm is now added to default views.
DEV-13267 - Two new functions have been added to support base64: base64Encode(string, [format]) and base64Decode[string, [format]).
DEV-13348 - Tab headers are no longer displayed for the 4 key areas of PhixFlow as they can be directly accessible via the header menu.
DEV-13553 - Added "Max Duration" to task plan under "advanced". value must be blank or a positive integer. When a value is entered the task plan will be automatically cancelled after running for a number of minutes equal to the max duration. Added "Earliest start" and "Latest end" to task plan under "advanced". value must be in the format hh:mm e.g. 06:30. If one is set then the other must be set as well. When both are set the task plan can only be run after the start time and will end automatically at the end time if still running.
DEV-13926 - Support for namespaces added to the XMLtoItems attribute function.
DEV-14525 - Enhancement to allow a single Task Plan to contain both analysis and rollback tasks. This supports the scenario where a rollback is required before an analysis is executed.
DEV-15042 - Task Plans can now contain a mix of Actionflow tasks and other tasks.
DEV-15243 - Macros now have access to _out, _inputMultiplier and _outputMultiplier.
Administration
DEV-13398 - External User Group Mapping Prefix field was added into the System Configuration. This changes the {mappingValue} variable with user group name if the user enters {mappingValue} variable to the External Login Groups field in the User Group.
DEV-13916 - The installer now includes options to report and repair data integrity issues in the PhixFlow configuration data. The installer now prompts for missing password and for confirmation before overwriting existing data.
Applications
None
ERD
DEV-15664 - It is now possible in ERD diagrams to select multiple tables using ctrl.
Workflow
None
Screens
DEV-9923 - Users can now add a style directly from the editor for a grid attribute.DEV-13840 - It is now possible to set View Attributes to display grid cells as HTML.
DEV-13989 - Configuration selection drop downs have been updated to now indicate the container (application or package) for each entry. E.g. when selecting Styles, Tables, etc you can now identify different items with the same name by the container they are in.
DEV-14482 - There is a new 'Copy selected records to the clipboard' right-click option for grids which allows users to copy data and paste it into Microsoft Excel.
DEV-14503 - Form Field Templates can now contain multiple input fields with different names.
DEV-14684 - Pressing the enter key when typing in a single-line string field on a screen will trigger the OnChange and form data change events. An example use case for this change is the ability to type in a search field and press enter which will cause the search criteria to apply to a filter and refresh the screen.
DEV-15052 - With the new relation view changes it is no longer necessary for Card Containers to have a View to present data. Existing Card Containers will maintain their views until they are removed and new Card Containers no longer support views.
DEV-15893 - Quick filters on grids in property editors are not case sensitive by default.
Actionflows
DEV-12943 - Save actions and View actions now pass through all attributes of the input record.
DEV-13524 - Gateway nodes now have a glyph to indicate if the gateway is inclusive or exclusive.
DEV-14286 - Actionflows are now included as an entry on the homepage and main menu bar.
DEV-14291 - Added "use raw url" to HTTP collectors and HTTP exporters. When ticked the URL will not have any escaped characters decoded, the URL is used in its raw form.
DEV-14784 - Added the ability to create a new Screen on the Open Screen action creation window.
Analysis Models
DEV-8554 - The "Email From" field on file exporters now allows expressions.
DEV-8810 - Added "Default Datasource Instance" to datasource, this will be used for the "find tables" option if there is more than one instance.
DEV-12051 - It is now possible to mark a pipe in an analysis model as an 'action' pipe. A new view option allows showing all pipes, only action pipes or analysis view (non-action pipes).
DEV-12986 - Users can now create a screen directly from a table in an analysis model by selecting 'Create Screen' when right clicking on a table.
DEV-13368 - Users can now view the database table name and database column name for tables and table attributes in their respective repository detail views.
Bug Fixes
Performance
DEV-14346 - Improved performance where lists of tables are loaded in the GUI.
Common Features
DEV-11508 - Fixed issue whereby deleting a View, View Action or Component used to leave some internal configuration data behind.
DEV-12221 - Improved display of audit summaries for pipes to include more context and have an improved layout.
DEV-14646 - You can now refer to pipe names as the default value of a switch statement.
DEV-14661 - It is now possible to add Validation Types to Configuration Export Tasks.
DEV-14727 - Dragging a task from one task pane to another is now supported.
DEV-14824 - Table Actions and Tables are now ordered alphabetically in the repository.
DEV-14900 - Actionflows will now no longer occasionally show as "Action" in the console log files.
DEV-14914 - Fixed incorrect type-conversion check on order-by fields.
DEV-14932 - Analysis tasks run from Actionflows will now include the name of the action in the log message.
DEV-15056 - Copying a Screen now also copies referenced Components.
DEV-15221 - Audit Summaries will no longer sometimes be marked as system instead of the user who made the change.
DEV-15475 - Resolved issue where exporting selected items from a filtered table wouldn't always work.
DEV-15669 - Selecting a record in the active tasks section of the system console will now show its messages in the lower grid.
DEV-15687 - Upgrade jQuery library to 3.7.0.
Administration
DEV-13050 - Where an object's visibility is controlled by a list of User Groups and an 'All Users can View' switch, the list of Groups is now cleared if 'All Users can View' is set to true. Prior to this change, the hidden list of User Groups could cause complications when exporting/importing. This change applies to Applications, Screens, Filters, Tables, Table Attributes, Views, View Order and Layout Components.
DEV-13827 - PhixFlow now supports displaying Unicode characters in users names.
Applications
DEV-14791 - Changing applications will no longer cause the "all users can view data" field to be set to an invalid value.
DEV-15722 - When copying or importing, user groups no longer maintain their associations with users that exist in the target instance.
ERD
None
Workflow
None
Screens
DEV-13160 - Rearranged the action tab of the button property editor so that mutually exclusive action types and action methods will no longer show together.
DEV-13171 - Fixed multiple issues related to changing fields templates.
DEV-14394 - Cards now correctly evaluate formatting rules and refresh after driving views change selection.
DEV-14406 - Improved performance of the screen creation process.
DEV-14647 - Fixed problem with views refreshing in an incorrect order.
DEV-14859 - Read-only flag now correctly applies to inner form components.
DEV-15207 - Outer area now correctly calculates Formatting Rules after upgrading its properties.
DEV-15704 - Driven components (cards, grids) are optimized not to refresh whilst screen is still loading.
DEV-15705 - Improved performance of dragging components when screen building.
DEV-15771 - Drop Downs now correctly apply Formatting Rules.
DEV-15850 - Dragging an item onto a form from the layers view will no longer create a copy and will now move the item.
DEV-15901 - Double clicking a button no longer incorrectly opens the same screen twice.
DEV-15923 - Fixed an error when creating a foreign key dropdown when the attribute type is decimal.
DEV-15948 - Selecting a value in a dropdown will cause any grids it drives to refresh.
Actionflows
DEV-12387 - Save Actions that are marked as "Insert" or "Auto insert / update" no longer need the primary key attribute to be mapped.
DEV-14176 - Calculate Action Attributes will now correctly record their audit detail.
DEV-14382 - Setting Cards as Drop Targets now works correctly for Action Flows.
DEV-14496 - Deleting the currently selected action phase will now default to selecting the first phase remaining.
DEV-14568 - Error messages evaluating expression for action attributes will now include the action name and the attribute name.
DEV-14585 - Confirmation buttons which are not wired to an output Action Phase will no longer cause the action spinner to stay perpetually.
DEV-14588 - Improved Action-flow error handling.
DEV-14595 - Toggling "Close parent screen" or "hide loading spinner" for an actionflow will no longer cause the input / output points to move.
DEV-14610 - You can no longer have two action connection points on the same action with the same name.
DEV-14688 - Actionflows will now correctly close the in progress spinner upon completion.
DEV-15066 - The parameters section of actionflow action editors has been renamed as Input Parameters and moved above the Output Attributes.
DEV-15285 - Fixed not being able to connect from some types of action nodes directly to the actionflow's output connection points.
DEV-15411 - Renamed "Returned Attributes" on action connection points to "Input Parameters".
DEV-15446 - Having two save actions on the same audited table will no longer cause the action to fail.
Analysis Models
DEV-13386 - Fixed analysis lookup pipes using an exact match index and group-by unticked failed with an internal error.
DEV-14567 - Expression related error messages will now include the expression's source.
DEV-14985 - Fixed multiple problems with Table Actions created from the Full Repository.
DEV-15051 - Fix invalid warnings of missing objects when importing configuration data.
DEV-15657 - Fixed problem with dragging items from the Repository when multiple Repository tabs are open.
DEV-15917 - Fixed issue where a lookup pipe in a Table Record Action returned the same results for all records updated; now the pipe filter conditions are correctly re-evaluated for each record updated. Note that the problem did not happen when an explicit lookup() function was used.