PhixFlow

PhixFlow version 7.23.0 is the first latest release of the design component of PhixFlow in the new GUI. This presents the design component with a new look a and feel, for designing models and applications. This also provides the design component in the new front end technology (HTML5, rather than flash), so that all of PhixFlow is now available in the new technology.

...

1. First review Compatibility Guide and Upgrade Planning to check any changing requirements for database versions etc.
2. Follow the Standard Upgrade Instructions plus any special instructions for all intermediate releases listed in Compatibility Guide and Upgrade Planning.

Special notes

For this release, there is an additional step when upgrading from a version at less than 7.2.0 to 7.2.0 or above. This only applies if you are running against a SQL Server database.

Change to SQL Server Dialect in datasource file

If you are running against a SQL Sever database, you need to update the dialect specified in the datasource file. The Standard Upgrade Instructions describe managing your phixflow-datasource.xml file, and migrating this to the new release. In this file you will have:

                <prop key="hibernate.dialect">org.hibernate.dialect.SQLServerDialect</prop>

Update this to say:

                <prop key="hibernate.dialect">org.hibernate.dialect.SQLServer2012Dialect</prop>

There are no special instructions for this release.

...

Contents

...

New Graphical User Interface (GUI) for design component

This release is the first to feature the design component of PhixFlow in the new presentation technology, which uses HTML5 rather than flash. 

The design component has also been given a new look a feel, to support creating models and rich applications.

...

Deprecated Features

...

URLs for opening PhixFlow and applications

The URLs used to start PhixFlow in standard mode, or to go straight to an application, have changed. See /wiki/spaces/HELPTRUNK/pages/47218729 for details.

Performance

It is now possible to specify on a stream by stream basis

• whether any indices should created during publishing
• whether inserts into Oracle should be direct paths inserts

Bug Fixes

Cache refreshes after PhixFlow upgrades

It is no longer necessary to clear your browser cache after upgrading PhixFlow. Previously, in some cases after an upgrade, you would get an error telling you that the client and server version did not match, and to resolve this, you would need to clear your browser cache.

Analysis fixes

Recovery after cancellation

If an analysis run was cancelled then re-run, the following run would always fail as it tried to roll back the incomplete results of the first run. This is now fixed.

Lookup pipe failures sometimes ignored

In some cases, lookup pipe failures were reported but did not cause stream data generation to fail. This problem was introduced in 6.0. This is now fixed.

Try function

...

The current Graphical User Interface (GUI) is supported in this release, but will be removed in a future release.

The following features are not supported in the new GUI, and will be removed when the current GUI is removed.

Alarms & Alarm Generators

WorkFlows

We recommend that users do not use these features for new work, and plan to replace them in existing configurations.

...

Features and Improvements

JDBC Drivers

The embedded JDBC drivers for Oracle, SQL Server and MariaDB (MySQL) have been updated to the latest versions compatible with Java 8.

New GUI Changes

Spellchecking, autoCorrect and autoComplete are now disabled in text areas and string fields.

Active Directory Integration

Active Directory group names are now matched to group names defined in User Groups and in System Configuration regardless of case.

Configuration Import/Export

The new configuration import/export mechanism is available for general use from the new GUI. The new mechanism has the following features:

Export then import recreates objects with the same internal ids as the originals. This is in contrast to the current mechanism which creates objects wth new ids. This means that objects transferred in partial exports overwrite the existing objects and no longer have to be manually re-integrated.

Objects can be collected into Containers (Applications or Containers). When a Container is imported, it completely replaces all previous contents of the same Container.

Improved performance.

Improved reliability.

...

Bug Fixes

Analysis Engine

Analysis ignored changes to disabled pipes between Streams, Collectors, Exporters etc.

Database Collector

Internal variables _fromDate and _toDate are now set correctly in Database Collector statements.

File Collector

Internal variables _fromDate/_toDate were not set correctly for File Collectors. This problem was introduced at 7.2.0 as part of a set of performance improvements.