Introduction

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

Installing or Upgrading PhixFlow

To install a new PhixFlow instance:

1. Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies. 
   1. Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
2. Follow the instructions in Installing PhixFlow.

To upgrade an existing PhixFlow instance: 

1. PhixFlow must be at version 8.3.18 or later in order to be upgraded to this version. If this is not the case please first upgrade to 8.3.18.
2. Check System Requirements and Compatibility for changes to the system requirements or supported database versions. For example, you may need to upgrade your database or Java version.
   1. Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
3. Ensure you have a backup of the database before upgrading PhixFlow.

4. Follow the Upgrading PhixFlow steps. It is important to complete any Special Upgrade Instructions for all the intermediate releases between your current version and the version to which you are upgrading.

Bug Fixes

DEV-18519 - Resolved issues where rollback could restore incorrect records in rare circumstances when there are historic failed streamsets.

DEV-13113 - Audit summary descriptions no longer include the username, as this is already provided in the username column. Audits summary descriptions created from import changes are now prepended with "Import"

DEV-18463 - In API Endpoints for Actionflows, when a multipart form POST is received. form fields that are file uploads are now available to be mapped as input attributes to the Actionflow.

DEV-18514 - When a user changes their password, the time since last changed is now correctly reset.

Introduction

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

Installing or Upgrading PhixFlow

To install a new PhixFlow instance:

1. Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies. 
   1. Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
2. Follow the instructions in Installing PhixFlow.

To upgrade an existing PhixFlow instance: 

1. PhixFlow must be at version 8.3.18 or later in order to be upgraded to this version. If this is not the case please first upgrade to 8.3.18.
2. Check System Requirements and Compatibility for changes to the system requirements or supported database versions. For example, you may need to upgrade your database or Java version.
   1. Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
3. Ensure you have a backup of the database before upgrading PhixFlow.

4. Follow the Upgrading PhixFlow steps. It is important to complete any Special Upgrade Instructions for all the intermediate releases between your current version and the version to which you are upgrading.

Improvements and New Features

Actionflows

DEV-16201 - In Actionflows, an "Attachments" section has been added to Email actions. It contains a reference to a file table and a filter, when set it will use the filter to find all applicable files from that file table and include them as attachments on the sent email.

DEV-17379 - Added a new "Retry" section for HTTP actions. This section contains three fields pertaining to automatically reattempting the HTTP connection under certain conditions:

• • • "Retry Expression" is an expression that when it evaluates to "true", instead of the record continuing normally through the Actionflow it will instead attempt to retry the connection.
    • "Retry Interval Expression" is an expression that when it evaluates to an integer determines the amount of time between attempted requests.
    • "Max Attempts" is the maximum number of times the HTTP action will try the HTTP connection before continuing, this must be an integer between 1 and 60.

DEV-17451 - A minimum and maximum number of records can now be enforced on Lookup connection points.
Actionflows that receive too many or too few records will now display a user readable error instead of prompting the user to check the system console.

DEV-17509 - Added the ability to run HTTP actions directly to allow testing of the request.

DEV-17876 - Added support for the lookup() function when used in an Actionflow to perform a lookup (using a request connector).

DEV-18017 - Added a "URL Alias" field to the properties of API Endpoints. When set, instead of the URL being constructed using the Actionflow name and application name, it will use the alias instead. The URL field in the properties will update to reflect the alias set.

DEV-18018 - API Endpoint Input Connection Points now support custom input parameters to be added. These will automatically be mapped from the incoming request URL query parameters or form fields. E.g. If an input parameter called field is added, and the request URL is https://server/phixflow/api/1/action/App/Api/trigger?field=abc then the value "abc" will be populated in the Actionflow. If the query parameter is missing then the parameter will be marked as unavailable unless a default value has been configured for it. When creating the URLs with query parameters care should be taken to ensure that the values are appropriately URL encoded in order to prevent unexpected behaviour.

DEV-18045 - If an action phase runs and has no inputs it will now throw an error.

DEV-18047 - Within an Actionflow, the HTTP action now has a new "Parameters" section which can be used to transmit values within a URL. The values are automatically encoded into a format suitable for passing via a URL and they are added to the end of the URL the HTTP action is calling, with the format:

?param1Name=param1Value&param2Name=param2Value

DEV-18089 - In an Actionflow, when dragging a Gateway node or Actionflow node onto an existing connection between two nodes, if the target node (being connected to) has more than one input connection point a popup appears with the first connection point selected by default. This avoids a user always having to manually select the input connection before confirming.

DEV-18090 - In an Actionflow, creating a connector from a Gateway node will automatically open the corresponding output rule in the properties.

DEV-18139 - Added Email Endpoint actions. Email accounts can now be configured to trigger an email endpoint action when an email is received, rather than saving the email to be picked up by a file collector at a later date. In addition to this, a "Maximum fetch count" has been added to email accounts, which when set will process the emails received by the email account in batches of this number, if not set, default is 2000. Email accounts and Client Token Configurations can now be created in an application or package.

DEV-18164 - In an Actionflow, within a HTTP action, the "Test HTTP Action" window has been redesigned for improved usability into two mains tabs: "Request" and "Response", with existing fields consolidated across these new tabs.

DEV-18220 - Added a new object type "XML Schema Definition". It has the properties: name, namespace and body. The namespace field is used to identify this xml schema definition and the body is used to validate xml. In addition, a new type of action, "XML Validate", has been added to Actionflows. It has a reference to a root XML schema definition (XSD) and optional additional XSDs. When passed XML it will pass the record through its "out" connection point if it is valid, or if it fails validation an error attribute containing a message is passed out of the "error" connection point.

DEV-18279 - A new type of Actionflow has been added called Email Endpoints. Email Endpoints can have a file table configured on them to store email attachments. If this is set up then when an email is received any attachments on that email will be downloaded to that file table's directory and a record with the file details will be created.

DEV-18323 - Email Endpoints can now have additional attributes added to their "in" connection point. Values will be provided by setting an input connection point attribute with the matching name. Any '-' characters are removed from the name.

DEV-18336 - In Actionflows, a "reply to" option has been added to Email actions. When set, the email will have its replyTo option set to the value this field evaluates to.

Administration

DEV-13897 - The Database Driver File Directory can now be set in Administration --> System Configuration --> System Directories. Previously, this was set using a script run against the PhixFlow database. The change simplifies the database drivers installation process.

DEV-17553 - Tomcat 10.1 is now a supported webserver. Please refer to the updated configuration instructions of how to create and use the webapps-javaee folder for the installation and upgrade processes.

DEV-18185 - The responsiveness of the configuration Export popup window has been updated to improve the layout of the popup when enlarged, making it easier to see the details of the exported content.

DEV-18192 - Within the PhixFlow configuration file "local.properties" used as part of the system setup, trailing whitespaces are automatically omitted when the file is processed. This stops the errors previously seen when whitespaces were included.

DEV-18194 - The entry in the System Console for a rollback now includes the Task Plan name.

DEV-18195 - The help link for setting a Home Screen Message in the System Configuration is now correct.

Analysis

DEV-17478 - The database collector menu item 'Run query and display result' now pops out of the hamburger menu if there is enough space.

DEV-17797 - The date-time format yyyyMMddHHmmss is now supported in File Collectors. Date and date-time attributes can now be stored as numbers and strings in upload files.

DEV-18169 - PhixFlow can now connect to SFTP servers using an RSA private key, with optional passphrase support. New fields have been added to the connection settings to support this.

Application

DEV-12660 - When importing files, the password field is now shown on the initial window, improving user experience.

DEV-17300 - The instance name is now displayed in the browser tab before the user logs in.

DEV-17882 - A log message "Initial DTO rebuilding complete" is now printed during start-up to indicate that the start-up data load processes have completed.

DEV-18117 - On start-up, the audit log files are reread and audit events that were not successfully persisted will be replayed into the database.

Common Features.

DEV-13114 - The start and end times of Data and Configuration imports and exports are now included in the Audit Summary.

DEV-15542 - When creating filters the case-insensitive flag on table attributes has been changed to case-sensitive to improve readability.

DEV-16126 - Added new logfile retention settings to Task Plans and Actionflows. When set the log file for the Task Plan / Actionflow will be automatically deleted upon completion unless a message of sufficient importance was written. There are two options, one for user generated messages (from the error, debug, info etc functions in expressions) and one for system generated messages.

DEV-16592 - Improved iconography for Datasources designed to make it clearer in the Repository what they are (when headers are removed) and if they are disabled.

DEV-17178 - Filters can now be applied to aggregate attributes on the primary table of a view.

DEV-17569 - Datasources, HTTP Datasources and HTTP Configuration objects can control the number of processing requests permitted in a set time frame, they will now show the number of requests waiting to be sent in their properties.

DEV-17589 - Form values are now validated against the field's backing attributes types and maximum sizes.

DEV-18023 - JSON parsing in expressions will now ignore any name-value pair where the value is unavailable.

DEV-18044 - Added '=' to the list of supported functions for fast expressions (e.g. formatting rules) this allows $ variables to be assigned values and used for these expressions.

ERD

DEV-18281 - Added a new field "Secondary Key" to table attributes. Relations can be connected to Secondary key attributes as well as Primary key attributes. Secondary key relations do not have to be unique and multiple related records can be returned from the same source record.

Performance

DEV-18110 - The performance of drop-down menus has been improved on screens.

DEV-18118 - Improved GUI response times after updating a screen.

Screens

DEV-16803 - Components can now be copied on the same screen by control-dragging or right-clicking the component in the Layers.

DEV-17659 - Word Cloud is now supported as a type of chart that can be added to a Screen.

DEV-17669 - Line Charts now plot the line between data-points when some of the data is missing.

DEV-17803 - Dynamic Text Fields now support placeholder text, shown when no value has been mapped to the field and no default value is configured.

DEV-17832 - There is a new advanced option on Fixed Dropdowns, 'Do Not Trigger Automatic Data Refresh' which works similarly to the same flag on Configurable Dropdowns and Date Fields - it allows the user to decide if changing the value of the Dropdown should cause any Views filtered by the field to refresh.

DEV-17909 - When creating a screen, templates are now separated into the packages they originate from.

DEV-17932 - On a screen, when changing a layout component template, the hover-over text on template items now shows the name and package of the template, in addition to the description.

DEV-18280 - In Screen building, a new File Record Gallery component is now available. It allows the user to display and manage multiple files, grouped by the folderId attribute on a File Table.

Bug Fixes

Actionflows

DEV-11733 - Where an Actionflow returns an error() message, the parent screen will no longer close.

DEV-17707 - In Actionflows, changing the source of an Input Connection will now delete any existing mappings.

DEV-17823 - Actionflow nodes can now be moved between Composite Actionflows and API Endpoints.

DEV-17824 - Opening the properties for a Bulk Update action no longer displays a gateway error.

DEV-17825 - Using the Calculate action lookup wizard will now populate the filter field on the property editor when the new filter is saved.

DEV-17854 - Fixed actions not terminating properly when an error occurred in an Actionflow that was passed a large number of records directly into a loop.

DEV-17864 - Within an Actionflow, Pivot Row View attributes are now mappable, all other pivot role attributes will not appear in the list of available attributes when mapping.

DEV-17935 - Within Actionflows, a fix has been applied to the Calculate Action to always process records in the right order when "prioritise throughput over ordering" is not ticked.

DEV-17961 - Save action attributes will now show the name of the save action as their source when they are mapped as output attributes.

DEV-18031 - Actionflow API Endpoints now support being held in and run from packages as well as applications.

DEV-18034 - In an Actionflow, in the properties for the Email action, a fix has been applied so that when two Email action properties are open at the same time and both have HTML enabled for the Message field, the properties behave correctly.

DEV-18048 - On the Actionflow attribute mapping screen, attributes coming from other Actionflows will now have the name and icon of that actionflow as well as the name of the Actionflow output point.

DEV-18101 - Fixed the Actionflow mapping window not refreshing properly when connected to an input Lookup Connection Point.

DEV-18138 - In Actionflows, a fix has been applied to the saving of View actions when created by a Calculate Lookup wizard.

DEV-18150 - The mapping window on Actionflows now lines up the mapping lines for attributes that are mapped to multiple output attributes, when viewed full screen.

DEV-18166 - In Actionflows, the Bulk Delete action has been fixed to stop the error "attempting to add duplicate field to an item dictionary" from occurring.

DEV-18175 - In Actionflows, within the Run Action feature, values for Boolean (TrueFalse) attributes now use toggles instead of checkboxes to set the value.

DEV-18283 - Fixed Actionflow lookups not working when contained in forEach() loops.

DEV-18295 - In Actionflows, on tables configured to keep audit history, having two Save actions that modify the same record no longer duplicates it.

DEV-18314 - Fixed Actionflows with multiple Phases and no confirmation buttons failing with a null pointer exception in some circumstances.

DEV-18346 - Fixed "unknown field name" errors for Actionflows where the Actionflow contains multiple insert Save actions for the same table.

Administration

DEV-18184 - Fixed a publishing error caused by importing a table that previously existed and was deleted.

DEV-18319 - Resolved behaviour, introduced in PhixFlow V10.0, whereby deleting a table linked to an Analysis model could leave inconsistent configuration data in the database, and cause subsequent configuration edits to fail due to violation of database constraints.

DEV-18369 - In the System Console, when sorting is applied to grid columns no errors now occur.

DEV-18406 - Fixed issue whereby recorded Audit information, which records changes to individual object properties, were corrupted in cases where the values are not displayed to the user e.g. changes to user passwords.

Analysis

DEV-16293 - The File Collector in Analysis modelling now has improved error messaging to state which file there is an issue reading. For example, "Collector X has failed while reading a row in the file: {file name}".

DEV-16677 - Improved error message when JSON parsing fails within an HTTP Collector.

DEV-17712 - PhixFlow now supports reading BLOB columns from Database Collectors in to String values.

DEV-18004 - PhixFlow Datasources now support multiline secret keys.

DEV-18177 - In Analysis Models, emails with long subjects will now be included in processing.

DEV-18390 - In Analysis Models, resolved issues with Database Collectors unable to fetch from SQLServer database columns of type 'uniqueidentifier' when they have a null value.

Application

DEV-18266 - Resolved failure on SQL Server to load application translation maps.

Common Features

DEV-12961 - Sequences are no longer reset during import.

DEV-13809 - Improved audit when data retention settings are changed on a table.

DEV-16155 - Improved audit when adding attributes to funnel actions.

DEV-16938 - Improved auditing when adding or removing tables on a Task Plan.

DEV-17523 - Relational attributes can now be used on pivot views.

DEV-17613 - Adding and removing attributes from Views now correctly refreshes them.

DEV-17841 - PhixFlow now correctly recognizes Spreadsheet Tabs including illegal XML characters (whitespaces, brackets, etc).

DEV-18022 - Tables with Pipe Views will now show the list of attributes from the View in the autocomplete in their attribute expressions instead of the attributes from the input table.

DEV-18167 - Date conversion now supports a wider range of ISO style timestamps, including those with timezone information, such as '2024-08-19T00:00:00.000Z', '2012-01-31 18:01:30+10:00' and '20120131T080130Z'.

DEV-18190 - Fixed issues with hover popup not appearing on Analysis Models, Workflows, Actionflow and ERDs when zoomed out.

DEV-18425 - Filtering with a list starting with a null value, no longer causes an error.

DEV-18438 - In XML Actions, renamed the XML Namespace fields: Name to Prefix and Value to URI.

DEV-18460 - In Table Actions, _prompt forms now correctly send values set on Date and DateTime fields.

ERD

DEV-18320 - Fixed relation arrows on ERDs not always pointing to the correct foreign key attribute.

DEV-18420 - The display name field linked to the foreign key is no longer added to a form when a multi-hop relation is created.

Screens

DEV-16341 - On Screens, we have fixed the problem causing the error 'Could not refresh data' showing when refreshing multiple grids and forms in parallel.

DEV-17011 - On Screens, when setting the flex-direction or flex-flow using a CSS Property on an Area component, it now sets the 'display' property to 'flex'.

DEV-17619 - On Screens, we have fixed the problem with driven views getting out of sync if the driving selection changes while they are still refreshing.

DEV-17639 - Fixed multiple presentation issues with the Floating Components Menu on Screens and in the Layers.

DEV-17805 - On Screens, if the outermost area has a backing table and then becomes an inner area, the Table field will still be visible in the Properties for that area.

DEV-17845 - When configuring a screen, changing the Template used by a Drop-Down form field now works correctly.

DEV-17859 - Form Fields on a Screen backed by a Relational Attributes do not use the validation held against them on their table.

DEV-17913 - On Screens, the Layers now appears when editing a Menu.

DEV-17983 - Fixed problems with charts colours when adding Custom Series and restricted Custom Series names to be valid Attributes names.

DEV-18112 - Aggregation on dynamic text fields can now be filtered on. This was already possible for standard input fields.

DEV-18156 - Default Filters created through View and View Component properties now correctly display on the View's Filters list.

DEV-18165 - Fixed the problem with Screens getting stuck out of focus after opening a menu.

DEV-18168 - It is now possible to set a double-click action on a View Component that will override any default double-click action set on the View referenced by the View Component.

DEV-18170 - Warning toast messages are no longer displayed when mixing shorthand CSS properties. CSS Properties such as 'margin', 'padding' and 'border' are now normalised to ensure they are applied correctly across all style settings (for example, "padding 1 2 3 4" is normalized to "padding-top 1, padding-right 2, padding-bottom 3, padding-left 4").

DEV-18181 - Fixed confirmation buttons to ensure the selected Actionflow phase runs.

DEV-18183 - After adding an Actionflow to an Event Handler, screens no longer require reopening to get that action to run.

DEV-18301 - When creating screens, background image positions for component styles will now be normalised. Where a single Custom value is provided for the background position, the value will be used for both horizontal and vertical settings. Additionally the Custom fields will accept numbers without "px" at the end.

DEV-18307 - On Screens, grid column styles are now applied correctly when using date or date-time attributes.

DEV-18451 - Fixed hidden view components on screens sometimes causing other screens to not refresh.

Workflow

DEV-18299 - In Workflows, the Actionflow icons now display correctly.

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:

1. Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies. 
   1. Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
2. Follow the instructions in Installing PhixFlow.

To upgrade an existing PhixFlow instance: 

1. PhixFlow must be at version 8.3.18 or later in order to be upgraded to this version. If this is not the case please first upgrade to 8.3.18.
2. Check System Requirements and Compatibility for changes to the system requirements or supported database versions. For example, you may need to upgrade your database or Java version.
   1. Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
3. Ensure you have a backup of the database before upgrading PhixFlow.

4. Follow the Upgrading PhixFlow steps. It is important to complete any Special Upgrade Instructions for all the intermediate releases between your current version and the version to which you are upgrading.

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.

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:

1. Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies. 
   1. Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
2. Follow the instructions in Installing PhixFlow.

To upgrade an existing PhixFlow instance: 

1. PhixFlow must be at version 8.3.18 or later in order to be upgraded to this version. If this is not the case please first upgrade to 8.3.18.
2. Check System Requirements and Compatibility for changes to the system requirements or supported database versions. For example, you may need to upgrade your database or Java version.
   1. Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
3. Ensure you have a backup of the database before upgrading PhixFlow.

4. Follow the Upgrading PhixFlow steps. It is important to complete any Special Upgrade Instructions for all the intermediate releases between your current version and the version to which you are upgrading.

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.

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:

1. Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies. 
   1. Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
2. Follow the instructions in Installing PhixFlow.

To upgrade an existing PhixFlow instance: 

1. PhixFlow must be at version 8.3.18 or later in order to be upgraded to this version. If this is not the case please first upgrade to 8.3.18.
2. Check System Requirements and Compatibility for changes to the system requirements or supported database versions. For example, you may need to upgrade your database or Java version.
   1. Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
3. Ensure you have a backup of the database before upgrading PhixFlow.

4. Follow the Upgrading PhixFlow steps. It is important to complete any Special Upgrade Instructions for all the intermediate releases between your current version and the version to which you are upgrading.

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.

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:

1. Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies. 
   1. Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
2. Follow the instructions in Installing PhixFlow.

To upgrade an existing PhixFlow instance: 

1. PhixFlow must be at version 8.3.18 or later in order to be upgraded to this version. If this is not the case please first upgrade to 8.3.18.
2. Check System Requirements and Compatibility for changes to the system requirements or supported database versions. For example, you may need to upgrade your database or Java version.
   1. Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
3. Ensure you have a backup of the database before upgrading PhixFlow.

4. Follow the Upgrading PhixFlow steps. It is important to complete any Special Upgrade Instructions for all the intermediate releases between your current version and the version to which you are upgrading.

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.

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:

1. Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies. 
   1. Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
2. Follow the instructions in Installing PhixFlow.

To upgrade an existing PhixFlow instance: 

1. PhixFlow must be at version 8.3.18 or later in order to be upgraded to this version. If this is not the case please first upgrade to 8.3.18.
2. Check System Requirements and Compatibility for changes to the system requirements or supported database versions. For example, you may need to upgrade your database or Java version.
   1. Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
3. Ensure you have a backup of the database before upgrading PhixFlow.

4. Follow the Upgrading PhixFlow steps. It is important to complete any Special Upgrade Instructions for all the intermediate releases between your current version and the version to 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:

1. Download: Serene_Grey.zip
2. 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.

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:

1. Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies. 
   1. Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
2. Follow the instructions in Installing PhixFlow.

To upgrade an existing PhixFlow instance: 

1. PhixFlow must be at version 8.3.18 or later in order to be upgraded to this version. If this is not the case please first upgrade to 8.3.18.
2. Check System Requirements and Compatibility for changes to the system requirements or supported database versions. For example, you may need to upgrade your database or Java version.
   1. Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
3. Ensure you have a backup of the database before upgrading PhixFlow.

4. Follow the Upgrading PhixFlow steps. It is important to complete any Special Upgrade Instructions for all the intermediate releases between your current version and the version to 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.

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:

1. Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies. 
   1. Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
2. Follow the instructions in Installing PhixFlow.

To upgrade an existing PhixFlow instance: 

1. PhixFlow must be at version 8.3.18 or later in order to be upgraded to this version. If this is not the case please first upgrade to 8.3.18.
2. Check System Requirements and Compatibility for changes to the system requirements or supported database versions. For example, you may need to upgrade your database or Java version.
   1. Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
3. Ensure you have a backup of the database before upgrading PhixFlow.

4. Follow the Upgrading PhixFlow steps. It is important to complete any Special Upgrade Instructions for all the intermediate releases between your current version and the version to 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

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.

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

Improvements and New Features

Minor patch release only containing bug fixes.

Bug Fixes

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:

1. Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies. 
   1. Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
2. Follow the instructions in Installing PhixFlow.

To upgrade an existing PhixFlow instance: 

1. PhixFlow must be at version 8.3.24 or later in order to be upgraded. If this is not the case please first upgrade to 8.3.24.
2. Check System Requirements and Compatibility for changes to the system requirements or supported database versions. For example, you may need to upgrade your database or Java version.
   1. Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
3. Ensure you have a backup of the database before upgrading PhixFlow.

4. Follow the Upgrading PhixFlow steps. It is important to complete any Special Upgrade Instructions for all the intermediate releases between your current version and the version to which you are upgrading.

Schema Changes

Improvements and New Features

None.

Bug Fixes

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

DEV-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”.

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

To install a new PhixFlow instance:

1. Check System Requirements and Compatibility for details of the PhixFlow system requirements and update any dependencies. 
   1. Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
2. Follow the instructions in Installing PhixFlow.

To upgrade an existing PhixFlow instance: 

1. Phixflow must be at version 8.3.24 or later in order to be upgraded. If this is not the case please first upgrade to 8.3.24.
2. Check System Requirements and Compatibility for changes to the system requirements or supported database versions. For example, you may need to upgrade your database or Java version.
   1. Please email support@phixflow.com if you are planning to run PhixFlow 11 on an unsupported database version.
3. Ensure you have a backup of the database before upgrading PhixFlow.

4. Follow the Upgrading PhixFlow steps. It is important to complete any Special Upgrade Instructions for all the intermediate releases between your current version and the version to which you are upgrading.

Schema Changes

Discontinued Features

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.

Introduction

The following are links to the PhixFlow release notes for all Version 10 product updates: 

Introduction

The following are links to the PhixFlow release notes for all Version 9 product updates: