...
Introduction
PhixFlow version 7.4.0 introduces exporting to multiple tabs in excel, along with performance improvements in the design component on the new GUI.
At this version of PhixFlow, the old flash-based GUI is still available.
...
Contents
| Table of Contents | ||||
|---|---|---|---|---|
|
...
Installation and Upgrade
To install a new PhixFlow instance, follow the standard installation instructions.
...
Excel File Collectors that specify the worksheet to read in the Excel Data Range Expression must now quote the worksheet name if it contains spaces and/or single quotes. This is not handled automatically by the upgrade process. See here for details.
| Anchor | ||||
|---|---|---|---|---|
|
...
- edit phixflow-datasource.xml
If you are using Oracle 12c, configuration imports can sometimes fail with this error:
...
| Code Block |
|---|
<bean id="hibernateProperties" class="org.springframework.beans.factory.config.PropertiesFactoryBean"> <property name="properties"> <props> <prop key="hibernate.dialect">org.hibernate.dialect.Oracle10gDialect</prop> <prop key="hibernate.order_updates">true</prop> <prop key="hibernate.jdbc.batch_size">1</prop> </props> </property> </bean> |
Contents
| Table of Contents | ||
|---|---|---|
|
...
Deprecated Features
Graphical User Interface
...
We recommend that users do not use these features for new work, and plan to replace them in existing configurations.
Database
The following database versions will not be supported after 31st March 2018:We are planning not to support the following old database versions in releases after 31st March 2018. Please contact the support desk if you are currently using any of these versions and are not planning to change by then. We'll plan continued support if needed with your input.
Oracle 11g
SQL Server 2012
...
The INSERT, DELETE and UPDATE types will cause the buttons to behave as if they had a predefined action attached with the same stream update action and, in the case of insert and update, the copy values by name the Copy Values by Name (see below) option ticked without actually having to configure and attach such an action. The stream to which this will be applied is the stream associated with the outermost area of the form.
You can define a button as INSERT, DELETE or UPDATE and then also attach an action. This might be needed, for example, if you want to carry out some validation logic, display confirmation messages, completion actions or to calculate some specific values for fields. In this case, the button will run the action but the type of the button (i.e. insert, delete or update) will override the corresponding setting on the action and the stream associated with the outer area of the form will override the stream specified on the action. The value of the copy values by name the Copy Values by Name field will be taken from the attached action.
...
Improvements to performance of modelling in new GUI
improvements ...
Changes to assist in application development
Drag a column header on a button to create a context param
...
A number of changes have been made to improvement performance in the new GUI while modelling.
Easier application development
In addition to the introduction of quick configuration for CRUD forms, a number of changes have been made to make creation of applications quicker and easier:
Stream view styling
You can now specify styles which will be used for displaying data grids. Those styles can be set on:
- System Configuration
- Application
- Stream View
Styles available:
- Grid Header Style
- Grid Header Button Style (applies to action buttons)
- Grid Header Icon Style (applies to standard PhixFlow buttons, e.g. filter, sort order
- Grid Header Dropdown Button Style (buttons that open menu lists)
- Grid Header Dropdown Pane Style (menu lists)
- Grid Paging Style (the paging bar)
- Grid Row Style
- Grid Column Header Style
Drag column headers onto buttons to create a context parameters
You can now drag a column header onto a button to create a context param parameter with the same name, and the value of the attribute from a selected record, in the underlying action.
Quick create for dashboard open button
The user can now drag You can create a button to open a dashboard in any of the following ways:
- Drag a dashboard onto a view header
...
- Drag a dashboard onto a form
...
- Drag a dashboard onto a button
...
- ; this will add a rule to the action behind the button, which opens the dashboard
...
- Drag a dashboard onto an area
...
Quick create for drop-down
The user You can now drag a StreamView stream view onto an inputField Input Field or a Field Container in order to convert it to a DropDown with the View and Value Attribute configured. This will convert the field/ container to a Drop Down showing the view.
Copy by value option on stream actions
There is a new option on stream actions that update the stream items called 'Copy Values by Name'. If this option is ticked then , if the action is performed from a form, any values on the form from which the action was initiated will be copied onto the stream items being updated. This is unless there is a specific stream action attribute for that field, in which case the value calculated by this attribute will be used instead.
This means that if you drag a new stream attribute onto your form, then the values entered into that field on the form will automatically be copied to the underlying stream item by insert or update actions without having . You do not have to create specific stream action attribute expressions for the new field on each stream action.
...
Automatically pass through previous context variables
There is a new tick box in the Context Parameters section of the Stream Action stream action editor called "include previous context parameters". If this is ticked then , any action on a dashboard will automatically pass on any context parameters sent to the dashboard when it was opened. This is unless the action also specifies a new context parameter of the same name.
...
When creating stream action expressions or formatting rule expressions you can now refer the fields on the relevant form (i.e. the form to which the action is attached via a button or the form to which the formatting rule applies) using the internal variable _form. This allows you to refer to fields on a form that includes a button for this action, rather than specifying the name of the dashboard element.
New views/forms for transactional streams
...
show all data
When you drop a transactional stream on onto a dashboard area to create a view then , the dashboard element is set to show all streamsetsstream sets.
Similarly, when you drop stream attributes attribute from a transactional stream onto a form on a dashboard, the dashboard element is set to show all streamsetsstream sets.
Use context variables if no backing record
When you pass context variables to a dashboard that contains a form, the context values will be used as default values for any form field with the same name. If a record is also retrieved from the server then the values of those attributes on the record that match the field names on the form will override the default values taken from the context variables - even if the value on the record is null.
Throw an error if two dashboard elements/streamViewLayoutComponents with the same name
You will now receive an error message when running an update action if two elements on a dashboard have the same name or if an element name clashes with the name of a lookup pipe on the stream being updated.
Other
Charts show spinner while updating
Charts are now showing spinner while updating
Miscellaneous
Empty menus made larger
Added minimum width and height of for drop-downs, so they are visible even if the user does not have privileges to see any of its the items in the drop-down.
Superceded flag on pipes
New 'Include Superseded' flag on pipes. If ticked, the result will include superseded records. Otherwise they'll be filtered out.
=============================================================
...
Exclude superceded records by default
New configuration flags have been included to make it easier to manage the flow and display of superceded records from self-updating streams.
Previously, if you had a stream with superseded superceded records in it then , any reads from that stream , e.g. on pipes in analysis models or when refreshing stream views, - through output pipes or in views - would include those superseded superceded records by default. To exclude them you would have to add specific filters to do soa filter.
Since in In most cases you do not want to see the superseded records (as in most cases they simply superceded records - generally, they represent the audit trail of old versions of the record) these records. These records will now be excluded by default unless you tick the 'Include Audit History Records' box flag.
In analysis models this tick box is found on the pipe. For stream views, the tick box is found on the stream view itself, but can be overriden overridden on dashboards by:
- ticking the same option on the dashboard element details (if the
...
- stream view is attached directly to the dashboard) or,
- on the stream view layout component (if the stream view is embedded in a form)
...
...
Custom fields
...
can be referenced in dashboards
Custom fields (not backed by a Stream Attributesstream attributes) can be referenced on dashboards, i.e. used in filters, actions.
...
Dashboard icons in open dashboards now show the dashboard description when the mouse pointer is hovered over the icon. Previously, this just showed on dashboards when a dashboard was hovered over in the list of dashboards in the repository browser.
Show click immediately on submit buttons in old forms in new
...
GUI
Submit button is grayed out after submitting a formgreyed out immediately in old forms, in the new GUI, after being pressed.
Specify styles for old forms
System Configuration has two new fieldfields:
- Form View Header Style
...
- Form View Content Style
...
These allow to specify styling of old forms.
...
Bug Fixes
Text input slowed down while modelling
...
Filter conditions now draggable
...
CSS properties were not ordered.
Error when deleting View that is automatically created
...
Can delete stream views created by dragging streams onto dashboards
An error was generated while deleting a stream view created on a dashboard by dragging a stream onto the dashboard
Actions with no context variables defined now have a context
| Fixed bug whereby the dashboardToOpen context parameter is always set on the return from an action. |
...
. This has been fixed.
Can now refactor with dangling input pipe
If a stream had a pipe with nothing on the other end - i.e. no input stream or collector - it was not possible to change the names of other pipes or stream attributes. This has been fixed.
...
No unfriendly error message on drop-down after multiple select
An unfriendly error message was thrown when the user selected multiple records in a driving view, opened a form then tried to open a drop-down. This error will no longer be thrown.
Fixed historic migration issues
drop_down_mapping.parent_id is nullable in migration scripts, not nullable in fresh install
Migration not setting ordered_area.layout_type to nullable
...
In particular:
- DROP_DOWN_MAPPING.PARENT_ID should be nullable; in some upgraded instances this was not correct
- ORDERED_AREA.LAYOUT_TYPE should be nullable; in some upgraded instances this was not correct.
_prompt filters no longer causes views to minimise and not close
Fixed problem with when calling _prompt filter from a standalone Stream View
...
could cause view to minimise, and not be closable.
Password reset link no longer gives 404
Fixed bug with invalid password reset url URL when app application name was not provided.
Standard error no longer appears on top of action validation error
If you throw an error in a stream action, using the " error" function () function in action validation, the user now only sees the error message you throw, and not the general task plan failure message.
Stream actions
...
now show errors caused by configuration
Stream Actions actions now correctly show configuration errors.