Admicom Estima Software updates

Modified on Fri, 16 May at 10:20 AM


Software update 15.5.2025 (2025.6.0)


Admicom Estima


Repaired/changed


  • Fixed Estima-Tempo integration so that projects that were published for Reporting are displayed in Estima-Tempo integration
  • Fixed Excel export currency symbols to be displayed wrong in the PrintOut view
  • Fixed Summary output in the PrintOut view. The output did not work if the scope information had a value of 0
  • Short by cost groups (functions menu) is now automatically on by default if the user has not turned them off separately
  • The sums and units of Ultima XML cost groups have been corrected
  • Fixed The scope information in the bid calculation so that the sub project scope information is now included in the total project amount
  • Fixed the length of the resource type field so that entering a string that is too long is no longer possible
  • Setting as project manager is now possible with administrator rights
  • In addition, other program library updates



Rest API


Repaired/changed


  • The quantity attribute of the work-items interface has been deprecated and disabled. In the future, use the calculations.quantity value, which can be included in the listing result by adding "include=calculations" to the query (.../work-items?include=calculations)
  • The total attribute of the calculations object of the work-items interface has been deprecated and disabled. Use calculations.totalPrice in the future
  • Fixed simultaneous adding and editing of purchase invoices to make it more reliable
  • The project data (/projects/projectId) has a VAT percentage ("vatPercent")




Software update 9.4.2025


Admicom Estima


Repaired/changed

  • Fixed resetting of work item selection when adding work items from the library to the building element 
  • Fixed the error related to the expiration of the login (token error), which caused red error messages for users 


Rest API

Repaired/changed

  • Fixed the error related to the calculation of floating points in the Rest API, which caused extra decimals