Highlights

 

Duplicate a flow

It is now easy to duplicate an existing flow from the context menu of the flow. A dialog will appear where you can enter a new name for the flow and then a copy of the flow will be added to the flow class. This allows you to easily use the base of an existing flow for a new flow.

 

Add activities on a sequence

Right-click on a sequence to add an activity directly in the right place. Instead of switching between the flow and the palette, there is now a quicker option. The palette opens into a search dialog where you can type directly to find the right activity. Use the down arrow to jump to the list and select the activity. Double-click or Enter to insert the activity into the flow. Shift+Enter inserts the activity and immediately opens the Properties dialog.

 

Working with decisions

When adding a decision, the properties dialog immediately displayed the validation message that a sequence with a condition had to be added. This message no longer appears in the decision properties dialog, as you can't change anything at this point.

It is also now possible to arrange the sequences of decision conditions in a specific order. This is important for code generation. The order can be important, especially when working with numbers.

 

New Clipboard activities

New activities have been added to use the VCL clipboard functionality. It is now easy to write to, read from and clear the clipboard.

Improvements

1.A new Information tab has been added to the properties dialog for an activity. This tab contains an input field which allows you to change the caption/title of the activity. This helps to make the flows more readable.

2.Firebird can now be selected as the database server for a datasource. This means that a specific Firebird SQL dialect is used to generate statements for entities and database queries.

3.Generators are now imported from a database. A generator can be associated with a field in the data entity edit dialog. This generator will then always be used in insert statements for that entity. Generators are supported by the Oracle and Firebird database server options.

4.The field definitions of the Codolex dataset now include the precision and scale for numeric fields as defined in the data entity.

5.You can now also use Ctrl+D in a list of properties to apply the stringify function. For example, when creating or modifying a variable with an entity or when calling a flow with parameters.

6.It is now possible to use literals in the text of a custom query when selecting columns. For example, a fixed text or a number instead of a column name.

7.Added the ability to add and use form data parameters to REST operation parameters.

8.Validation messages produce warning messages in the generated code. Even if they are informative. It also blocks the generation of code for the activity. This has been changed. Informative validations will not block code generation and produce hint messages instead of warnings.

9.It is now possible to clear a variable selection in property dialogs.

10.Other small changes to improve the JSON import, make labels in activities clearer, fix tab order in property dialogs and make the editor more stable.

Fixes

1.Boolean fields are now converted to JSON as true and false instead of -1 and 0.

2.The select statement of a view entity containing an updatable entity is now saved correctly after changing.

3.When a field of an entity variable is used, the condition will now produce the correct code statement.

4.It is no longer possible to drag connected activities into a subflow.        

5.The flow is now better displayed in the flow editor when the source code preview is open. Variable names now remain visible.

6.When adding a parameter to the REST operation, the value of the selected parameter is no longer displayed. The fields are empty.

7.Pressing Ctrl+D in an empty input no longer throws an exception.

8.If an entity field was updated and the entity instance was also used in a dataset, an error message was displayed if the modified field was not defined as a field in the dataset. This has been fixed.

9.Changes to the project, a data entity or a data flow can cause validation notifications in other data flows. These validations did not always reflect correctly in the editors of open flows.

10.The Codolex dataset now throws an exception if LoadEntities is called while the dataset is active.