Navigation:  7.18 > 7.18.0683

Released on October 22, 2019

New: Partnership with Edisys (SPIGAO) extended

SPIGAO is now part of the 'Automation/Partner application' menu. The ease of use has widely improved compared to the external module we had. To use it, you can now download and install the SPIGAO application from the menu and just click 'Import' button to import projects either from the web or for local files and 'Export' button to export and display SPIGAO documents. This makes the dialog really simple and efficient. Even without subscription, you can test the demo project provided.

Important: You must install version 3.6.3 of SPIGAO. You can download it from: https://support.spigao.com/download/projet-stable-setup/

The new implementation enable full support of SPIGAO features:

•Comments

•Fixed prices

•Links between tasks

•Last level in the minutes

•Prices for information

If you want to subscribe, please contact directly Edisys: https://www.spigao.com/

Change: Editing Reference when having centralized storage

When centralized storage in the database of the estimate is active and a list with valid entries is provided when editing the reference fields in minutes then the article or the set is stored in the database of the estimate and a reference to it is made from the row where the input is done.
When afterward this reference field is overwritten with a new valid entry, this pushes the new article or set to the database of the estimate and a reference to this new entry is made from the row.

When editing the reference field of an article in the database of the estimate itself, this replaces the complete row with the new article (article name is taken from the reference field in this case). This can lead to invalid references to the old article in which case proper error messages are generated.

When editing the reference field of a reference to an article (i.e. article in a set), then this new article is inserted in the database of the estimate (if not existing yet) and a reference to this article is written to the edited row.

Change: Contract database – Use Quantity per unit for minutes inside set for Set database

For all minutes Quantity was stored as quantity in Contract Set database. Now it is Quantity per unit for all minutes inside a top level set (so minutes in a set and set header inside another set), still Quantity for minutes outside set and top level set header.

Bug Fix: Double-click on an estimate in the Search module

The module was only closing without any information. Now, it leads to QDV7 and open directly the selected estimate.