- 31 Mar 2025
- 18 Minutes to read
- Print
- PDF
Release Notes Crescendo (6.3)
- Updated on 31 Mar 2025
- 18 Minutes to read
- Print
- PDF
The following section provides key highlights, improvements introduced and known issues in Apex Crescendo (6.3) release.
Upgrade .Net Framework to version 8.0 (for Apex Crescendo 6.3.0 Patch 5 Release)
For Apex Crescendo 6.3.0 Patch 5 Release (March 5, 2025), ensure you upgrade the .NET Framework to version 8.0. Ensure that the latest Hosting Bundle (8.0.13) is installed on all application servers. After installation, restart IIS. The Crescendo v6.3.0 patch 5 requires the latest hosting bundle to function correctly.
Download the necessary files from the Microsoft site: https://dotnet.microsoft.com/en-us/download/dotnet/8.0.
Merged Releases
Updates till the following releases have been merged into Crescendo (6.3) Release:
Merged all releases up to: v6.1.0.1 HF10 B025 Patch 9 to Crescendo 6.3.0
Notes
The Offline translation mode supports Localization from the base language English to Arabic and French.
The support resolution for mobile and laptop are:
Mobile - Small screen - 320 pixels(px)
Laptop - Large screen - 1920 pixels(px)
New Features
Platform Studio
Let's take a quick look at our Platform Studio user persona.
The following section provides a sneak-peek of the functionalities added for Platform Studio.
Design Studio
Let's take a quick look at our Design Studio user personas.
The following section provides a sneak-peek of the functionalities added for Design Studio.
Applications
The following section provides key highlights and Application-wise description of new features introduced in Apex Release.
Service Management
Let's take a quick look at our Service Management user personas.
The following section provides a sneak-peek of the functionalities added for Service Management.
Apex Mobile
Let's take a quick look at our Apex Mobile user persona.
The following section provides a sneak-peek of the functionalities added for Apex Mobile.
Improvements
The following are new enhancements added in Crescendo (6.3):
Platform
Element | Improvement Name | Description |
---|---|---|
Top panel | Approvals and Notifications | The approval and notification icons are displayed in both Service Management and Asset Management applications, with approval notifications filtered by the selected application, while general notifications span all applications. For more information, refer Dashboard. |
Design Studio
Element | Improvement Name | Description |
---|---|---|
Notification Parser | Language Support for Parsed Emails | In a Mailbox configured with Parse Rules and for the emails forwarded, the Subject Tag takes effect according to the local language through Outlook. For more information, refer Notification Parser. |
Scheduler | Notify Recipient for MSP Customers | The Notify Recipients functionality for Managed Service Provider (MSP) customers is used to automate alerts or updates about scheduled tasks, jobs, or maintenance events. This functionality can be customized based on the specific needs of MSP customers. For more information, refer Scheduler. |
Business Rule Designer | Notify Recipient for MSP Customers | With the Notify Recipients feature, Managed Service Provider (MSP) customers can streamline the delivery of automated updates for tasks, jobs, or maintenance schedules. This capability can be personalized through the Business Rule Designer to align with the distinct needs of each MSP, enabling seamless communication. For more information, refer Business Rule Designer. |
Notification Parser | Subject Tag(s) introduced as Actions in Notification Parser. | Subject Tag(s) is mandatory in Notification Parser as an Action to ensure if parsed mails are included with tags in the Subject field when Forwarded or Responded. For more information, refer Notification Parser Actions. |
Mobile App
Element | Improvement Name | Description |
---|---|---|
Apex Mobile | The Analyst and Approver personas have been enabled. | In the Apex Mobile, all Analyst and Approver personas have been enabled for the End User. |
Known Issues
The following section provides details of known issues in this release:
Issue ID | Issue Description | Scenario | Workaround |
---|---|---|---|
75767 | The Service Portal record count next to the tenant shows (N+1) when N records are displayed on the list page. | Prerequisite: Assets must be displayed in the following statuses: "Instore," "Allocated," "Reactivated," and "Deactivated." Steps:
| N/A |
69099 | When we click on Change History button in Workgroup, the values are not translated to 'Arabic' language. | Steps:
| N/A |
60792 | The Analyst is unable to select the count, and values are not displaying properly. | Prerequisite: Bulk Update must be configured on Design List View Page of under Actions section of Form Designer. Steps:
| N/A |
46968 | In the Themes list page, the system-defined Themes do not display. | Prerequisite: Create few Themes for a Sub Domain and Role Template access should be given for more than one Sub Domain. Steps:
| N/A |
61077 | When a template is applied, the values are not populated for the Tree View control type initially. However, after saving the record, the values are populated correctly. | Prerequisite: Import Template utility must be configured. Steps:
| N/A |
59436 | Uploaded image was not retained under the Header section of added Panel. | Steps:
| N/A |
76487 | When a user clicks the Service Automation application, the system displays a System Under Maintenance error and tries to open the Analyst Dashboard. | Steps:
| N/A |
Fixed Issues
The following section provides details of Fixed issues in this release:
Issue ID | Issue Description | Scenario | Resolution |
---|---|---|---|
168271 (Patch 6) | While performing User Role Mapping, in the "Publish To" step, the dropdown values for Category attribute was not loading values properly. | Steps:
| Values for Category attribute in the User Role Mapping > Publish step, are populating without any issues. |
165703 | Manage Incident Page was displaying blank without any Incidents. | Steps:
| Manage Incident Page is displaying all Incidents as expected. |
165698 | SLA values were not being updated even if the SLA conditions were met. | Steps:
| SLA values are being updated if SLA conditions are met. |
165405 | The analysts were unable to view the encrypted text in the text box control of the Service Request module. | Prerequisites:
Steps:
| The analysts can view the encrypted text in the text box control of the Service Request module. |
165280 | When the multi Grp data under the MV1 field was updated and saved in the Catalog for the Service Request, an error message was displayed. | Prerequisite: Create a Service Catalog. Steps:
| When the multi Grp data under the MV1 field is updated in the Catalog, the Service Request is successfully saved. |
165699 | The Workgroup and Analyst fields in Manage Service Requests were showing blank values. | Steps:
| The Workgroup and Analyst fields display appropriate values in the Manage Service Request page. |
164327 (Patch4) | Post-upgrade, the API configuration was missing from the Mailbox Configuration feature. | Steps:
| The API configuration is displayed without any issue. |
162641 | Due to lazy load in the Change Management module, only a few statuses were loading. | Steps:
| The statuses are now loading appropriately in the Change Management module. |
161645 | For the Change Management module, the Hyperlink label was not getting displayed as mentioned in the Label field, in the triggered email. | Steps:
| For the Change Management module, the Hyperlink label is getting displayed as mentioned in the Label field, in the triggered email. |
166399 | The Data Source tab on the Status configuration page of the Manage Change Request page was not functioning properly. | Steps:
| The Data Source tab on the Status configuration of the Manage Change Request page functions well. |
165462 (Patch4) | The OTKA AD import user pagination was not working during the API chaining with the next page. | Prerequisite: The OKTA AD import must have more than 200 users. Steps:
| The OKTA AD import user pagination is working as expected. |
165326 (Patch4) | The left menu remained open and did not collapse, even after moving the cursor outside of it. | Steps:
| The left menu does not remain open and getting collapsed after moving the cursor outside of it. |
166215 (Patch4) | In the Add Master Value step of Common Master, an error message was displayed while the Active toggle of the Master Value was updated. | Steps:
| The Active toggle functions as expected while updating in the Add Master Value step of Common Master module. |
166943 (Patch4) | Clicking on linked records redirected users to the Home page. | Prerequisite: Create a new Incident, go to the Links tab, and add a record. Steps:
| Linked records are now displayed through the Links tab of Manage Incidents. |
166145 | Incident ticket hyperlink was not displaying correctly in the email notification. | Steps:
| Incident ticket hyperlink is working as expected in the email notification. |
1570 | Awaiting Approval label was not completely displayed in the mobile application. | Steps:
| Awaiting Approval label is displayed accurately in the mobile application. |
167671 (Patch 5) | On the Apex Mobile, the Search Box and the Search icon were not aligned on the CR list page. | Steps:
| The Search Box and the Search icon are aligned appropriately on the CR list page. |
165492 (Patch 5) | On the Manage Change Request details page, the Assigned Change Manager field value was not displayed according to the validation controls in the General tab. | Prerequisites:
Steps:
| The Assigned Change Manager field value is displayed based on the validation controls in the General tab of the Manage Change Request details page. |
166729 (Patch 5) | When attempting to add fields in Multivalued Group, fields appeared blank. Once the form is saved, it displayed the following message: “No data to display.” | Steps:
| When attempting to add fields in Multivalued Group, fields do not appear blank. Once the form is saved, it does not display any message. |
167655 (Patch 5) | In the API Explorer, when values for manager_id and email_id were passed, the application threw an error. | Prerequisite: The User List must be having user data. Steps:
| The values are passed successfully without any error in the API Explorer. |
167655 (Patch 5) | In the API Explorer, the application displayed an unauthorized error message when a cloned subform was used. | Prerequisite: A cloned sub form with all the mandatory details must be created. Steps:
| A cloned sub form can be used to create an API successfully. |
167168 (Patch 6) | Users were experiencing an error message while updating a newly created request through a Catalog. | Prerequisites:
Steps:
| Users are not experiencing error message while updating a newly created request through a Catalog. |
168230 (Patch 6) | The Workgroup field was blank after submitting or approving the Service Request. | Steps:
| The Workgroup field shows the selected workgroup for the Service Request. |
165266/164811 (Patch 6 and 7) | Email notifications were triggered in the Change Management module with incorrect subject lines. | Prerequisites:
Steps:
| Appropriate email notifications are triggered in the Change Management module. |
167288 (Patch 6) | The Business Rule was not executing, displayed a failed status for each event. | Steps:
| The Business Rule is getting executed successfully and does not display any failed status for the event. |
153220 (Patch 6) | When configuring workflows for Change Management, the user faced issues under User Approval. | Steps:
| The User Approval under workflows works successfully without any issues. |
167667 (Patch 6) | On the Apex Mobile, the Search Box and the image were not aligned appropriately. | Steps:
| The Search Box and the image are aligned appropriately. |
168860 (Patch 7) | After upgrade, the Manage Change Record list page was not displaying the list of records. It appeared blank. | Steps:
| After upgrade, the Manage Change Record list page displays the list of records. |
166085 (Patch 7) | For Role-Based Approvals, the owner workgroup was not mapped as an approver in the Workflow Designer. | Steps:
| In Role-Based Approvals, the owner workgroup is mapped as an approver in the Workflow Designer. |
169072 (Patch 7) | Validation errors occurred when the user tried to fetch an SR record through the GET Request using API. This issue occurred when the SR record was fetched from a cloned Form. | Steps:
| The API fetches details of the SR created from a cloned Form and displays on the Response window successfully. |