release 3.2

NEW FEATURES

#47 - New instruction to create a reference data entity : add reference entity ENTITYNAME

Entity model is completed with two new fields :

• order field ( type number )
• enabled field ( type boolean, default true )

#46 - Do not erase the file toSyncProd.lock.json to ensure the ability to update properly any version of a generated application

In a nodea application, there are three files used to manage the database synchronization :

• toSync.json
• toSyncProd.json
• toSyncProd.lock.json

Any instruction is loggued onto the toSync.json file.

toSync.json file is used when starting the app and then the content of this file is moved onto the toSyncProd.json file.

When using the deploy instruction, the file toSyncProd.lock.json is completed with the content of toSyncProd.json file which is executed on the deployed application : this is done automatically by the nodea platform. This feature is not available when using the nodea software on your own from desktop.

Each deployment will create a new entry in the file organized in this way :

{ "deployments":
    [
       { 
         "versions": VERSIONNUMBER,
         "queries": [ QUERIES ]
       }
    ]
}

#48
Status component comes today with the possibility to check "Comment" option.
If checked, then a popin is reased when changing the status and the use can add a free comment.

This is usually not sufficient for any report purpose. So we have added a new tab Reasons to Status entity in order to allow the selection of a predefined reason when changing a status.

Adding of a new tab called Reasons on a status in order to have some predefined elements to select when using the status.
Adding of an option reason ( motif in French ) ( boolean type )

If the option is checked, then the popin displays a select input. If both options ( reason and comment ) are checked, select input and textarea are displayed.

Moreover, history status table is automatically completed with a foreign key to the c_status_reason table.

# 41 - Create a datalist with column aggregating fields for "has many" relationship ( related to fields )
We added the ability to concat values in a single column when using "has many" relationship.

FIX

#41 - Create a datalist with column aggregating fields for "has many" relationship ( related to fields )

#45 - Security enhancements for local authentication

#44 - By default on a select2 input, cursor is not properly focused on the select area

#42 - Postgres enhancements - using of iLike expression