...
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
...
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:
Drag column headers onto buttons to create a context
...
parameters
The user 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 - even if the value on the record is null.
Throw an error if two dashboard elements/streamViewLayoutComponents with the same name
...