...

...

Installation / Upgrade

To install a new PhixFlow instance, follow the standard installation instructions.

...

When using a Date/time function on an Attribute. If , if the date parameter is NULL, the function returns null instead of throwing an exception failing with the message that the date can not be null.

...

A message can now be set on the PhixFlow home screen which is displayed prior to log in when the application starts up. The location of a file containing the HTML message can be specified in the SystemConfiguration. If this file is set then the contents will be displayed on the home screen.

...

A new checkbox has been added to system configuration window - 'restrict non admins only' . When ticked - it restricts login privileges from any non admin user. Only , so only admin users will be are able to login. Default value is set to false (unticked checkbox), this allows for every authorised user to login.

 It is no longer possible to create a new user without also setting a password, and this avoids a number of secondary issues arising from users that have no password set.

...

In the System Configuration - Advanced tab - the 'Schema Version' field can display longer version numbers containing additional label information

Change name of The System Configuration parameter from 'Max Page/Chart Size' has been renamed to 'Maximum Download Size'.

Active Directory Integration

When logging into PhixFlow as a Active Directory (LDAP) user, the list of user groups for that user are saved in a single database field, and are used to determine which PhixFlow User Groups of which the user groups are available in the application. Now exclude any groups provided by active directory if they don't exist in PhixFlow as there are too many user groups providedis a member. Previously, that list of user groups could exceed the size of he database field, resulting in that user being unable to login. The saved list is now limited to those groups that are relevant to PhixFlow.

When an Active Directory user logs in, a user is created in PhixFlow using details taken from the Active Directory server.:

• The user's First Name is populated from the AD Active Directory givenName field.
• The user's Phone Number is set from the first of the following AD Active Directory fields (telephoneNumber, mobile, or ipPhone) that is set.
• The user's Organisation is set to the Company or Department fields from the Active Directory record.

...

We have revised the layout of the Email Account form to make it more usable.

Diagnostics

Now a task initialisation failure message contains more details about the failure itself, and in case of stream attribute expressions failures - it contains the details of stream name which failed, stream attribute name which failed, as well as the actual expression that failed.

More A more meaningful message is now provided in case of archiving failure.

...

Performance statistics are now recorded in the 'STATSstats' table.

Time duration statistics are now all standardized to be stored in seconds .

Statistics Data recorded by PhixFlow is stored in a table called Stats.

(whole seconds or decimal fractions depending on the statistic).

The start time (from_dtm field) and end time (to_dtm field) fields of each stats record were previously populated with the current time at the start/end of the Monitor Service for each period. However this period started at any number of seconds within a minuteperiod covered, regardless of the relationship between the reporting period and the hour. We now schedule the start time to rounded time within a minute based on the DB  stats reporting period to be scnchronized with the hour based on reporting period set in the System Configuration, e.Ieg. if set to 15 seconds then stats are recorded at seconds 00 / 15 / 45 for each minute.

The STATS_RECORD table has been renamed STATS.

The 10 minutes, reporting periods will start on the hour, 10 mins past the hour, 20 mins past etc.

The Stream statistics now include the total time write time.

...

The statistics recorded now store the full context information when they are written. and the process that initiated the activity. Eg. the Iniator could be "TaskPlan X", with a context of "stream A" with the statistical data recorded for "INSERT_COUNT" (Total count of records inserted for the Stream intiated by Task X). The Initiator context Id's and context Id's are stored should the original name of the Stream/object be modified since having recorded the statistics.

...

Operational

Both web clients now actively check that they are connected to a compatible server. This prevents users from continuing to use an old gui client if the server has been upgraded whilst they were logged in.

Performance

Stream Actions and Task Plans are now compiled the first time they are run, and the compiled versions are saved so that they can be re-used in subsequent runs. This can result in significant performance improvements, particularly for Actions that are run frequently.

...

Bug Fixes

...

Dashboards

Importing a dashboard that had a background filter set to reference a driving view could cause the filter to fail at runtime.

...

When creating a Pivot View, A a pivot column source can be set to an Expression referencing a lookup pipe that is used to generate the pivot columns. If the lookup pipe is was self referencing on the stream for a Pivot View, then it is getting the columns read data from the previous stream set in instead of the latest streamset. It now correctly creates the pivot columns using the latest streamset.

Show Pivot views now correctly show the record count in the page status/navigation bar for Pivot Views.

When setting up a Pivot View, a label attribute can be specified. If the same label is used by more than one Pivot column, the view now fails with a message giving the name of the label and which column its already been used on.

...