🎯 Now Live!Release Date | 19th October 2026
The following section provides fixed issues in Apex Aspen Q3 Patch 2 release.
Fixed Issues
The following are the fixed issues in this release.
Issue ID | Issue Description | Resolution |
|---|---|---|
192553 | HR work orders did not appear for users. | HR work orders are displayed correctly for users. |
193343 | CR emails were sent after the status was changed to Cancelled. | CR emails are not sent when the status is changed to Cancelled. |
193916 | Issues were encountered with CR approval through the mobile app. | CR approval works correctly through the mobile app. |
193069 | The auto-fill field does not work | The auto-fill fields work as expected |
191880 | Following successful hardware and software discovery, the discovered assets were not being automatically populated into the inventory as expected. Analysis identified that a stored procedure failure in the hardware and software variance processing job was preventing discovered asset data from being updated in the inventory, specifically in the Apex 2.0 environment. | The issue was resolved by correcting the stored procedure failure and restoring the hardware and software variance processing workflow, ensuring discovered assets are successfully synchronized and updated in the inventory automatically.
|
194149 | Role-Based Access Control (RBAC) for Apex 2.0 Knowledge Articles was not functioning as expected. | The RBAC configuration has been corrected, ensuring users now have appropriate access to knowledge articles based on their assigned roles and permissions. |
193850 | For a Catalog ID, the Catalog Name was appearing twice, creating a data discrepancy when compared with the corresponding Transaction table records. | The data inconsistency has been resolved, and the Catalog Name is now displayed correctly in the table |
194123 | Custom field dropdown values were not populating on the End User Incident page in the mobile app. Since the fields were mandatory, users were unable to select values or submit tickets successfully. | The dropdown value population issue has been fixed, and users can now select the required values and submit incident tickets without any issues. |
194126 | In the mobile app, the mandatory Emp ID custom table field did not display related dropdown values, allowing users to enter unrestricted values and submit Service Requests. | The Emp ID field validation has been corrected, and the dropdown now displays the appropriate values, ensuring accurate data entry and controlled submissions. |
191536 | When a child subcategory was selected, the Approver and Publisher fields appeared blank, preventing users from viewing the associated assignment details. | The field-mapping logic has been corrected, and the Approver and Publisher details are now displayed correctly when a child subcategory is selected. |
193132 | Row numbers (sequence numbers) were displayed when reports were downloaded in Excel format but were missing from CSV downloads, resulting in inconsistent report outputs across formats. | The report export functionality has been standardized, and row numbers are now generated consistently across supported download formats as per the configured requirements. |
193130 | The downloaded report displayed a generated number instead of the report name when exported to Excel or another format. | The downloaded report displays the correct report name. |
193661 | The SR Catalog Remarks/Subject field was missing from AIW. | The SR Catalog Remarks/Subject field is included in AIW. |
193571 | Some tables were missing after an upgrade. | All required tables are available after the upgrade. |
193595 | When creating an SR, the user group details were not displayed for approver selection, and a user dropdown was displayed instead. | User group details are displayed correctly for approver selection when creating an SR |
193593 | The attribute sequence on the New Service Request page did not match the sequence in the web application. | The attribute sequence on the New Service Request page matches the sequence in the web application. |
192275 | HTML markup/code was displayed directly on the payment request catalog tile instead of rendering correctly, causing the intended catalog content to appear incorrectly to end users. | The payment request catalog tile displays the intended content correctly without exposing HTML markup or code to end users. |
191854 | On the Fixed Asset Inventory page, clicking the Total Count was displaying an error message prompting users to refresh or try again. The issue occurred across all asset statuses, including Allocated, In Store, and Inactive. | Clicking the Total Count on the Fixed Asset Inventory page displays the asset details correctly across all statuses, including Allocated, In Store, and Inactive. |
193586 | In the HMSI Apex 2.0 Q3 mobile app, approving Change Requests (CRs) was triggering an error, although the approval process worked as expected on the web application. | Change Requests can be approved successfully through the HMSI Apex 2.0 Q3 mobile app. |
193725 | An alignment issue occurred with the Custom Attribute fields on the End User page. | The Custom Attribute fields on the End User page are aligned correctly |
194004 | An alignment issue occurred with the Custom Attribute fields on the End User page. | The Custom Attribute fields on the End User page are aligned correctly |
193266 | The radio button element on the Incident General form was displaying incorrect formatting, with misaligned text and symbols. The text did not remain on a single line when sufficient space was available in a single-column group. | The radio button text on the Incident General form is correctly aligned with the symbol and displayed on a single line when sufficient space is available in a single-column group. |
193943 | An issue occurred while importing a simple list to create a time zone lookup table, where unexpected symbols appeared instead of the “+” sign. | The simple list imports correctly into the time zone lookup table, displaying the “+” sign as expected. |
193835 | The issue was occurring when attempting to view Change Records from the Analyst Main Page. The error message, “Invalid length for a Base-64 char array or string,” appeared intermittently but was encountered most of the time when opening Change Records. | The issue with viewing Change Records from the Analyst Main Page has been resolved. Change Records are now opening successfully without any error. |
193894 | The visibility control for a Service Catalog item was not working as expected. The User Picker field was not being hidden correctly when the Yes/No field was empty or in the In Selection state, despite the configuration working correctly for Yes and No. | The visibility control for the Service Catalog item is working as expected. |
193922 | The user was unable to deactivate certain categories due to associated catalog items that could not be located. They were also unable to deactivate some catalog items to proceed with deactivating the related categories. | The catalog items and associated categories can now be deactivated successfully. |
192964 | The Assigned Workgroup data was missing from the dataset. | The Assigned Workgroup data is now appearing correctly in the dataset. |
130006 | Data was not syncing to the IM Overview report at specific time intervals. | Data is now syncing correctly to the IM Overview report at the specified time intervals. |