Release 8.0.9

To upgrade an existing PhixFlow instance: 

1. Check the Compatibility Guide and Upgrade Planning for changes to the system requirements or supported database versions. For example, you may need to upgrade your database or Java version.
2. Ensure you have a backup of the database before upgrading PhixFlow.
3. Follow the instructions in Upgrading PhixFlow. There are no special instructions for upgrading to PhixFlow 8.0.9. However, if you are upgrading multiple versions, remember to check the Special Upgrade Instructions. 
4. After upgrading, check for models that contain the StaticStream → PushPipe → Stream structure; See Check For Affected Models, below.

Check For Affected Models

1. Run your preferred SQL tool or database management tool.

2. Copy the following SQL query into the tool and run it.

   select s.stream_id, d.name as "Stream Name", p.pipe_id, p.name as "Pipe Name", p.output_data_handler_id
   from stream s, pipe p, data_handler d, stream s2
   where s.stream_id = p.input_data_handler_id
   AND s.stream_id = d.data_handler_id
   AND p.output_data_handler_id = s2.stream_id
   AND p.pipe_type='NOTIFY'
   AND s.static_data_boo='T';

3. If the Static_Stream → Push_Pipe → Stream structure occurs in any models, the query returns the rows that represent the static stream and its push pipe. 
   If you have this structure, note that:
   • In previous releases, running analysis on the stream at the end of a Static_Stream → Push_Pipe → Stream structure would cause the static stream to run.
   • From version 8.0.9 the static stream will no longer run.
4. If this change will affect how the model runs, you must modify the model to ensure it continues to work as intended.

Features and Improvements

DEV-6893  Before you can reset your password, you must have three security question/answer pairs and an email address associated with your account. 

DEV-6791  The way push pipes and static streams interact has been improved. This fixes an issue in which a static stream would sometimes be run when it should not; see Check Affected Models, above for details.

DEV-6846  Audit records now record that they were created by an import process. The records state "<change made> while importing".

DEV-451  To track down user login problems you can now configure logback.xml to produce a security log file. This log file records login, logout and failed login attempts. You can find the option in the TOMCAT/webapps/$WEBAPP/WEB-INF/classes/logback.xml.example file. See also Install PhixFlow Webapp.

Bug Fixes

DEV-6888  Google Chrome's password manager no longer asks to save data (such as the answer to a security question) that is not your password. Previously, the password manager treated the answer to a security question as a password.

DEV-6854  When dragging items from lists into property tab grids, selecting multiple items now works correctly. You can select items by clicking the line or using the checkbox at the start of the line.

DEV-6911  A double-click (default) action on a stream view now works correctly for views other than grids, for example charts. 

DEV-6796  In number columns, if you try to use a quick filter with no value specified, PhixFlow now treats the search value as _NULL.

DEV-6803  Scrolling in a drop-down list no longer adds columns to the list when the stream view has Show Records Count set.

DEV-6838  For floating point number fields, a default value of 0 now correctly shows the decimal places.

DEV-3553  The documentation has been updated to include the internal variable _system.instance. You can use this variable in an expression to return the current instance name; see Internal Variables.

DEV-6881  Sometimes, tasks appear stuck in the Active Tasks section of the console. If this is caused by errors writing information to the log, the tasks will now automatically clear after 15 minutes. This means you no longer need to restart Tomcat to clear the console.

DEV-6892  For administrators setting up user accounts, you can save the properties without setting any security question/answer fields. If you set any security question/answer fields, you must complete all of them before you can save the user properties.