7.24.1153 |
  
|
7.24.1153 |
|
Released on August 15, 2024
The IEstimate.Scenarios was not refreshed when a macro was executed multiple times. It always returned the scenarios that existed when the macro was called for the first time.
The result of the IWbs.GetFullData contained wrong empty values for numeric WBS field, if such a field contained a non-numeric value. Only these non-numeric values were correct, and the numeric values were empty.
Two new estimate events are available in the Events Management:
1.On_Before_Apply_Scenario
2.On_After_Apply_Scenario
As with other similar events, the On_Before_Apply_Scenario event is cancellable in which case the application of the scenario will not be done. You can cancel an event with the Cancel_Operation() verb, or if you call a macro in the event, set the following in the macro: context.MustCancel = true.
This occurred when the user moved reports columns left or right multiple times too fast. For example, by holding the ALT+left/right arrow. The report header rows could be displayed as duplicated. Another moving or compute all has fixed it.
When the user moved reports columns left and right multiple times, there was a chance that an error occurred. The Reports tab was left in a broken state and Check and repaint was required to repair it.
A new value NomenclatureFilterType.RowsWithMustPurchase was added which represents the Rows flagged as 'Must Purchase'.
An error was displayed in nomenclatures report, if the filter option in the applied profile was set to "Rows flagged as 'Must purchase'" or "Sets from the database of the estimate (All levels/Level 1)". But this happened only if the estimate was not compatible with the profile filter setting. This means that the estimate didn't contain minute field MUST_PURCHASE or IS_HEADER_OF_SET respectively.
The Delete_Row() verb in requests didn't work correctly, if it was used on the same line as an IF keyword. For example:
If Minutes.[Description] = "ABC" Then Delete_Row()
The old CustomersManual.xml file adapted for V22 and V24 version
When hiding one or several worksheets before the phase 3, the generation of this phase was failing. This is fixed and it is possible to omit one or several worksheets in the final result by hiding them.
When editing a row in another tab than Estimate, the row is saved when selecting another row, however when selecting another tab, the row wasn’t saved and tab didn’t change. The row is now saved also when selecting another tab while still in edit mode.
Due to changes in Windows operating system, the signing process introduced an incorrect signature in the resulting workbook, with a time zone error. The process has been reviewed and fixed.
If the estimate is defined with more than one fieldset in either MATERIAL or WORKFORCE type, the organization was incorrectly applied. This case has been fixed.
Can now insert directly articles or sets in the WBS. It will create tasks automatically if the cursor is a line (above or below a task). One task will be created for each article or set inserted. The description, item and unit fields of the WBS are automatically populated with corresponding values inserted.
Selective undo/redo operations are supported meaning that if you insert several sets or articles at once, you can roll back operations one by one (creation of tasks and insertion of data in the minute).
When the cursor is a rectangle around a task, it works as before meaning that it inserts all article or sets selected inside the task. It doesn't create any new task. This operation can also be rolled back.
We're translating more and more code from VB.NET to C# and an important quantity of assemblies have been translated. This could cause some problems, so, please report any problem you could find in this beta version.