What's new in version 2024.2.5

February 2025

Version 2024.2.5 is a maintenance release. It addresses several issues reported in previous versions.

Setting up Recurrent Ticket jobs

Resolved a layout issue in the Recurrent Tickets schedule form where the Occur panel was too narrow, causing label wrapping. The panel now displays correctly, improving readability and ensuring a cleaner layout.
Addressed an issue where Recurrent Ticket jobs failed to be created in specific cases. This happened when their workflow form contained a mandatory virtual field or when the workflow template included a string field that was not present in the form. Recurrent Ticket jobs are now created successfully, regardless of the forms and templates used.
Resolved an issue with custom forms for recurrent change requests where the attachment area was not displaying correctly, preventing attachments from being added when setting up a Recurrent Ticket job. The attachment area now displays and functions as expected.

Restored the ability to search by object identifier, such as ticket number or article ID, when the search scope is set to "Everywhere."

Resolved a visual issue with custom dashboard layouts where column widths specified in pixels were incorrectly interpreted as percentages, leading to unexpected results. The column width is now applied exactly as specified.

Resolved an issue with the NinjaOne Integration in the default workflow pack. Previously, the integration encountered the error "'STRING_AGG' is not a recognized built-in function name" when running on Microsoft SQL Server 2014 or 2012. This issue has now been resolved. To obtain the updated integration, please contact our Support Team.

Updated the Node.js platform included with the installer to a newer version. This update will take effect after the upgrade, improving the overall stability and security of the portal.

Resolved an issue where importing configuration settings failed with the error "The UPDATE statement conflicted with the FOREIGN KEY constraint" when the export file contained a type-based custom form layout. This issue is now resolved, ensuring smooth export and import of configuration settings.