Release Notes Apex Aspen Q3 Patch 1

Prev Next

🎯 Now Live!

Release Date | 4th September 2026

Let’s dive into the key highlights, exciting improvements introduced, and a few known issues to keep an eye on. Every update brings something new, with a focus on enhancing the experience!

The following section provides key highlights and known issues in Apex Aspen Q3 Patch 1 release.

Key Highlights

Our team’s been on the move, polishing the UI and adding smarter functionality to power up your daily grind. Curious about What’s New? Dive in and explore the latest highlights - they are too good to miss!

SDI UI Modernization and AI-Powered Analyst Insights

User Persona: Administrator, Analyst

Smarter Configuration. Sharper Insights. Better Outcomes.

Modernize Service Desk Intelligence with simpler configuration, multi-tenant flexibility, and smarter analyst experiences. SDI now brings configuration and AI-powered recommendations into a streamlined experience—helping administrators configure with less effort and enabling analysts to review, understand, and apply AI recommendations with greater confidence.

Perks at a glance

  • Streamlined Configuration
    A more compact and organized SDI configuration experience.

  • Multi-Tenant Support
    Configure and manage SDI settings across multiple tenants.

  • Greater Flexibility
    Configure SDI independently for individual fields and service areas.

  • Improved Visibility
    Easily track SDI suggestions and see how many have been applied.

  • Consistent Experience
    Clearer labels and a modernized UI make SDI easier to understand and use.

Figure: System Desk Intelligence - Details Page

For more information, refer to Service Desk Intelligence.

Asset Allocation in Mobile Incident Creation

User Persona: End User

Associate assets with incidents effortlessly, even when no asset is assigned.

Asset Allocation is now available on the Mobile App's Log New Incident page, allowing users to associate one or more assets with an incident. Although the field is mandatory, users can bypass it when no asset is allocated to them, ensuring they can submit incidents without unnecessary validation.

Perks at a glance

  • Associate Assets
    Link one or more relevant assets to an incident.

  • Flexible Validation
    Bypass the mandatory field when no asset is allocated to the user.

Figure: Asset Allocation

For more information, refer to Log New Incident.

Simplified Text to Code Configuration

User Persona: Administrator, End User

Simpler setup. Smarter skill generation.

Text to Code configuration is simplified by moving Provider and Model details to the In-App API. Admins now configure the Tenant ID and In App API URL under Application Settings, reducing setup effort and centralizing AI configuration.

Perks at a glance

  • Simpler Text to Code setup:
    Admins only need to enable Text to Code; Provider and Model no longer need to be configured there.

  • Centralized AI configuration:
    Provider and Model details are managed through the In-App API, providing a single source for these settings.

  • Reduced administrative effort:
    Eliminates duplicate or repeated configuration on individual feature pages.

Figure: Text to Code Page

For more information, refer to Text to Code.

Prompt to Report

User Persona: Report Designer

AI-Powered Report and Dashboard Creation.

Create reports and dashboards using simple natural-language prompts, reducing manual configuration and making data easier to analyze.

Perks at a glance

  • Natural-Language Reporting
    Describe your reporting requirement in plain language and let AI interpret the request.

  • Smart Report Discovery
    Find relevant existing reports and dashboards before creating a new one.

  • AI-Guided Creation
    Automatically identify relevant data, generate queries, and recommend suitable chart types.

  • Interactive Refinement
    Review the generated report and refine the requirement using natural language.

  • Report and Dashboard Creation
    Create and preview reports and dashboards using selected visualizations, all through a guided AI experience.

Figure: Prompt to Report

For more information, refer to Prompt to Report.

Mobile App – Change Record Approval

User Persona: Approver

Keep Change Management Moving—Approve CRs on the Go.

Enable authorized approvers to review, approve, reject, or refer back Change Records from the Mobile PWA, helping prevent approval delays and maintain change workflow continuity.

Perks at a glance

  • Mobile Change Approval
    Review and approve pending Change Records directly from a mobile device, without accessing the desktop application.

  • Comprehensive CR Details
    View key change information, including change type, owner workgroup, change initiator, planned start and end times, risks, impact, and approval stages before taking action.

  • Flexible Approval Actions
    Approvers can authorize, reject, or refer back Change Records with appropriate remarks directly from the Mobile PWA.

  • Status-Based CR Management
    Quickly view Change Records based on their approval status, including All, Approved, Pending for Action, Referred Back, and Rejected, helping approvers focus on records requiring attention.


    Figure: Approve Change Records

    For more information, refer to Approve Change Records.

AIW Feature Enhancement

The Product just got smarter with - AIW!

Create Incident with configured Custom attributes from AIW Chat.

Key Highlight

Create Incidents with Configured Custom Attributes from AIW Chat

User Persona: End User

Why spend more time providing missing incident information when AIW can collect the required details during the conversation?

This enhancement enables end users to create incidents with configured Standard and Custom attributes directly from AIW chat. AIW automatically generates the Symptom and Description from the issue prompt and requests values only for the mandatory attributes configured in the tenant’s Log Incident form. This ensures that incidents contain complete and accurate information before submission.

Perks at a glance

  • Tenant-Specific Attribute Collection

    AIW evaluates the tenant’s Log Incident configuration and prompts end users only for the mandatory Standard and Custom attributes required by the organization.

  • Automated Incident Details

    AIW automatically generates the Symptom and Description from the end user’s issue prompt, reducing manual effort and simplifying incident creation.

  • Guided Value Selection

    For mandatory attributes with predefined values, AIW displays the configured options and enables end users to select the appropriate value conversationally.

  • Complete and Accurate Submissions

    AIW prevents incident submission until all mandatory attributes contain valid values, helping service desk teams receive the information required to classify, rank, assign, and resolve incidents.

  • Review Before Submission

    Before creating the incident, AIW presents the generated issue details and collected attribute values for review. End users can update a value conversationally or confirm the information to create the incident.

Figure: AIW Custom Attributes

For more information, refer to Create Incidents with Configured Attributes from AIW Chat.

Fixed Issues

Following issues have been fixed in this release from the previous release:

Bug ID

Description

118574

Duplicate and irrelevant file being considered for incident creation

122440

AIW >Guided Collection Agent >FTUE >Admin Onboarding Agent >> User has only IT Tenant Role template Access but all Tenants Loading where IM Configured.

122778

Apex Aspen Q3 (2026.3.0.0) #20260723.1: Llama >> SDI Feature >AIW suggestion values not appending on incident detail page.

124064

Automation>>Apex Aspen Q3 (2026.3.0.0) #20260802.1 >>IM>> Uploaded attachment names with special/non-English characters are displayed as ????

124071

Apex Aspen Q3 (2026.3.0.0) #20260802.1 > User Dashboard > Response Needed >AI Engine Fails to Recognize Current Ticket Context When Prompted by User

124076

Apex Aspen Q3 (2026.3.0.0) #20260802.1: LAT: 'Yes' and 'No' buttons are not retained in AIW chat after page refresh

124106

Automation>>Apex Aspen Q3 (2026.3.0.0) #20260803.1>>Incident API>>Incident API Returns "Object Reference Not Set to an Instance of an Object" When Symptom Is Empty in Incident Creation Payload

124109

Automation>>Apex Aspen Q3 (2026.3.0.0) #20260803.1>>Incident API>>Incident API Allows Incident Creation Without Mandatory Symptom and Description Fields

124119

Apex Aspen Q3 (2026.3.0.0) #20260803.1: LAT: End User Chatbot Does Not Display the Expected Message After Analyst Ends the Chat

124290

verify Analyst create ticket on behalf of end user

124311

Apex Aspen Q3 (2026.3.0.0) #20260806.1>>Admin>>Discovery>>Inline validation message is not displayed for "Re-enter Password" field on clicking Submit in Monitoring Account Details page

124312

Apex Aspen Q3 (2026.3.0.0) #20260806.1>>Admin>>Custom scheduler>>Jobs are displayed under Custom Scheduler even when the corresponding module is not available in ITSM Summit

124313

Integration Platform : Loop component execution is getting failed.

124325

Apex Aspen Q3 (2026.3.0.0) #20260806.1>> Black border is displayed in the empty area of the My Watchlist grid

124329

Apex Aspen Q3 (2026.3.0.0) #20260806.1>IMS>Incident created instead of call record for ambiguous symptom and description

123808

The notification parser works correctly with configured conditions after the upgrade.

125373

Work order descriptions are displayed correctly without HTML tags for end users.

123899

Known Issues

Following are the known issues in this release:

Bug ID

Description

126692

Apex Aspen Q3 Patch1 (2026.3.0.1) #20260902.2 >>Encountered error message "The page encountered an error. Please refresh and try again." in the total asset count of Consuable asset.

126693

Apex Aspen Q3 Patch1 (2026.3.0.1) #20260902.2>>The page encountered an error. Please refresh and try again. validation message is displayed in My Asset List page.

126672

Mobile app_6.0.31: Mobile App: Mobile App: SAML Authentication Fails with "Oops! An Error Occurred" Message

126348

Apex Aspen Q3 Patch1 (2026.3.0.1) #20260831.1>> Auto Escalation Emails Triggered for Inactive Users.

126417

Apex Aspen Q3 Patch1 (2026.3.0.1)>Change >change : issue >>User is unable to approve/reject the first level Change Request (CR) through the API.

126546

Apex Aspen Q3 Patch1 (2026.3.0.1) #20260902.2>> SR>> User is unable to Approve the Bulk SRs through API

126658

Apex Aspen Q3 Patch1 (2026.3.0.1) #20260903.3>>Issue: The task status is not updating the New after Authorized the CR.

126681

Apex Aspen Q3 Patch1 (2026.3.0.1) #20260904.2 > Call Management->In a specific scenario, Last 5 Calls, Incidents, and Requests are not displayed in the dashboard pop-up, even though the corresponding data exists.

126327

AIW >> Supporting Custom Attribute>> During Analyst Update of an Incident ticket Mandatory Custom Attribute is Not Honoured in AIW.

126576

AIW >> Supporting Custom Attribute>> custom and mandatory attributes are not handled in AIW ticket-creation for other user by analyst.

126680

Automation>> CTP to Q3 >>Apex Aspen Q3 Patch1 (2026.3.0.1) #20260904.2>>IM API>>SLA Service Window>>SLA created successfully via API on tenant without IM config — visible in GET list but not in UI

124310

Automation>>Apex Aspen Q3 (2026.3.0.0) #20260806.1>>IM API>>Category>>Category validation is inconsistent between UI and API, allowing invalid operations

125561

Apex Aspen Q3 Patch1 (2026.3.0.1) #20260819.1>(Mobile Version 6.0.31.)>The selected assets are not retained when the user reopens the Asset Allocation page.

106689

Automation>>ELBRUS SP3 HF11 B070 Patch16 & Apex Aspen Spring #20260323.1 >>Saved custom attribute value is not retained in AD Import record

126684

Apex Aspen Q3 Patch1 (2026.3.0.1) #20260904.3>>After User Accept/Reject the Reconciliation Asset still the status is not changed to Accepted/Rejected in Asset Reconciliation page. (Asset Mails are not getting parsed)

126649

Apex Aspen Q3 Patch1 (2026.3.0.1) #20260903.3: The dashboard created by user 1 is displayed in the User 2 P2R chat, when clicked on it, the error is displayed.

126215

Apex Aspen Q3 Patch1 (2026.3.0.1) #20260829.2: Observed that some time single user input is showing duplicate time.

126237

Apex Aspen Q3 Patch1 (2026.3.0.1) #20260829.2: received duplicate response from chat bot

126364

Apex Aspen Q3 Patch1 (2026.3.0.1) #20260901.1: Chat bot has no response and requested column addition is not as expected in query.

126614

NFR - im_ticket_information table OOM killed Issue

126619

NFR - mart_cm_approval_action_details OOM Killed issue

126648

Apex Aspen Q3 Patch1 (2026.3.0.1) #20260903.3> Reports > Dashboard displays errors when loading chart elements while editing.

125543

Automation>>Apex Aspen Q3 Patch1 (2026.3.0.1) #20260819.1>>Incident>>Inconsistency>>AI Recommendations popup can be dragged/moved and does not close using the Esc key

124246

Auto assignment feature is not working as expected

126027

Apex Aspen Q3 Patch1 (2026.3.0.1) #20260826.2>Mobile Version 6.0.31>Approve CRs>Unable to Authorize, Authorize & Forward, or Put on Hold

126274

LI and Knowledge record pipeline is failing

126660

Reporting api is not working : PR and SDI UI is unavailable.

114928

Apex Aspen Q2 (2026.2.2.1) #20260609.1: The Search asset is showing no data when software asset is searched by license name.

120815

Apex Aspen Winter (2026.1.3.10) #20260710.2: Service Request: Browser Tab Title Is Inconsistent (details page) with Other Modules like IM, CM and CMDB

124172

Apex Aspen Q3 (2026.3.0.0) #20260728.1>>RTL Bulletin Direction is Incorrect

125938

Apex Aspen Q3 Patch1 (2026.3.0.1) #20260823.1 >> Global search is not working, when searched with valid ticket ID

126286

IMS>>https://qamanualctp2q3patch.symphonyaiapexdev.com/>> SR not creating, Many mails getting stuck and Status always showing Failed.

118765

Workflow Engine : When Notification is triggered due to an Error, then in the triggered email the Mail Body is not rendered as configured. Instead, its merged and shown in single line.

126666

Apex Aspen Q3 Patch1 (2026.3.0.1) #20260903.3: Discovery > Discovery Scan Status Changes to Error If .\ Is Not Provided in Domain Field

117776

Workflow Engine : When multiple components are placed inside 'Error Handler' component and if connected, then the connections are placed outside the 'Error Handler' boundary.

Security Enhancements

Note

Security enhanced by performing Vulnerability and Acceptance Penetration Testing (VAPT). This has hardened the Apex Application security layer.