Smarter wiki articles, a completely revamped action engine for plugins, improved email actions and a whole host of enhancements to tickets, reports and projects. That’s what we’ve added in the September 2026 release!
You can read the full changelog below;

What have we added?

• French, Spanish and Norwegian have been added as languages for Neoforce users.
• It is now possible to use variables in wiki articles. This works both on the portal and in the practitioners’ section.
• The wiki within the customer portal now (optionally) displays the six most-viewed articles. You can enable this option via Administration > Wiki > General settings > Customer portal (section)
  
• Dataset schemas can now also colour the icon in the menu. This is optional and must be enabled in the schema settings.
• The ‘Generate ticket’ action type now also allows you to link people and wiki articles directly (the ‘Linked’ tab).
• The ‘Linked’ tab for people and organisations now gives you the option – via a drop-down menu – to quickly filter by open and/or closed tickets.
  
• Inactive items in the search results are now clearly marked with a yellow border.
• Drop-down menus and search bars for people now display the profile picture (where available).
• When importing emails (both tickets and accounts), you can now configure the system so that imported emails are moved to a specific folder are moved.
  
• You can now choose, for each setting, which method to use for a new ticket is created (standard, form or template). This process is triggered by clicking the ‘New ticket’ button; the other options remain available via the drop-down menu next to it.
  
• New ‘Registrant Card’ page (within tickets) to quickly view relevant information about a registrant. This page can also be accessed via the URL, making it easy to integrate into your telephony system (for example, from RedCactus) can be used.
• The ‘Export to PDF’ buttons now first open a window where you can select the page orientation (portrait/landscape) and an optional header/footer, rather than exporting straight away. The header/footer options are not available on the customer portal.
  
• New action type ‘Newsletter’. This works in the same way as the standard email campaign, but instead of selecting multiple email addresses, you choose just one group of people in the [On] field (without CC/BCC). Every active member of that group with an email address receives their own email, meaning the other recipients remain invisible. The subject line and message are personalised for each recipient: the recipient’s variables are available as ${person.*} and if ${recipient.*}.
• The drop-down menu for a project within tickets now displays the project’s client as the subtitle.
• A personalised, toggleable filter has been added to the project selection box on tickets, which limits the results to projects linked to the ticket’s organisation.
• You can now limit the number of columns returned by an API filter’s output.
• A new authorisation, to be granted by object type (and by dataset schema), to determine who is permitted to make a saved filter public or shareable. Personal filters remain usable indefinitely; existing groups and users will retain their current rights via a migration process.
• The start date and time of a stopwatch can now be edited ‘inline’.
• It is now possible to set a publication date for wiki articles.
• The ‘End date including extensions’ field has been added to contracts.
• Floating notifications are now hidden as soon as you open the notifications screen, and no longer appear if that screen is already open.
• The authorisation options when adding or editing an API token now have the same look and feel as those for users and groups.
  

What did we adjust or fix?

• The search query is now saved when you open the search settings and is automatically run again after you save any new settings.
• Reporting on land parcels is now also possible.
• The page title that appears in the header when scrolling now has a copy button when you hover over it.
• The UI/UX of the public wiki on the portal has been updated.
• The header and footer columns in email templates now support larger amounts of data.
• The error message that appears when scanning a QR code using the camera has been made more user-friendly.
• Zooming in on images has been improved.
• The system now remembers whether the inline search bar is expanded for each user.
• When sorting teams on smartphones, you can now scroll without accidentally dragging.
• When removing images from Markdown text, several blank lines would sometimes remain; now, at most one remains.
• When dragging dataset fields, no warning appeared when exiting the schema. This has been resolved.
• The ‘Changes based on fields’ widget was not exporting to PDF or XLSX. This is now working again.
• The pop-up window displaying tag results would sometimes overlap when switching between fields.
• A potentially fatal error when adding multiple dataset objects simultaneously via the API (__multibody) has been resolved.

As well as the points mentioned above, there are loads of other things that have changed or been improved!
You can read the full overview in the changelog within your own Neoforce tenant.

Questions?

Do you have any questions or comments? Please feel free to contact support!