Skip to main content
Release notes 2025

Release notes v25.09; More field options, reports as widgets and performance improvements

Door 10 September 2025No Comments

The Neoforce release September 2025 once again brings a range of new features, improvements and solutions.
With this update, we are making the platform even more flexible, faster and user-friendly. Below you can read about the changes this version brings!

What have we added?

  • There is a new field type Person group added. This field type can be used within datasets and additional fields, giving users more flexibility in managing groups of people.
  • On the My Account page, it is now possible to add personal notes. This allows users to easily save their own notes that are visible only to themselves.
  • Reports can now be added as widgets and viewed directly on the dashboard. This makes important information more quickly accessible and insightful.
  • Two new variable modifiers have been introduced: uppercase and lowercase. Allows variables to be automatically displayed in upper or lower case, depending on the desired application.
  • When downloading multiple files at once, the generated ZIP file now contains the name of the object to which the files belong. This makes the contents clearer and more traceable.
  • Performance improvements made.

What did we adjust or fix?

  • For contracts, it is now possible to enter the field classification disable so that it is visible only when relevant.
  • An issue where new timeline responses disappeared when an error occurred during saving has been fixed.
  • The issue where several tabs remained visible after an error when saving a dataset item has been fixed.
  • Sample variables in additional fields used an incorrect prefix; this has been corrected.
  • Filters were unfairly affecting the search page. This now works as intended again.
  • The error where wrong authorisation was applied when deleting timeline history has been fixed.
  • When manually creating a ticket via a template, linked assets were not added. This issue has been resolved.
  • Subtickets created via an extended template were not saving the set assets correctly. This has been fixed.
  • Relationships could not be saved when the schema had a long name. This problem has also been fixed.