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 7.9.0, 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:

To find information from previous release notes, see the Release help space, or search.

Release 9.0.5

Introduction

PhixFlow is pleased to announce the release of PhixFlow Version 9.0.5. This page describes the improvements and fixes in this version. This major release includes some important changes.

Installing or Upgrading to PhixFlow Version 9.0.5

To install a new PhixFlow instance:

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 9.0.5 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.
1. Please email support@phixflow.com if you are planning to run PhixFlow 9.0.5 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 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

None.

Schema Changes

PhixFlow requires product schema changes for this release.

Highlighted Bug Fixes

DEV-14369 - DatePickers now send the selected date regardless of the timezone.

DEV-14370 - 'Select first row by default' flag now correctly causes formatting rules to evaluate when a screen is loaded.

Improvements and New Features

DEV-13215 - You can no longer have two users with the same username.

DEV-13926 - Support for namespaces added to the XMLtoItems() attribute function.

DEV-14291 - Added the option "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.

Release 9.0.4

Introduction

PhixFlow is pleased to announce the release of PhixFlow Version 9.0.4. This page describes the improvements and fixes in this version. This major release includes some important changes.

Installing or Upgrading to PhixFlow Version 9.0.4

To install a new PhixFlow instance:

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 9.0.4 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.
1. Please email support@phixflow.com if you are planning to run PhixFlow 9.0.4 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.

Highlighted Bug Fixes

DEV-8521: It is now allowed to filter on the action summary column of audit summary and audit detail grids.

DEV-12817: Fixed occasional problem with selecting text not always working correctly.

DEV-13175: Improved error message from calculate action when an attribute is of the wrong type.

DEV-13609: Fixed performance regression test with cached lookups when compared against 8.3 cached lookups.

DEV-13645: Filters with the condition contains, starts with or ends with will now correctly match underscore and percent symbols.

DEV-13903:Actionflows on kanban card containers will now correctly update the kanban value and kanban display value when dropped on empty space

DEV-13967: Tooltips for html formatted view attributes will now be formatted correctly.

DEV-14083: PhixFlow no longer errors when a view uses 2 streams and the data range is set to Latest and the stream contains a local attribute

DEV-14242: Form fields on cards can now have a backing attribute set correctly from a property editor.

DEV-14245: Resolved regression preventing some users from changing their passwords.

Improvements and New Features

DEV-14220: New attribute functions have been added, refer to the help pages for full details:

- zipExtract(zipContents, filename, [charset) - extracts the file with the given name using the given charset

- zipListFiles(zipContents) - returns a list of filenames in the zipfile

- changeCharset(byteString [, charset]) - treats the input string as binary and attempts to convert it to the specified charset (autodetecting if none is specified).

Release 9.0.3

Introduction

PhixFlow is pleased to announce the release of PhixFlow Version 9.0.3. This page describes the improvements and fixes in this version. This major release includes some important changes.

Installing or Upgrading to PhixFlow Version 9.0.3

To install a new PhixFlow instance:

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 9.0.3 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.
1. Please email support@phixflow.com if you are planning to run PhixFlow 9.0.3 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.

Highlighted Bug Fixes

This release includes the following fix:

DEV-7873: Resolved an issue where you could get a Stack Overflow error if you called a macro with different numbers of parameters on a single stream or two streams running at the same time.

DEV-13909: File Collector and Http Collector sometimes failed to identify records to import based on XPath settings.

Sections on this page

Introduction
Installing or Upgrading to PhixFlow Version 9.0.3
Highlighted Bug Fixes

Release 9.0.2

Introduction

PhixFlow is pleased to announce the release of PhixFlow Version 9.0.2. This page describes the improvements and fixes in this version. This major release includes some important changes.

Installing or Upgrading to PhixFlow Version 9.0.2

To install a new PhixFlow instance:

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 9.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.
1. Please email support@phixflow.com if you are planning to run PhixFlow 9.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.

Special Upgrade Instructions

If you are upgrading from 9.0.0 please check that the migration script from 8.3.20 to 8.3.21 has been run. If it has been run there will be a column export_file_formats_enum in table stream_view. If this column does not exist you must run the 8.3.20 to 8.3.21 migration script before running the 9.0.0 to 9.0.1 migration script.

Improvements and New Features

DEV-9798: Users can now override the font size on a grid using grid row styles.

DEV-9923: Users can now add styles directly on the editor for grid attributes.

DEV-12898: Users can now access the list of templates using the screen toolbar.

DEV-13401: Font has now changed for all expressions to Roboto Mono.

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.

Highlighted Bug Fixes

This release includes the following fixes:

DEV-13234: Multiple connectors are now automatically curved on Workflow Models.

DEV-13288: Relational Drop Down fields will now have the drop down sorted alphabetically

DEV-13421: Dragging streamsets from the stream set grid to another stream will now correctly copy those stream sets over to the new stream.

DEV-13495: Object (buttons, event handlers, drop targets) are now hidden for users who don't have permission to run the assigned action.

Sections on this page

Introduction
Installing or Upgrading to PhixFlow Version 9.0.2
Improvements and New Features
Highlighted Bug Fixes

Release 9.0.1

Introduction

PhixFlow is pleased to announce the release of PhixFlow Version 9.0.1. This page describes the improvements and fixes in this version. This major release includes some important changes.

Installing or Upgrading to PhixFlow Version 9.0.1

To install a new PhixFlow instance:

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 9.0.1 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.
1. Please email support@phixflow.com if you are planning to run PhixFlow 9.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.

Special Upgrade Instructions

If you are upgrading from 9.0.0 please check that the migration script from 8.3.20 to 8.3.21 has been run. If it has been run there will be a column export_file_formats_enum in table stream_view. If this column does not exist you must run the 8.3.20 to 8.3.21 migration script before running the 9.0.0 to 9.0.1 migration script.

Improvements and New Features

DEV-13131: It is now possible to remove a backing table from a Kanban board.

DEV-13248: Component mappings are now known as Component Alias. The editor for this has been moved to the 'Advanced' section in the Screen, button, card component and view component editor properties.

DEV-13331: Previously extra escaping was required for backslashes in http collector bodies and other places. For instance to include the string "\n" in the output it would need to be escaped as "\\\\n".

For all new applications this extra level of escapes is no longer required and a single level of escaping the backslash is needed "\\n".

As this may have a detrimental impact on existing apps or packages a setting has been added "Back slashes must be escaped in expressions", For existing apps this will be set to true, for all new apps this defaults to false.

DEV-13348: Tab headers are no longer provided for the 4 key areas of PhixFlow. They will be directly accessible via the header menu.

DEV-13379: Actionflow mapping screens now allow Input Connection Point and Output Connection point lists to scroll independently.

DEV-13398: External User Group Mapping Prefix field was added into the System Configuration. This change the {mappingValue} variable with user group name if the user enters {mappingValue} variable to the External Login Groups field in the User Group.

DEV-13432: When looking at stream sets the action icons are no longer within the three dots menu and are instead on the menu bar.

DEV-13464:Updated the error message when attempting to create a form with no default form component set

DEV-13473:On Views users now have a 'custom' default data range option. If this is selected the user can enter a number of periods to use.

DEV-13494: A new getFields method has been added, this will return a list of the field/attribute names for Records. If assigned to a temporary variable these names can then be used in expressions using the syntax in.$fieldname.

Highlighted Bug Fixes

This release includes the following fixes:

DEV-11701: Actionflows can now be correctly moved between Packages and Applications.

DEV-12342: Task Plans no longer run invalid actionflow configurations.

DEV-13343: Corrections have been applied to the PhixFlow GUI to ensure reliable responsive behaviour on smaller monitors.

DEV-13347: The System Configuration settings for displaying the tabs button and whether tabs are displayed by default is only applicable to Application Mode.

DEV-13371: It is now not possible to create multiple connection point attributes with the same name.

DEV-13377: Improved import to allow repository objects to be imported when the package or application does not existin the target instance.

DEV-13438: New relationship connectors between tables in an ERD are now added to all ERDs containing the related tables..

DEV-13444: Workflows can now correctly display all actionflows including those nested in tabs components.

DEV-13487 Resolved issue in 9.0.0 where count would sometimes return the wrong result.

Sections on this page

Introduction
Installing or Upgrading to PhixFlow Version 9.0.1
Improvements and New Features
Highlighted Bug Fixes

Release 9.0.0

Introduction

PhixFlow is pleased to announce the release of PhixFlow Version 9. This page describes the improvements and fixes in this version. This major release includes some important changes.

Major New Features and Changes

Version 9 has introduced a host of exciting new features, full details of which can be found using the link below.

Several changes have been introduced as part of the Version 9.0 improvements, these will affect both PhixFlow Designers and PhixFlow Application users. Full details can be found using the link below.

Major New Features and Changes

Template Package

The new Serene Grey Template Package has been released as part of version 9.0.0. This includes an extensive set of templates for screen building with items grouped into logical collections within the palette. To find out more see: Template Packages.

Terminology Changes

The following terminology has been changed in PhixFlow to make the concepts easier to understand.

Previous Term	New Term
Dashboard	Screen
Stream	Table
Stream Attributes	Attributes
Stream Item	Record
Stream Set	Recordset
Stream View	View
Stream Action	Table-Action
Stream Item Action	Record-Action
Driver Class	Database Driver

In the system console, he initiator type will now be recorded as Table rather than Stream. This means if you are monitoring the logs for this value the system will require and update.

Installing or Upgrading to PhixFlow Version 9.0.0

To install a new PhixFlow instance:

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 9.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.
1. Please email support@phixflow.com if you are planning to run PhixFlow 9.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 new versions of the following configuration files in your ../webapp/WEB-INF/classes directory:
1. logback.xml
2. phixflow-datasource.xml
3. phixflow-instance.xml
4. phixflow-logging.xml
5. phixflow-login.xml
6. phixflow-secret.xml
To do this:
1. Rename your existing configuration files, for example by adding a .bak suffix.
2. Follow the Install the PhixFlow Webapp instructions for creating a new file from the ".example" files provided.
3. Copy the individual values from your existing configuration files and paste them into the new files.
  1. Avoid copying entire XML blocks into your new configuration files, as you may overwrite a section of the configuration file that PhixFlow requires.

Discontinued Features

The following are now deprecated/out of support:

DEV-10300 The option to open the small popout palette has been removed. This is due to extended palette functionality being present in the docked version of the palette.

Changes to Privileges

New Privileges

Users	Logging	Styles	Other
Add and Delete Users from a User Group	Enable System Logging	Create Style	Create Applications
Create Users	View System Logging Configuration	View Style	Download Unlimited Data
Modify Users	Modify System Logging Configuration	List Style	Edit configuration
Delete Users		Modify Style	Cancel Tasks
		Delete Style
Add these to administration roles	Add these to administration roles	Add these to application designer roles	Add these to application designer roles and administration roles

Privilege Changes

DEV-10126 The existing View System Console privilege provides access to the system console and to rolling back a task. However, you now need the new Cancel Tasks privilege to see the option for stopping a running task. During upgrade, the new Cancel Tasks privilege is automatically added to any user who already has the View System Console and Run Analysis privileges.

DEV-10262 The following items have been changed so their list privilege is now visible in the repository. Previously they were only shown if the user had the UserAdministration privilege.
- Email Account - New: Email Account LIST privilege
- Locales and Languages - Changed to existing Language LIST privilege.

During upgrade, the new EmailAccountList and LanguageList privileges are automatically added to any user who already has the UserAdministration privilege. External User Templates continue to use UserAdministration.

DEV-10901 Run Stream Actions has been renamed to Run Actions. Users require this privilege to run both Table actions (now called table-actions and record-actions) as well as the new actionflows.

DEV-11111 - Formatting Rules on screens now use the Style Privilege.

If you have created an application user role, make sure you update it with any privileges they need; see Controlling User Access to Applications

Improvements and New Features

Performance

DEV-7454 After a server restart, PhixFlow automatically re-caches frequently-used models and Screens in the background. This means the first user to access the model or Screen no longer experiences a delay as it is cached. The period over which PhixFlow tracks object usage is set in System Configuration Delete DTO Usage Records after Days.

Applications

DEV-7304 Palettes can now have grouped components, as illustrated below. To organise your palette components into groups, use the palette properties → Palette Groups options.

DEV-7313 For drop-down components in an application, when the user types into the drop-down list, PhixFlow automatically filters the possible options. The filtering-as-you-type has changed from being case-sensitive to case-insensitive.

DEV-7386 To provide more control when you want to divide a screen, the pop-up menu options:

Add Vertical Bar

Add Horizontal Bar

have been replaced with the options:

Add area above

Add area below

Add area on right

Add area on left

DEV-7487 For a locked screen in design mode, no toolbar is displayed. Right-click to either unlock or to see options to show information, such as properties and attributes.

DEV-7591 You can now add drop-targets to individual area components. There is also a new variable, _dropPosition, which provides co-ordinates of the dropped item relative to the component on which it is dropped; see _dropPosition for details.

DEV-7698 If there is an error when PhixFlow evaluates a CSS Property expression on a layout component, the error message now includes the component name.

DEV-7756 There is a new repository category, Layout Categories. You can configure areas to belong to a layout category then use it to set a Preferred Parent; see Component Categories and Preferred Parents. Where preferred parent areas have been configured, when you drag a component from the palette, PhixFlow will highlight the appropriate drop-areas on the screen.

DEV-7907 Grid view components now have a Basic Settings → Default Page Size to set how many records are displayed in the grid.

DEV-7976 Names of context parameters are preserved, with their actual names, when displayed on the show context parameters popup screen. Previously they were prettified by inserting spaces between capitalized words.

DEV-8048 You can now configure event handlers for some components. This means an application can run a table-action or actionflow when the user mouse-clicks or presses the Enter key.

You can configure the following events on data field components:

OnEnter: the user presses the Enter key in a data field.

OnBlur: the user mouse-clicks out of a data field. The event is triggered whether or not the field has changed.

OnChange: the user mouse-clicks out of a data field in which they have changed data. Notice that this event is not triggered by the user typing into a field.

You can configure the following events:

OnClick: the user mouse clicks in an area or grid views.

OnChange: any change to data in an area component.

DEV-8178 When dragging cards on a kanban board, PhixFlow displays the cards as you are moving them.

DEV-8273 In the Screen properties there are new Basic Settings options to specify a position and size for the screen. By default, new Screens are set to Position: Floating. Alternatively, you can pin a screen to one of the window edges and specify the size using Width and Height options. Use the Pinned options to create a permanently visible screen. This is useful for a navigation area or toolbar that you want to be visible for all other screens. Floating screens do not overlap with pinned screens. When the user maximises a Floating screen, it expands only to the remaining space.

DEV-8385 Scheduled, Suspended and Disabled task plans now have clearer icons.

DEV-8464 Layout Components with "On Click" event-handlers will now have a pointer cursor by default.

DEV-9180 The Internal Icon Source field on screen components now has the option to list existing images and add new images.

DEV-9361 For data views, the attribute properties now include a Grid Settings → Minimum Width option. When PhixFlow adjusts grid column widths to make use of available space, the attribute's column will not become narrower than the specified minimum width.

DEV-9364 You can now use formatting rules with different background images to create true/false field components that look different to the default ticked/unticked box; see Making a True-False Component.

DEV-9554 Use the new button component option → Actions tab → Action Type → Maximise/Minimise Screen to toggle whether or not a Screen is maximised; see Component. In a formatting rule, use the associated new _screen internal variable to match the button icon to the current maximised state of the Screen.

DEV-9605 Data views, form fields and card components can no longer have spaces in their names.

DEV-10395 The Style properties → Justify now has the Space Evenly option for responsive sizing and positioning of components.

DEV-10582 The ability to display a component by right-clicking on it and selecting display is now available in the palette.

DEV-10779 The Basic Settings section in an objects properties is now called 'Details'.

DEV-11189 Users can now access the learning centre, application properties and add startup actions from the application homepage.

DEV-11200 The component type is now displayed in the repository header to make it easier to see what a component is. For example, Table, Area, Grid, View etc.

DEV-11211 After deleting the current Application, all windows are closed and the Application Selection screen is displayed.

DEV-11499 When an action is added to a grid, the default setting is now to always show the button.

DEV-11537 PhixFlow now displays an error message when an action is run from a Form containing multiple fields with the same name, as this may lead to unexpected behaviour.

DEV-11546 HTTP Collectors and Exporters now appear in the HTTP Datasource properties in the repository.

DEV-12177 The PhixFlow Header now has a button that allows the user to hide/show windows tabs.

DEV-12186 Opening a screen from the screens homepage or repository now opens the screen unlocked.

Analysis Models

DEV-1870 Pipes from transactional tables now always allow incomplete recordsets.

DEV-7039 Tables now have a Basic Settings → Default Data Range option in which you can select, if a view does not have the default data range set, it defaults to using the setting in its backing table.:

Latest: records from the latest recordset only

All: records from all recordsets.

DEV-7601 In analysis models, new objects added using the pop-up toolbar are assigned to the same container as the analysis model.

DEV-7738 In datasource properties, the Database Driver option now links to the driver properties.

DEV-7741 You can now add driver classes to an application or package.

DEV-7870 HTTP collectors and exporters can now use the PATCH HTTP method.

DEV-8272 PhixFlow now checks tables and view-attributes to ensure their properties are correct. If you need to correct the configuration, PhixFlow reports the issue in the Errors list. Application and package properties also have an Errors section, which lists issues with any table or attribute that they contain.
Note: The Errors section reports issues that do not affect processing. For example, the analysis process can run on tables that have no Data Retention property set. However, retaining all data can lead to performance issues, so PhixFlow records this as an error in the table configuration.

DEV-8297 Attributes from multiple tables can now be included in views. Often, the primary key attribute that links related tables has a unhelpful name, such as UID. You can now assign a different attribute to use as the Display Name. This acts as a label for the primary key when it appears in view components; see Attribute.

DEV-8783 In database collectors, the properties menu option Run Query and See Result is now only present when the database collector is enabled.

DEV-10160 PhixFlow now requires all tables to have data retention configured. If no data retention option is set, PhixFlow records an error in the table's Error properties. If you do not want to specify the criteria for keeping data in the Keep... properties, set Data Retention > Retain All Data. However, table data will accumulate, which can lead to performance issues; see table Data Retention properties.

DEV-10388 The pipe property → Maximum Number of records per Group is no longer available on a pipe connected to a calculate table.

DEV-10617 In table properties (was stream properties) the Multipliers and Filters has been renamed to Analysis Options. The following options have been moved from the Basic Settings section into the Analysis Options section:

- Enabled

- Static Data

- Period

- Default Date Range

- Table Type

- Supersede Items on Pipe

DEV-10936 HTTP collectors now include JSON as a response type and JsonPath is available to enter an expression to process data from the JSON block.

DEV-10937 DEV-11115 As an alternative to using a keystore, PhixFlow can now record key/value pairs using a Secret Key and Local Secret. The value, for example a password, is stored encoded. You can refer to the secret key name using ${_datasource.secret-key-name} in an HTTP Header → Value, or a HTTP Collector/HTTP Exporter → Statement Expression to provide a password to an external site.

DEV-10938, DEV10943 To support secure storage of details, both Datasource and HTTP Datasource modelling objects now have the ability to record a secret. This can be applied both locally in the modelling object (Local Secret) or held externally in the Keystore used by PhixFlow (External Keystore). To support the latter these modelling objects have new Advanced → Internal ID property. See Secret Key and Local Secret for detail on how these can be implemented.

DEV-10944, DEV-10945 HTTP collector and HTTP exporter properties have been reorganised so that the commonly-used properties are easier to access.

DEV-11014, DEV-11131 To support data import from JSON, embedded expressions in HTTP collectors/exporters and headers must be enclosed in ${...}. For embedded expressions in other contexts, we recommend changing to ${...}, although {...} is still supported; see Embedded Expressions. As PhixFlow cannot include newlines in an attribute value it automatically replaces newlines in the returned JSON with a space. If you want the data to indicate where the newlines were, in the JsonPath expression, specify the escape character \n.

DEV-11035 A new Analysis Options section has been added to the Table properties, this section contains the Audit Manual Changes option.

DEV-11548 Collectors and exporters now have the ability to use a custom icon if one is provided.

DEV-11657 HTTP Collector URL fields require ${} expressions and no longer accept {} expressions e.g. ${_URL} rather than {_URL}.
Important Note: Existing applications will be updated as part of the upgrade process but should be validated once the update is deployed.

DEV-12105 Terminology Change: "Upload Managed File" changed to "Upload File" to make it clearer.

DEV-12380 The "View Chart" option in a table editor has been renamed to "View Data".

DEV-12402 A File Exporter set to send an email has its icon changed in the repository from a text file to an email envelope to indicate its purpose and configuration.

Common Features

DEV-7359 You can mouse-over an expression in a property tab grid to see the full expression.

DEV-8278 When you save a table or view attribute, PhixFlow now checks that their properties are correct and reports it in the Model Validation Status property. You can see a list of the checks and any corrections required in the Errors section of the Table or View Attribute properties. The Model Validation Status property in an application or package also indicates whether or not the contained tables and view attributes are OK.

DEV-8901 The expression popup editor has a new 'show functions' button and the existing buttons have been updated.

DEV-9751 The Open Repository button now opens a repository browser filtered to the currently selected application. Previously a repository browser showing all available applications was opened.

DEV-9837 Download area columns have been resized to improve the visibility of the information presented.

DEV-10019 There is a new text function, hash, which hash-encodes a string using the specified algorithm. It can optionally include a salt-string.

DEV-10853 The term Stream is replaced with the more ubiquitous term Table.

DEV-10857 The Permanently delete option will be placed at the bottom of all right-click menus.

DEV-11604 All expression editors now have an icon to indicate the allowed inputs.

DEV-11740 Added a new 'Expand / Contract Help' button which allows the user to show/hide the contextual help pane.

DEV-12245 Table repository sub-categories have been alphabetically ordered.

DEV-13005 StreamItemId and supercededDtm is now added to default views.

Administration

DEV-5605 The Tomcat webapps folder now includes a readme file containing the PhixFlow product and package versions.

DEV-6977 In an external user template, you can now specify a default Export Password Policy.

DEV-7086 Logging for emails record now includes the date and time when they were sent or when sending failed.

DEV-7329 The process of moving items between instances (export - import) can result in items referring to something that is not present in the target system. PhixFlow checks to make sure all references go to an item that will exist in the target system once the import is complete. If it finds that an item is missing, the import will fail. There are two ways to resolve this:

Use the console messages related to the import to identify which items are missing. The error messages include the field name of the item in the form object.field, for example UserGroup.users.
- Either, in the source instance, redo the export, ensuring all the items are included.
- Or, force PhixFlow to complete an import with missing items, use the System Configuration → Allow Missing on Import option to specify the permitted missing items, then rerun the import.

DEV-7354 When you add an application to the export window, PhixFlow prompts you to also add all of the application's packages.

DEV-7410 Driver classes now have and Advanced → Datasource Profile property. This can take the values:

- default - for most drivers

- bigQuery - for Google BigQuery.

DEV-7454 There is a new option, System Configuration → System Tuning → DTO Building Thread Pool Size. If there are issues with rebuilding the recently-used object cache (DTOs) on restart, PhixFlow support may advise you on how to tune this option.

DEV-7524 There is a new option for administrators who need to perform system maintenance without PhixFlow running task plans. You can disable scheduled task plans:

- from within PhixFlow, using the System Configuration → Advanced → Disable Scheduled Tasks

- without logging into PhixFlow, using the server.properties file disableScheduledTasks=false option; see Disabling Scheduled Task Plans.

DEV-7539 PhixFlow now checks that a user account has a password when you enable it from the repository context menu, as well as from the properties tab.

DEV-7561 The system console now shows progress messages when a table-action deletes items.

DEV-7644 The Administration menu option Other Options → Publish Streams now attempts to publish tables that have previously failed to publish, as well as publishing all other data to the PhixFlow database.

DEV-7663 Email accounts now have a Protect On Import tick box. With this option selected, the email account will not be changed or deleted when a different version of the account is imported from another PhixFlow instance.

DEV-7739 For driver classes, the Connector Jar File Location is now relative to the Database Driver File Directory. You can specify a specific jar file, or a sub-directory containing multiple jar files; see Database Driver.

DEV-7749 To prevent specific properties being overwritten by an import from another PhixFlow instance, the Protect on Import is now available for:

- File exporter → Recipient Expressions: TO, CC and BCC

- Task Plans → Basic settings: Enabled, Scheduled, Suspend on Failure, Suspended and Schedule.

DEV-7840 When you delete a user, their account no longer appears in the repository or in the user list. To display a list of deleted users, in the repository, right-click Users and select Show deleted Users.

DEV-8807 Setting a value for System Configuration → File Download Expiry is now required. If you have not set a time, upgrading to version 9.0.0 will automatically show the default value of 24 hours.

DEV-9030 Access to the user's details has been moved to the new header bar to improve ease of access. Now, a dedicated screen allows users to manage their accounts.

DEV-10946 In previous versions, HTTP connection log files were truncated. Full details will now be logged, up to the System Logging Configuration →Maximum HTTP Log Length.

DEV-12212 The migration script produces errors, or warnings, when attempting to drop tables used as part of the PhixFlow upgrade where they do not exist.

Bug Fixes

The following issues have been fixed in this release:

Applications

DEV-7378 On a Kanban board, a dragged card is no longer duplicated until the board is redrawn.

DEV-7489 Deleting layout components from the repository no longer times out.

DEV-7506 You cannot type into input fields until the form data has loaded. This prevents attempts to enter data that will be lost when the field is populated.

DEV-7509 For layout components, changes to CSS Properties are now listed in the Audit Summary.

DEV-7531 Layout component default values will no longer be overwritten if there is an empty record in the backing table.

DEV-7573 Formatting rules now refresh when you you select a date from a calendar.

DEV-7619 When a card component on a Screen becomes hidden and then visible once more, as a result of changing context parameters, the correct number of cards will now be displayed.

DEV-7689 When working on a Screen in Design Mode, right-clicking to open the context menu no longer starts dragging layout components.

DEV-7706 When a card container is nested within another card container, a double-click action on the nested card container now correctly calculates _form values.

DEV-8145 Adding an event-handler to a screen will update the screen automatically. For example, a double-click action added to a grid will work without needing to manually refresh the screen.

DEV-8367 Cached Screens now keep the focus when they are reopened in the design mode.

DEV-8792 Fixed multiple problems with the Page Number field on a grid's paging bar including only allowing positive numbers.

DEV-9152 Palettes now automatically refresh when an item is removed.

DEV-9263 Screens now refresh any CSS transform property that relies on context parameters.

DEV-9268 Cards placed on Forms backed by Tables now correctly refresh all records.

DEV-9345 Palettes now correctly refresh after making any changes to them directly or to their elements.

DEV-9369 The need to close and re-open a screen after dragging a component with formatting rules using _field.value has been resolved. The formatting rule accepts the value immediately.

DEV-9569 The 'skip-to-last-page' feature is now working as expected on grid components.

DEV-9741 Pivot view menu options only appear on the right-click for pivot views. Previously these were displayed for all view types.

DEV-9800 Styles applied through formatting rules now correctly apply to selected states.

DEV-9825 Refresh actions now automatically refresh a view after an auto-save action.

DEV-9833 Columns in a grid that are unhidden will automatically display and no longer require a refresh.

DEV-9884 Show in Repository button removed from the application detailed list view.

DEV-9972 Card areas no longer have the Style → Auto Size property, as cards in a card area cannot be auto-sized.

DEV-10151 The case-sensitive flag has been removed from filter editors for PhixFlow instances running on SQL Server, as those filters are always case insensitive.

DEV-10162 Fixed the problem of entering a number larger than the number of pages in a grid, into the paging bar.

DEV-10167 Tabs now support having content dragged directly onto them, including tables and views.

DEV-10169 The help link provided in a Palette's header is now always displayed where a URL value is provided.

DEV-10176 Table view attribute formatting rule expressions will now treat a null value as true and the style will be applied.

DEV-10313 Improved the paging bar for grids and card containers to ensure the correct number of records is displayed in the count.

DEV-10331 Formatting rules now apply correctly to grid cells.

DEV-10441 Editing form fields will now drive other screen content, such as grids, to refresh.

DEV-10475 For a column backed by a view, if the view is renamed, the values in the column filter can now be selected and applied.

DEV-10524 Fixed problem with Grid Header button style not being applied using a grid style.

DEV-10876 The selection highlight is now correctly displayed around layout components that are on the edge of the screen.

DEV-11434 Fixed issues with creating Grid Menus through the Table View Editor.

DEV-11483 Read-only checkboxes in property editors will now have a different mouse cursor.

DEV-11554 The read only CSS property will now be correctly applied to Boolean fields on forms.

DEV-11566 Decimal places are no longer permitted in integer fields.

DEV-11603 Filters added from a Table View's list are now correctly added to the Table View

DEV-12125 Field Containers can now only have Attribute names which start with a letter an only contain alpha-numeric characters or an underscore.

DEV-12410 When creating background filters (by dragging a grid header onto another grid) the user will be asked which attribute to use when the target view is backed by a Query.

DEV-12674 Pivot Views don't refresh data anymore if they are incomplete (e.g. don't have all required attributes set)

DEV-12750 Filters with deleted / hidden attributes will now display as "Attribute Not Found" instead of "NULL"

DEV-12779 When selecting the option to view a list of objects in the repository, any belonging to packages associated to the current application will now be shown.

DEV-12915 Record Sets generated by table actions will now have a cycle of 1 instead of 0. This is shown in the System Console --> Record Sets --> Cycle (column).

DEV-12941 Added "Default Dynamic Text Component" to Application, System Configuration and Package under "Styles" > "Default Components". When dragging an attribute onto a card container this component will be used as the template.

DEV-12948 Fixed problem with 'Is not in' and 'Does not end with' filter conditions for views.

DEV-12972 Views no longer display errors after adding a Background Filter Rule containing "_form" expressions.

Analysis Models

DEV-2354 Using a database reserved name as a view attribute name no longer causes an error.

DEV-4503 Renaming a attribute now properly refactors output multiplier expressions in a different table that is linked by a pipe.

DEV-7409 Using a positive offset push pipe to force an analysis run to repeat, now correctly creates recordsets up to the pipe's Max Stream Sets value on every analysis run, not only the first run.

DEV-7727 Lookup pipes can now be used in datasource instance expressions.

DEV-7728 For a datasource with Protect during import ticked, PhixFlow no longer incorrectly renames datasource instances.

DEV-7729 For non-transactional recordsets, the Rollback All Data option for a log file now runs rollback on all recordsets, not just the recordset related to the log.

DEV-10161 Improved error handling when importing a file and the data in a column exceeds the maximum length specified by the PhixFlow attribute. The target attribute's expected length is now stated in the error message.

DEV-10192 Fixed problem with table icons not refreshing on Analysis Models after the Table's type is changed.

DEV-12428 Resolved error opening view when set as pipe view on file exporter push pipe.

DEV-12656 Data Range of Tables created through Analysis Models is now set to LATEST

Common Features

DEV-7642 View properties have been corrected so that Show Paging Bar is only available for grid views.

DEV-7765 Adding a sort order via a view no longer causes an error.

DEV-8656 The issue of NaN showing in the Page Number field on grids has been resolved.

DEV-10201 The date-time column in the console log can now be resized.

DEV-10850 The Sequence editor now shows the parent container.

DEV-11746 Updating the logged-in user no longer requires a logout and back in to apply the updated properties.

DEV-11850 Fixed problem with message windows being hidden behind other screens.

DEV-11887 When a large number of warnings or errors are displayed the count will now display correctly with all numbers being clearly visible.

DEV-12153 Error messages produced by PhixFlow have been updated to use the latest terminology.

Administration

DEV-6944 When import deletes a sequence, all references to the sequence are now correctly deleted from memory.

DEV-6951 If an import size exceeds a limit on the server, PhixFlow now reports an "upload too large" error.

DEV-7270 In the console, a system task now shows as failed if it fails to archive log files.

DEV-7932 The export policy set in the system configuration is inherited by all users. Previously it was incorrectly using the standard password policy.

DEV-11557 In the user properties, the security questions are now removed for external users and those in mixed mode as they are irrelevant for their configuration.

DEV-11746 Updating the logged-in user no longer requires a logout and back in to apply the updated properties.

DEV-12838 Removed the error when filtering against a Privilege name.

Sections on this page

Introduction
Major New Features and Changes
- Template Package
- Terminology Changes
Installing or Upgrading to PhixFlow Version 9.0.0
Discontinued Features
Changes to Privileges
- New Privileges
- Privilege Changes
Improvements and New Features
Bug Fixes

Browser not supported