Navigation:  7.17 > 7.17.0651

This beta version is also the exact image of the 7.18.0001 official

Released on June 10, 2019

New: Variables for currencies

Two new variables added SYS_Currency_Of_Estimate and SYS_Currency_Of_Parent_Estimate. The first one contains the currency of the estimate and the second the currency of the parent estimate when the estimate is a child. This works in both adjustable transparency and full transparency modes.

New: Reindex when settings are loaded from a child estimate in adjustable transparency

When you load setting at opening time from a child estimate set for adjustable transparency, a full rebuild operation is made so that the resulting estimate becomes immediately operational.

Change: Import settings in adjustable transparency

In adjustable transparency, when the settings are imported from the child template, the behavior is as follows:

 
. for shared fields, the properties are taken from the parent estimate except for the formula and the position of the fields in the different profiles which is taken from the child estimate. If the shared field is not available in the child estimate then the field is positioned at the right.
. for non-shared fields, the properties are completely taken from the child template.

 

Outside adjustable transparency, when the column definitions are imported, then everything is taken from the source estimate, but the formatting definitions for non-administrators is removed. So a user will start seeing the columns as the administrator has, possibly reduced by permission rights.

New: Message to prevent creation of non transparent children

You cannot create a non-transparent grandchild from a non-transparent child. You have to work in full transparency below a non-transparent child. However, the transparent grandchild created can work with a non-transparent great grandchild using his own shared fields. Normally shared fields should be deleted when creating such a transparent grandchild but this is not done so far, you have to manually delete the shared fields from the fields manager. A new message is now provided to block the creation of non-transparent grandchild from a non-transparent child. The logic assumes that a transparent grandchild should not know what is requested by the parent of his parent (his grandparent)