---
title: "Release Notes Apex Aspen Q2 Patch 4"
slug: "release-notes-apex-aspen-q2-patch-4"
status: "update"
updated: 2026-09-21T11:16:33Z
published: 2026-09-21T11:16:56Z
canonical: "help.symphonysummitai.com/release-notes-apex-aspen-q2-patch-4"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.symphonysummitai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Release Notes Apex Aspen Q2 Patch 4

> [!NOTE]
> 🎯 Now Live!
> 
> **Release Date | 28th July 2026**

The following section provides fixed issues in Apex Aspen Q2 Patch 4 release.

- [Fixed Issues](/apex/docs/release-notes-apex-aspen-q2-patch-4#fixed-issues)

### Fixed Issues

Following are the fixed issues in this release.

| Issue ID | Issue Description | Resolution |
| --- | --- | --- |
| 190404 | In the Web Application, the **Asset Usage Type** field was not enabled; however, the API expected this field to be provided, which caused the asset allocation to fail. It displayed 404 Error Message. When the **Asset Usage Type** was passed through the API, the allocation completed successfully. **API** With Asset Usage type: { "ServiceName": "AM_AssetAction", "objCommonParameters": { "_ProxyDetails": { "APIKey": "DN0kp3OV47z0ts3v0sKYYuKrYG2jGPfhld4O+8SwgjI=", "AuthType": "APIKEY", "ProxyID": 0, "ReturnType": "JSON", "OrgID": 1 }, "oAM_Asset_MasterParam": { "_Instance": "IT", "_Asset_ID": 253 }, "oAM_Asset_AllocationParam": { "_AllocateTo": "Single User", "_EmailID":"[Brian.Parker@symphonyai.co](mailto:Brian.Parker@symphonyai.co)", "_Floor_Num":"India\\Bangalore\\5th Floor", "_AllotedDate": "2026-07-22 18:50:00", "_AssetUsageType": "Secondary", "_AllocationType": "Permanent" }, "ActionType": "ALLOCATE", "Remarks": "Allocating laptop to user by API" } } Without Asset usage type: { "ServiceName": "AM_AssetAction", "objCommonParameters": { "_ProxyDetails": { "APIKey": "DN0kp3OV47z0ts3v0sKYYuKrYG2jGPfhld4O+8SwgjI=", "AuthType": "APIKEY", "ProxyID": 0, "ReturnType": "JSON", "OrgID": 1 }, "oAM_Asset_MasterParam": { "_Instance": "IT", "_Asset_ID": 253 }, "oAM_Asset_AllocationParam": { "_AllocateTo": "Single User", "_EmailID":"[Brian.Parker@symphonyai.co](mailto:Brian.Parker@symphonyai.co)", "_Floor_Num":"India\\Bangalore\\5th Floor", "_AllotedDate": "2026-07-22 18:50:00", "_AllocationType": "Permanent" }, "ActionType": "ALLOCATE", "Remarks": "Allocating laptop to user by API" } } | While the Asset Allocation, system does not through any error. If **Asset Usage Type** is not enabled and yet API passing the usage type, then this message is displayed: “AssetUsageType is not enabled at tenant level, remove it from payload.” If **Asset Usage Type** is enabled then asset gets allocated successfully. “Successfully allocated the asset details.” If **Asset Usage Type** is enabled and End User is passing wrong data through API, then the following message is displayed: “Invalid Asset Usage Type.” |
| 190676 | **Knowledge Base (**KB) articles opened from **Global Search** displayed an error page instead of the article content. When users searched for a KB article using **Global Search** and selected the article from the search results, the system displayed the message **"The page encountered an error"** rather than opening the requested KB article. | Users can now open KB articles directly from search results without encountering errors, and the article content is displayed successfully. |
| 191078 | Linked **Configuration Items** (CIs) were not displayed immediately after creating a relationship. Users had to refresh or submit the page before the linked CI count and relationship became visible. | Linked CIs and their relationship count are displayed immediately after creating the relationship, without requiring a page refresh or submission. |