What's new in version 2025.1.1
July 2025
Version 2025.1.1 is a maintenance release.
Integration with email
-
Smarter ticket linking for email replies in CC scenarios
The Mail Connector now more accurately links reply emails to existing tickets, even when the auto-added MessageID tag is missing. This update specifically addresses a scenario where a CC'd user replies to an email without the tag, which previously caused duplicate tickets to be created. Now, such replies are correctly associated with the original ticket, reducing confusion and preventing unnecessary ticket clutter. This change helps keep conversations consolidated, simplifies technician workflows, and improves the overall experience for both requesters and CC'd participants.
-
Resolved an issue where the Processing tab under Email Processing > Mail Connector in the web Admin Center could fail to load with the error: "The Tree View component requires all items to have a unique id property." This occurred when the same workflow action was referenced multiple times in the Mail Connector's business logic.
Access and sign-in
-
Resolved an issue that could cause the Web App to become unresponsive on the sign-in screen in certain multi-user environments.
Purchasing
-
Resolved an issue with selecting Bill To and Ship To addresses in Purchase Orders. Address details are now correctly populated from the selected Company Address record, rather than defaulting to the last address in the list.
-
Addressed an issue where vendor details, such as FEIN and contact information, were not populated in a Purchase Order if the vendor was selected after the PO was initially created without one (e.g., via direct modification or the "Add Line Item" action). Vendor selection now correctly updates the Vendor Details section.
Software asset management
-
The Tracked Software form now supports multi-select for all Allocate a commands on the Allocation tab, enabling faster and more efficient many-to-many license assignments.
Change management
-
Removed the unnecessary “Closed" status option from the Change Calendar filter. Since closed Change Requests (like other inactive items) are excluded from workflows and cannot appear in the calendar, this change eliminates confusion and ensures the filter accurately represents the calendar’s contents.
Service management
-
Resolved an issue where recent actions for creating Service Requests appeared dimmed in the Recent menu. These actions now display correctly and can be launched like recent actions for other object types.
Dashboards
-
Addressed an issue with loading View-type dashboard widgets. These widgets display lists of data views along with record counts. Previously, if a widget included custom views with resource-intensive queries that took over 30 seconds, it could delay the entire dashboard from rendering. These widgets now load independently, allowing the rest of the dashboard to appear promptly, even if some counts take longer to load.
Organization management
-
Addressed an issue where Reference-type user-defined fields (UDFs) created for Locations were missing from the list of available columns when customizing data views. These fields now appear correctly and can be added to Location views as expected.
Default workflow
-
Expanded push notifications for self-service apps
The default workflow now includes a full range of push notifications for self-service apps. Previously limited to just one "Notify Requester" notification, it now delivers instant updates on all key events like ticket creation, resolution, and satisfaction surveys. This keeps self-service customers in the loop and helps them stay up to date with everything that matters.
-
Improved user import from AlloyScan
Previously, the Owner and Last Logged User values were sometimes missing in Computer records in Alloy Navigator, despite the data being available in AlloyScan. This was due to limitations in how the default AlloyScan Sync business logic matched user information. The matching process has been refined, and user details from AlloyScan now appear correctly in Alloy Navigator.
IMPORTANT: If you are upgrading from a previous version, these updates will not apply automatically. You may need to modify your existing workflow to enable them. For assistance, please contact our Support Team.
Workflow management
-
Resolved an issue where scheduled On-Condition triggers could fail with a "Multiple-step operation generated errors" message when followed by another On-Condition trigger in certain scenarios. This affected the default automation job "Close Completed Request after 14 days unmodified" #2037 and could also impact custom automations.
-
Our How to set up one-click workflows via the API article has been expanded to simplify finding instructions on changing the logo shown on the ticket feedback page (the "one-click workflow"). To update the logo, replace the file located on the web server hosting the API at
[PhysicalPathToAPIfiles]\HtmlTemplates\images\logo.jpg. -
The Self Service Portal no longer unexpectedly converts Date fields to Date/Time when used in custom business logic. This fix ensures consistent behavior with the Web App and prevents unnecessary time shifts caused by differences between server and browser time zones.
Import
-
Resolved an access violation error that occurred when importing projects from Excel (.xlsx) files, specifically when two or more fields were mapped.
Archiving
-
Addressed an issue where archiving jobs unexpectedly required additional SQL Server permissions and could fail to run under an account with only the dbcreator and securityadmin roles. This resulted in errors such as "The database principal owns a schema in the database, and cannot be dropped."
Archiving jobs now run successfully with just the expected permissions, no extra rights are needed. For reference, see the account requirements here.
Admin Center
-
Resolved an issue that caused errors related to invalid decimal and thousand separators in certain Admin Center sections when using non-US browser locales. The Admin Center now correctly handles numeric formats across all user language settings.
Documentation
-
Our Admin Center vs. Settings App article has been updated to better reflect how the availability of administrative settings differs between Cloud and On-Premises deployments. Based on user feedback, explanations have been added to clarify why certain settings, such as License Management, are view-only in Cloud deployments.
INFO: The full list of differences between Cloud and On-Prem can be found here: Installation Guide: Alloy Navigator Cloud (SaaS).