...

Similarly, when you drop stream attribute from a transactional stream onto a form on a dashboard, the dashboard element is set to show all stream 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 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. This has been fixed.

Actions with no context variables defined

...

no longer have a context

...

At a recent version, a change was introduced which always defined a context for an action - even when the action had no context variables defined. 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

In particular:drop

• 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.