Releasenotes v25.02; drag and drop at tables, Tags for triggers & actions and much more

As you've come to expect from us, the February 2025 update also brings a bunch of new features, changes and more to production environments! In a departure from normal practice, we are pushing this update on Thursday evening (13 February).

Below you can read what we changed;

What have we added?

• Triggers and actions can now be linked to tags for better organisation. In doing so, you can also click on a tag to see all actions (or triggers) of that tag. You can link multiple tags to one action or trigger.
• Imported tickets now more clearly show the attachments above the request.
• It has become possible to insert an additional field in tickets at more places (blocks).
• Pages on the customer portal can now -in addition to forms- also link to other pages.
• Datasets and additional fields now also have a field type 'Text field - dynamic height'.
• Table fields can now also have a self-manageable width per column.
• The rows in table fields can now be manually sorted by drag and drop.
• You can now add a 'plain text' to datasets as well. This is not a field but just 'readable text' for end users.
• In user management, we have added a short notepad that is visible and usable only by administrators.
• It is now possible to set a start and end date of a ticket created via mail import.
• The KPI bar in datasets can now be hidden with the click of a button.
• The 'applications', 'certificates', 'databases' and 'servers' pages now also have the 'Linked' tab. This allows you to quickly and clearly see all linked tickets and more in the future!
• Contracts now also have the (optional) 'Renew for' field.
• On the 'Applications' page, you can now enable or disable more fields.
• Forms can now have more than one person field.
• When copying various objects, files are now included.
• The image preview window now also shows a [Print] button.
• From now on, you can also use an action to generate a subticket. Of course, you must then perform the action on an extended ticket.
• The API now allows you to pass the value in addition to the database ID during an update.
• Variables (usable in actions, triggers and more) now also have the value from 'history'. That means you can use, for example, the new status (after saving) but also the old status. You do this in (for example) the following way '${ticket.history.statusID.old} or ${ticket.history.statusID.new}'.

What did we change or fix?

• Only non-pushed notifications are now -if enabled- emailed.
• In some cases, if you clicked the [Download] button when previewing an image, the thumbnail was downloaded.
• Forwarded .eml files became corrupted.
• Various minor UI and UX tweaks.

Apart from these points, we have changed even more. You can therefore find the full changelog in Neoforce itself.

If you have any further questions, please contact support!