🎯 Now Live!
Release Date | 25th September 2026
The following section provides fixed issues in Apex Aspen Q2 Patch 7 release.
Improvements
Following is the improvement in this release.
Improvement Name | Description | Benefits |
|---|---|---|
Report Configuration Enhancements User Persona: Report Designer | Report Alert Configuration
Reporting Tags
For more information, refer Report Designer Alert Access and Tags. |
|
Fixed Issues
The following are the fixed issues in this release.
Issue ID | Issue Description | Resolution |
|---|---|---|
192295 | Upon clicking the User tab twice from the User Dashboard, users were redirected to the old Dashboard. | Clicking the User tab twice now redirects users to the correct dashboard. |
191248 | Validation controls did not work as expected in the Change module. Validation rules configured in Form Builder, such as making a text box mandatory when a custom checkbox was selected or hiding the text box when the checkbox was cleared, were not applied. | Checkbox-based validation rules now correctly make the dependent text box mandatory when the checkbox is selected and hide it when the checkbox is cleared. |
191387 | The Change the PR status to Pending to fill 5 Why Remediation information message was displayed intermittently when changing a Problem Record status from Pending to Resolved or from Resolved to Closed, although the message was not applicable to these status changes. | The 5 Why Remediation information message is not displayed during the Pending to Resolved or Resolved to Closed status transitions. |
189947 | Business Rule 11 was triggered even though the user had not entered the keyword “AWS”. | Business Rule 11 now triggers only when the user enters the keyword “AWS.” |
186295 | Asset bulk allocation failed when Employee ID was used as the user reference, displaying a “User details are not valid” error instead of allocating the assets. | Asset bulk allocation now works as expected when Employee ID is used as the user reference. |
191208 | CC recipients did not receive email notifications when a ticket was reopened. | CC recipients receive email notifications when a ticket is reopened. |
191333 | An error occurred when attempting to implement an auto-created task after the associated CR was approved up to the CAB stage. | System allows auto-created tasks to be implemented successfully after the associated CR is approved up to the CAB stage. |
186367 | The Effort button in the Apex 2.0 GATI and CLIX instances was not functioning as expected, preventing users from performing effort-related actions within the application.
| The Effort button functionality in the Apex 2.0 GATI and CLIX instances, enables users to perform effort-related actions successfully.
|
191449 | Field labels were overlapping with their corresponding input fields, resulting in an unclear and misaligned user interface. | All field labels are displayed clearly without overlapping. |
193182 | The AD user's email ID was getting cleared from the User Details page when the user declined GDPR. | AD user's email ID is now retained on the User Details page when the user declines GDPR. |
193210 | The hyperlink for the Incident ID field was not available in the New Incident Logged notification. | The Incident ID field in the New Incident Logged notification now includes the hyperlink as expected. |