Let’s dive into the key highlights, exciting improvements introduced, and a few fixed issues to keep an eye on. Every update brings something new, with a focus on enhancing the experience!
The following section provides fixed issues and improvements in Apex Aspen Q2 (2026.2.3.0) release.
Prerequisites
The following updates outline key actions for the new Workflow Engine across PM, KM, and IM modules.
Notes
New Workflow Engine has been introduced for Problem Management (PM), Knowledge Management (KM), and Incident Management (IM). Complete all pending approvals in these modules before upgrading.
For PM and KM, the default workflows will be available in Draft state. Administrators must review, publish, and deploy these workflows. For more information, refer to Workflow.
After deployment, raise new requests in KM and PM using the deployed workflows.
If a custom workflow is configured for the IM module, refer to the IM approval configuration and replicate it in the new Workflow Engine. For more information, refer to Workflow.
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!
Change Management Report
Introduced Change Record Schedule report to provide a centralized calendar-based view in the Change Management.
Change Record Schedule Report
User Persona: End User / Analyst
What if you could visualize every planned, approved, and completed change in a single calendar view? With the Change Record Schedule report, you can!
The Change Record Schedule report provides a centralized calendar-based view of all planned, approved, and completed changes. It enables IT and business teams to efficiently monitor schedules, track implementation timelines, and coordinate change activities across the organization.
✅ Perks at a glance
Centralized Change Visibility
View all planned, approved, and completed changes from a single calendar-based interface for improved schedule monitoring and operational awareness.Multiple Calendar Views
Analyze change schedules using flexible viewing options including Day, Week, Month, and Agenda views based on business and operational requirements.Advanced Filtering Capabilities
Quickly identify and refine change records using flexible filters to simplify schedule tracking and reporting.Increased Implementation Success
Enhance execution efficiency through better change planning, tracking, and schedule management.Change Record Schedule screenshot
Figure: Change Record Schedule
For more information, refer to Change Record Schedule report.
Improvements
Following are the improvements in this release.
Improvement Name | Description | Benefits |
|---|---|---|
Effort Tracking using Manual and Stop Watch entry. User Persona: Administrator / Analyst | Introduces dual effort tracking modes allowing users to either manually enter effort values or automatically capture effort using a start/stop timer. Manual entry supports external tracking and bulk updates, while stopwatch-based tracking ensures real-time, system-calculated effort logging within tickets. For more information, refer to this page. |
|
Fixed Issue
Following are the fixed issues in this release.
Issue ID | Issue Description | Resolution |
|---|---|---|
188575 | The system displayed a validation message indicating that the Work Order already existed when creating or updating a Work Order with an existing name under a different category. The system also prevented updates to an existing Work Order within the same category due to incorrect duplicate name validation. | The Work Order name validation logic now allows creation of Work Orders with the same name under different categories and permits updates to existing Work Orders within the same category without incorrectly triggering duplicate name validation. |
109175 | The following issues related to report authorization and access restriction handling were addressed:
| Both the issue are addressed and its working as designed:
|
112042 | An error was displayed even though the user email existed in the User Profile, and the issue continued after refreshing the chat or re-logging into the application. | The user profile validation and session handling logic are working as designed. |
112258 | The alignment was not centered, and the component height exceeded the configured height of 40px, resulting in inconsistent display behavior. | The styling has been updated to ensure proper center alignment and to maintain the component height within the configured 40px limit. |
Note
If the page appears blank or the reporting screen is not visible, clear the browser cache and history.