Who is this article for?

Administrators interested in learning more about product updates.

No elevated access or permissions are required.

This article outlines the product changes, enhancements, and fixes that have been implemented for our LTS clients throughout 2025.

2025.3.1.0 LTS

General

• Updated links in the Help widget:

  • Customer Portal now directs to Ideagen Community

  • Help now redirects to Ideagen Help

  • API Documentation now redirects to Ideagen Help

  • What's New? now redirects to the release notes section of Ideagen Help

Features

Interface updates

• Enhanced the navigation and top menu interface throughout all system pages:
  • Updated header to better reflect the solution brand
  • Enhanced collapsible left navigation panel, offering users a more comprehensive view
  • Introduced Favourite Settings menu, replacing the Gear icon from the previous navigation

Security

• Addressed multiple vulnerabilities to enhance security.

• Extended support for Single Sign-On (SSO) to allow authentication using an attribute other than email.
  Previously, our SSO only supported email-based login. With this update, you can now configure an alternative attribute for SSO authentication, providing greater flexibility to meet security and compliance requirement.
  You can set up the additional attributes by following out guide to configuring additional Single Sign-On (SSO) attributes.

• Added support for the system to store up to 10 previous passwords per user.
  This enhancement increases the number of previous passwords retained, improving security by preventing reuse of a broader set of past passwords.

Workflows

• Added the ability to disable groups in inactive workflows when they are indirectly assigned as responsible parties through a custom field in an inactive workflow instance.
• Improved error messages to provide clearer guidance when a group cannot be disabled or deleted.

• Introduced a dedicated section in the Group Summary view that clearly shows if a group is used via a custom field in a workflow instance.

Technical

• Updated ASPOSE library. Upgraded to version v24.9 to enhance system maintainability and compatibility.
• Updated NuGet package. Refreshed outdated NuGet packages to improve system stability and long-term maintainability.
• Modernised data access with Dapper update. Converted legacy code from Ado to Dapper.

Fixes

• Resolved an issue where custom document reports incorrectly included documents with an expiration date one day beyond the selected range.
  The filtering logic has been corrected to ensure accurate results within the specified date range.
• Resolved an issue where removing a user from one of multiple assigned sign-off groups incorrectly removed their sign-off task, even if they were still in another assigned group.
  Now, sign-off tasks remain in the user’s inbox as long as they belong to any sign-off group, and changes to sign-off personnel/groups do not affect active instances.
• Resolved an issue where fields were not saved correctly for all affected routes.
• Resolved an issue where duplicate route requirements appeared when initiating a recurring step in the Workflow.
• Corrected Portuguese and Spanish translations in the versioning details within the bottom navigation menu.
• Added the ability to add a non-displaying category to custom fields to allow easier selection, using the format <!category>Custom Field Name (e.g. <!Laboratory>Sample ID>).
• Improved error handling for the Date Picker to correctly validate UK, US, and invalid date formats.
• Corrected sorting issues in report date columns that use the UK date format (UK tenant only):
  • Date Retention Activity
  • Retired Document List
• Resolved an issue where a date-type custom field in workflow instances launched via Workflow Automation displayed a default time value of "12:00 AM", even when users entered only a date.
  The field will now correctly display only the date, as intended.
• Some of the areas do not display the correct date/time format, even when the server is configured to Day-Month-Year settings. The format only appears correctly when the user preference is explicitly set to languages utilising the Day-Month-Year format.
  The system should not rely on user preferences languages for date/time formatting. Instead, all formats should be standardised to align with the server settings, consistent with other modules.
  For example, if the server date format is DD/MM/YY, it should be displayed as DD/MM/YY, rather than defaulting to MM/DD/YY.
  Impacted areas:
  • • Common Scripts > Workflow Fields Audit Trail > Time Stamp field
    • Reports > Data Retention Activity > Run > Date Published/Completed & Date Deleted fields
    • Reports > Retired Document List > Run > Date Retired field

This fix applies only to workflow instances launched through Workflow Automation. Parent instances are not affected, as they already displayed the date correctly.