PhixFlow 5.9

Resizing Dashboards 

Dashboards can now be set up so that their content automatically resizes as the Dashboard resizes. 
This means that Dashboards can be configured so that end users can adjust the size of the Dashboard for their screen and the contents will adjust their widths and height automatically. 

The new options are available through the context menus on the Dashboard background pane and on Dashboard contents. 
The options allow the user to divide the Dashboard up into multiple resizing or fixed width/fixed height panes and then specify whether items placed inside the panes should be maximized or should have absolute positions and dimensions. 

Context Menu options are: 

• Add Vertical Bar: Splits the pane left and right 
• Add Horizontal Bar: Splits the pane top and bottom 
• Delete Pane 
• Layout Options: Opens a form allowing the user to specify 
  • Maximize the pane content 
  • Fix the pane width
  • Fix the pane height

There is a new menu item under Admin button - 'Manage Email Accounts'. 
Clicking on that opens a list of Email Accounts which allows adding, updating and removing existing Email Accounts. 

• Outbound accounts are used to send emails from PhixFlow. There can be only one enabled outbound account. 
• System fetches emails from all enabled inbound accounts. There can be more than one active inbound account.

Internal variables are now available also from normal File Collectors: 

• _fileName
• _modifiedDate 
• _path 
• _rootDirectory 
• _subDirectory 
• _size 
• _lineNumber - not available in 'File Details Only' File Collectors 

It is now possible to change the stream index scheme while the stream contains data. Changing the index scheme optimises the stream for reading from individual steam sets or from all stream sets.

Indexes and primary keys on core tables have been reviewed and deleted / added where appropriate.

Selection Views now use the selected attribute instead of first attribute of the view. 

There is a new 'Show Attributes' option in the Stream Views list context menu which shows Attributes of the selected Stream View.

curValue() and nextValue() takes expressions, not just literals.

Instance name is now accessible for expressions as the "_system.instance".

Privileges list is now sorted alphabetically.

The "Grid" Stream View definition form now shows all properties of the view attribute (not just its name).

The Stream View Attribute definition form now shows a box indicating the size of the field on a form i.e. there is now a visual indicator of the meaning of a width of (say) 100 pixels.

Dashboards can now be set to open in a maximized state by default. The option is available through the Dashboard editor.

A new button is available under the User menu (top right corner). It allows switching between a Design and App mode. 

Design mode allows the user to see design functions of PhixFlow, the toolbar on the left in particular. 

App mode hides configuration features of PhixFlow. 

The default mode of the user can be set through the user editor. 

Users need to have a permission in order to use the design mode. If the user has no permission to use the design mode, the app mode is launched. 

The selected mode can be specified also through the URL, by adding a "design=true/false" attribute. A list of attributes should be prefixed with a '?' character. For example: 

• www.phixflowexample.com - a default user's mode will be launched. 
• www.phixflowexample.com?design=true - a design mode will be launched (if the user is permitted) 

• www.phixflowexample.com?design=false - an app mode will be launched

  (This release contains more changes which affect the URL. See Upgrade Notes for details)

The user can now set up multiple applications. 

Every application can have its own set of menus which can be displayed at the top of the screen. Menu can be set as a default for desktop devices and for mobile devices. The appropriate menu will be displayed according to the user's device. If only one menu is specified, it will be the default for desktop and mobile. 

Users can also choose any other menu from the new list of Applications and Menus available through the new icon at the top left corner of the screen. The list allows launching Applications using the same window, new window or new tab (available through the context menu - right-click).

Another way of launching selected Application and Menu is typing its name at the end of the URL and prefixing them with the '#' character. The Menu name should be separated by the '/' character. An example URL would look like: 

• www.phixflowexample.com - no Application specified. 
• www.phixflowexample.com#App1 - the 'App1' Application will be launched with the default menu (if specified). 

• www.phixflowexample.com#App1/Menu1 - The 'App1' Application with the 'Menu1' will be launched.

  (This release contains more changes which affect the URL. See Upgrade Notes for details)

Upgraded selected external packages.

DATE and DATETIME columns are being exported to Excel in the same format as they appear on the Stream View.

It is now possible to configure a 'pivot table' stream view in which values in a nominated value attribute are broken out into one of many view columns based on the value in a nominated pivot attribute. 

The pivot view columns can be

• all values in the view data
• the result of an expression (which can in turn refer to a lookup pipe on the source stream)

Pivot column headers can be derived automatically from data values using date/time and number formats on the view attributes, or from label attributes.

Publishing always checks for existing data before applying changes.

Publishing no longer incorrectly identifies all integer stream attributes as changed and if the stream is marked as having no data.

Correction to 5.5 to 5.6 migration script for Oracle based instances. Default Dashboard filters are now being restored during the upgrade.

Fixed bug with CSV and Excel file collectors failing if there were more columns in a file than expected.

Fixed bug with possible GUI locking while having some configuration windows opened.

Fixed a floating digit issue during the update action.

Fixed bug with failing model import.

Fixed bug with ifNull function not returning list properly.

concatenateList casts single values to lists.

Fixed bug with the not populated filter list on the view configuration screen.

Fixed bug with exporting floating numbers to Excel.

Fixed bug with the user updating error while the user has some passwords archived more than a year ago.

Fixed bug with the alphabetic lists sorting on the Oracle database.

Whether a stream action caused its invoking view to refresh on completion or not was changed at release 5.6.0. In earlier releases it was implicit, and from 5.6.0 onwards a refresh had to be explicitly requested by adding the action to the list of view refresh actions.

The migration scripts from 5.5.1 to 5.6.0 attempted to create the necessary view refresh actions, but failed in the case where a view referenced the same action more than once. This problem is fixed in the 5.6.0 migration scripts in this release.

Fixed bug with a stream filter with an 'is in' condition generating invalid sql if the list of values on the right-hand side of the condition is zero-length.

The System Logging Configuration window shows the 'Log Exporter Statements' tick box correctly.

Corrected possible issue with the handling of failed streamsets generated by a different instance of PhixFlow.

Fixed bug with the visible password length of other users

Dashboard object background filters now set driving-driven links correctly.

Email sender:

1. Make a backup copy of the phixflow-datasource.xml file.
2. Open the phixflow-datasource.xml file.
3. Note the port, host, username, password and javaMailProperties values.
4. Delete the mailSender bean from the phixflow.datasource.xml file.
5. In PhixFlow go to Admin → Manage Email Accounts and add a new account.

6. Tick the Outbound flag, type the account name and enter values from the step 2. The Properties have format: property.name=value. Each property should be entered in new line. Tick Enabled.

   You can test the configuration by entering a test email address and sending a test email by clicking the Test Configuration button.

Email fetcher:

1. Make a backup copy of the phixflow-email.xml file.
2. Open the phixflow-email.xml file.
3. Note the enabled, port, host, protocol, username and password values.
4. Delete the phixflow-email.xml file.
5. In PhixFlow go to Admin → Manage Email Accounts and add a new account.

6. Leave the Outbound flag unticked, type the account name and Enter values from the step 2. If you leave the Pooling Interval blank, the pollingInterval value configured in the server.properties file will be used.

   You can test the configuration by clicking the Test Configuration button.

As there are new functionalities which can be accessed by manipulating the application URL it is important to remember about the sequence of using new URL attributes:

1. design=true and design=false must be typed right after the default PhixFlow URL and be prefixed by the ‘?’ character.
2. #ApplicationName/MenuName must be typed at the end of the full PhixFlow URL.

• www.phixflowexample.com – PhixFlow without any defined Application in a mode specified as default for the logged in user.
• www.phixflowexample.com?design=true – PhixFlow without any defined Application in the Design Mode
• www.phixflowexample.com?design=fals – PhixFlow without any defined Application in the App Mode
• www.phixflowexample.com#App1 – App1 application with a default menu in a mode specified as default for the logged in user.
• www.phixflowexample.com#App1/Menu1 – App1 application with the Menu1 in a mode specified as default for the logged in user.
• www.phixflowexample.com?design=true#App1 – App1 application with a default menu in the Design Mode
• www.phixflowexample.com?design=false#App1 – App1 application with a default menu in the App Mode
• www.phixflowexample.com?design=true#App1/Menu1 – App1 application with the Menu1 in the Design Mode
• www.phixflowexample.com?design=false#App1/Menu1 – App1 application with the Menu1 in the App Mode