Service Management Releases

What’s new on Service Management? Navigate a detailed release log of new features and fixes.

Brand New 7.96.7
Feb 18, 2025
Bug Fixes
Minor
Addressed some mistranslations across different languages.
#39902
Brand New 7.96.6
Feb 18, 2025
Bug Fixes
Minor
Fixed an issue preventing date label to show up in some cases.
#38017
Brand New 7.96.5
Feb 17, 2025
Bug Fixes
Major
Resolved an issue where Custom Fields were not visible for input when opening a new request in SQL Server environments.
#39712
Brand New 7.96.4
Feb 14, 2025
Bug Fixes
Minor
Fixed a bug that prevented certain users from being edited.
#39833
Brand New 7.96.3
Feb 14, 2025
Bug Fixes
Minor
Minor performance enhancements.
#39827
Brand New 7.96.2
Feb 11, 2025
Bug Fixes
Minor
Fixing a minor bug preventing mouse over tooltip to show up.
#39754
Brand New 7.96.1
Feb 10, 2025
Bug Fixes
Minor
Resolved an issue where certain actions and filters were incorrectly displayed in the predefined views of the Self Service Portal.
#39735
Brand New 7.96.0
Feb 7, 2025
Features and Improvements
New
Multi-Stage Selection in Workflows
Selecting multiple stages within a workflow got real! Simply hold the Ctrl key (Cmd for Mac users) while clicking on individual stages or drag to create a selection rectangle. With this, you can easily move groups of stages around the canvas, making workflow organization faster and simpler.
#20197
Bug Fixes
Minor
Addressed an issue where the reporting engine sometimes failed to update workflow stage data, leading to inaccurate reports.
#39480
Minor
Addressed a bug that caused request lists export failures for on-premises customers if the file was generated outside a temporary directory.
#39387
Minor
Before this fix, shared custom fields could be used only once per Start/Form stage. Now, you can use shared custom fields multiple times within these stages, providing greater flexibility in your workflow configurations.
#39026
Minor
Updated authentication settings to better align with access restrictions
#38395
Minor
We've resolved an issue where 0 was being considered both "undefined" and a valid number, causing unpredictable behavior in conditional paths. Now, the system properly differentiates between an empty field and a user-entered 0, ensuring reliable decision-making.
#26256