Add tab muni on Selector showing as many exploitations as the municipality has (disabled by default)
A new tab has been added in order to see the exploitations that each municipality has. To enable this tab, the column "enabled" in table "config_param_system" has to be set to "True" for the parameter "basic_selector_tab_municipality".
Enable the possibility to use a specific sequence on code for every feature type
A new functionality has been developed in order to set a customized code for feature types. First, it is necessary to create a sequence on the database which name is the concatenation of the "id" of table "cat_feature" and the words "code_seq" (i.e "circ_manhole_code_seq). Then, this sequence is going to be used when inserting new objects of that type of feature.
Additionally, a prefix can be used in combination of the sequence to build the code for the object. To do so, a JSON string has be to added in column "addparam" of table "cat_feature". This JSON has to contain the key "code_prefix" and the prefix itself as the value of that key.
Relate connec.plot_code with table by using plot code if variable edit_connec_autofill_plotcode is true
If true, this variable enables the possibility to capture by intersection the plot code for the connec inserted. It can be found in table "config_param_system" where parameter name is "edit_connec_autofill_plotcode". It is necessary to fill the table "ext_plot" with the geometries of the plots and its cadastral reference or plot code in order to see how it works.
New field on ext_municipality, ext_region, ext_province: ext_code
A new field has been added into tables "ext_municipality", "ext_region" and "ext_province" under the name of "ext_code". The aim of this field is to enable the possibility to use an external code to identify the municipality, region and province. This code can be either an oficial standard code or a customized code.
Add utils table ext_province_x_region with double fk to ext_municipality
A new table called "ext_province_x_region" has been added with foreign keys to table "ext_muncipality". This table stores the relationship between province and regions.
Add combo for feature_type on dimensions dialog [ARC, NODE, CONNEC {GULLY}]
Now, it it possible to choose the feature type in the info form of a dimension object.
Rename config_graph_inlet to config_graph_mincut
Table "config_graph_inlet" has been renamed to "config_graph_mincut".
Remove expl_id from config_graph_mincut
Column "expl_id" has been removed from table "config_graph_mincut".
Disable mincut if user hasn't any inlet on canvas to work with
Mincut is disabled unless an operative inlet is located in the working canvas.
Remove config_graph_valve strategy by using graph_delimiter column from cat_feature
The configuration for valves now it is done by column "graphdelimiter" of table "cat_feature".
Add '%' symbol on profile's slope
The symbol "%" now appears in the profile picture in order to show the units of slope.
Remove to_arc and status on inp_shortpipe. Instead, now inventory values are used
Columns "to_arc" and "status" can now be found in table "config_graph_checkvalve" as part of the inventory values.
New variable "plan_node_replace_code"
The aim of this variables is to trace the original code to a node that has been involved in a feature when a node replace is done in planification mode using the spceific tool Psector Relations tab. This variable can be found in table "config_param_system" under the name of "plan_node_replace_code".
New field on plan_netscenario_presszone: presszone_type
A new column "presszone_type" has been added to table "plan_netscenario_presszone". The available values for this columns are present in catalog "edit_typevalue" where column "typevalue" is "presszone_type".
New fields on plan_netscenario_presszone and plan_netscenario_dma: stylesheet, expl_id2
New columns "stylesheet" and "expl_id2" have been added to tables "plan_netscenario_presszone" and "plan_netscenario_dma".
Enhance cat_manager by working with system users and roles
Now, the table "cat_manager" works with database system roles and users instead of working with the content of table "cat_users".
Clean dbmodel: Drop views vi_parent_arc, and v_anl_flow_*
Views vi_parent_arc and v_anl_flow views have been deleted in order to clean unnecessary views.
