Check System Requirements and Compatibility for changes to the system requirements or supported database versions. For example, you may need to upgrade your database or Java version.
Please email support@phixflow.com if you are planning to run PhixFlow on an unsupported database version.
Ensure you have a backup of the database before upgrading PhixFlow.
Follow the Upgrading PhixFlow steps. It is important to complete Step 8, in which you apply any Special Upgrade Instructions for all the intermediate releases between your current version and the version to which you are upgrading.
Special Upgrade Instructions
New settings have been added to the logback.xml.example file to enable logging of audit events to file. The applications logback.xml file should be updated with these new configuration sections.
If it is desired to terminate Phixflow if audit record writing fails for extended periods of time then the setting dbAuditService.haltOnDiscardCommitted should be set to true.
Schema Changes
No Schema changes are required for this release.
New Features
Bug Fixes
DEV-18000 - Fixed the import deleting sort order attributes when the table and the sort order are held in different applications or packages.
DEV-18028 - In the properties of a Table View, a fix has been applied to the "allow export to Excel and CSV" option which stops PhixFlow from erroring when this feature is used.
DEV-18056 - An optional configuration setting (dbAuditService.haltOnDiscardCommitted) has been added, which when set will terminate Phixflow if audit records are unable to be written to the database after extended periods of retrying (24 hours, configurable by setting dbAuditService.retryForMs).
DEV-18107 - Audit records are now also recorded in a separate audit.log file as they are being generated. This guarantees their availability even if the application is restarted before they can be written to the database.