- 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.
- 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. We also recommend that you republish the PhixFlow data as described in Step 10 of Upgrading PhixFlow.
| Tip |
|---|
If you are upgrading |
from a version earlier than 8.2.0, please read the special upgrade instructions for 8.2.0. This release introduced the keystore and encryption of security data. It also changed the database indexing scheme for stream data tables. Updating the indexing scheme in a large Oracle database may take a long time. If this is an issue for you, please contact PhixFlow Support. You may be able to use the |
Bug Fixes
DEV-8195 When upgrading PhixFlow on SQL Server, the java upgrader no longer incorrectly keeps indexes that include the superceded_dtm column. This was causing the upgrade to fail.
DEV-7806 In an analysis model, if you rerun analysis after a failed analysis run on a transactional stream, PhixFlow now correctly deletes the data from the failed run before reprocessing the transactional stream.
DEV-8036 In legacy forms, actions triggered from a form view will now find the attributes set in _prompt.
DEV-8039 Number formats with Use thousands separator ticked no longer overwrite trailing zeroes when Suppress trailing zeroes is also ticked.
DEV-8209 User groups now correctly export then importing to another PhixFlow instance.