Check System Requirements and Compatibility for changes to the system requirements or supported database versions. For example, you may need to upgrade your database or Java version.
Please email support@phixflow.com if you are planning to run PhixFlow on an unsupported database version.
Ensure you have a backup of the database before upgrading PhixFlow.
Follow the Upgrading PhixFlow steps. It is important to complete Step 8, in which you apply any Special Upgrade Instructions for all the intermediate releases between your current version and the version to which you are upgrading.
This release includes changes that affect the PhixFlow database. After upgrading, remember to republish the PhixFlow data as described in Step 10 of Upgrading PhixFlow
Special Upgrade Instructions
Grid/Table Styling Changes
In version 8 grid rows were alternating by default (white/grey). This is no longer the default since version 9. This is no longer the default since version 9. To enable alternating colours the 'Grid Row Style' and 'Grid Alternate Row Style'.
In version 8 grid cells had borders by default. This is no longer the default since version 9. Cell borders can be created by setting the top border in 'Row Styles' and a right border on 'Column Styles'.
In version 8 grid rows were highlighted in green when the mouse hovered over them. This is no longer the default since version 9. This can be restored by setting the background colour of the 'Grid Row Hover Style'.
All styles are listed below.
Restoring Grid/Table Styling from 8.3
If you wish to restore the grid styling from PhixFlow Version 8.3, the following Styles can be updated in Administration → System → Configuration → Styles Tab → Style Settings, .add these styles to the Style's CSS Properties:
Grid Row Style:
height: 18px
borderRight: 1px solid #d3d3d3
Grid Alternate Row Style:
background-color: #e6e6e6
Row Selection Style:
background-color: #07e51c
Grid Row Hover Style:
background-color: #22FF37
Styling Review
Previously style attributes were wrongly being inherited even when they were not enabled in the parent style. This has been fixed. Applications should be checked to ensure their styling is still correct and that they weren't relying on the previously broken behaviour.
Read only Review
The Read only setting is now reliably inherited by child components, from their parent component. Behaviour of existing applications should be checked in case previous misconfigurations are now being applied. Any issues can be resolved by explicitly setting the read only option on the child components to override those inherited from the parent components settings
Schema Changes
Schema changes are not required for this release.
Improvements and New Features
N/A
Bug Fixes
DEV-16294 - For views, in app mode, it will now only shows 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-16575 - Background Filter Rules now add correctly to DropDown Fields backed by relational attributes. 'Add Filter' button now add correctly to DropDown Fields backed by relational attributes.
DEV-16577 - Read only settings are now reliably propagated to child components.
DEV-16638 - Action flows will now ignore incomplete record sets except those created in the same action flows.
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-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-16728 - Fixed regression where the css property "Display: none" was being ignored. Components are now correctly hidden when the css property is set.
