---
title: "Release Notes Crescendo (6.3)"
slug: "release-notes-crescendo-63"
updated: 2026-08-17T06:01:45Z
published: 2026-08-17T06:01:45Z
canonical: "help.symphonysummitai.com/release-notes-crescendo-63"
---

> ## 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 Crescendo (6.3)

> [!NOTE]
> 🎯 Now Live!
> 
> **Release Date | 25th January 2025**

The following section provides key highlights, improvements introduced and known issues in Apex Crescendo (6.3) release.

- [Merged Releases](/summit-platform/docs/release-notes-crescendo-63#merged-releases)
- [New Features](/summit-platform/docs/release-notes-crescendo-63#new-features)
- [Improvements](/summit-platform/docs/release-notes-crescendo-63#improvements)
- [Known Issues](/summit-platform/docs/release-notes-crescendo-63#known-issues)
- [Fixed Issues](/summit-platform/docs/release-notes-crescendo-63#fixed-issues)

> [!NOTE]
> 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.](https://dotnet.microsoft.com/en-us/download/dotnet/8.0.)
> - For GDPR - MSSQL Server Standard Edition 2022 and above

## 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

> [!NOTE]
> 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.

| ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Super Admin.png?sv=2026-02-06&spr=https&st=2026-10-31T11%3A19%3A13Z&se=2026-10-31T12%3A19%3A13Z&sr=c&sp=r&sig=xV6cfq3Iw%2Bu%2Fvss%2BTz176vLKRkGWz8eP92fy4%2F2RFes%3D) |
| --- |

The following section provides a sneak-peek of the functionalities added for Platform Studio.

| [![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Crescendo 6.3 RN Cards (1).png?sv=2026-02-06&spr=https&st=2026-10-31T11%3A19%3A13Z&se=2026-10-31T12%3A19%3A13Z&sr=c&sp=r&sig=xV6cfq3Iw%2Bu%2Fvss%2BTz176vLKRkGWz8eP92fy4%2F2RFes%3D)](https://help.symphonysummitai.com/summit-platform/docs/customer-crescendo) |
| --- |

### Design Studio

Let's take a quick look at our Design Studio user personas.

| ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Application Designer.png?sv=2026-02-06&spr=https&st=2026-10-31T11%3A19%3A13Z&se=2026-10-31T12%3A19%3A13Z&sr=c&sp=r&sig=xV6cfq3Iw%2Bu%2Fvss%2BTz176vLKRkGWz8eP92fy4%2F2RFes%3D) |
| --- |

The following section provides a sneak-peek of the functionalities added for Design Studio.

| [![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Notification Designer(2).png?sv=2026-02-06&spr=https&st=2026-10-31T11%3A19%3A13Z&se=2026-10-31T12%3A19%3A13Z&sr=c&sp=r&sig=xV6cfq3Iw%2Bu%2Fvss%2BTz176vLKRkGWz8eP92fy4%2F2RFes%3D)](https://help.symphonysummitai.com/summit-platform/docs/clone-hyperlink-crescendo) | [![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Send Email.png?sv=2026-02-06&spr=https&st=2026-10-31T11%3A19%3A13Z&se=2026-10-31T12%3A19%3A13Z&sr=c&sp=r&sig=xV6cfq3Iw%2Bu%2Fvss%2BTz176vLKRkGWz8eP92fy4%2F2RFes%3D)](https://help.symphonysummitai.com/summit-platform/docs/send-email-crescendo) | [![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-PHGCJX26.png?sv=2026-02-06&spr=https&st=2026-10-31T11%3A19%3A13Z&se=2026-10-31T12%3A19%3A13Z&sr=c&sp=r&sig=xV6cfq3Iw%2Bu%2Fvss%2BTz176vLKRkGWz8eP92fy4%2F2RFes%3D)](https://help.symphonysummitai.com/summit-platform/docs/configure-localization-crescendo) |
| --- | --- | --- |

## Applications

The following section provides key highlights and Application-wise description of new features introduced in Apex Release.

- [Service Management](/summit-platform/docs/release-notes-crescendo-63#service-management)
- [Apex Mobile](/summit-platform/docs/release-notes-crescendo-63#apex-mobile)

### Service Management

Let's take a quick look at our Service Management user personas.

| ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Analyst(3).png?sv=2026-02-06&spr=https&st=2026-10-31T11%3A19%3A13Z&se=2026-10-31T12%3A19%3A13Z&sr=c&sp=r&sig=xV6cfq3Iw%2Bu%2Fvss%2BTz176vLKRkGWz8eP92fy4%2F2RFes%3D) | ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/End User(1).png?sv=2026-02-06&spr=https&st=2026-10-31T11%3A19%3A13Z&se=2026-10-31T12%3A19%3A13Z&sr=c&sp=r&sig=xV6cfq3Iw%2Bu%2Fvss%2BTz176vLKRkGWz8eP92fy4%2F2RFes%3D) |  |
| --- | --- | --- |

The following section provides a sneak-peek of the functionalities added for Service Management.

| [![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-MFBTVPZA.png?sv=2026-02-06&spr=https&st=2026-10-31T11%3A19%3A13Z&se=2026-10-31T12%3A19%3A13Z&sr=c&sp=r&sig=xV6cfq3Iw%2Bu%2Fvss%2BTz176vLKRkGWz8eP92fy4%2F2RFes%3D)](https://help.symphonysummitai.com/summit-platform/docs/wo-status-by-location) | [![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-GFGEIG33.png?sv=2026-02-06&spr=https&st=2026-10-31T11%3A19%3A13Z&se=2026-10-31T12%3A19%3A13Z&sr=c&sp=r&sig=xV6cfq3Iw%2Bu%2Fvss%2BTz176vLKRkGWz8eP92fy4%2F2RFes%3D)](https://help.symphonysummitai.com/summit-platform/docs/service-management-1) |  |
| --- | --- | --- |

### Apex Mobile

Let's take a quick look at our Apex Mobile user persona.

| ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-1719408795505.png?sv=2026-02-06&spr=https&st=2026-10-31T11%3A19%3A13Z&se=2026-10-31T12%3A19%3A13Z&sr=c&sp=r&sig=xV6cfq3Iw%2Bu%2Fvss%2BTz176vLKRkGWz8eP92fy4%2F2RFes%3D) |
| --- |

The following section provides a sneak-peek of the functionalities added for Apex Mobile.

| [![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Apex Mobile_analyst.png?sv=2026-02-06&spr=https&st=2026-10-31T11%3A19%3A13Z&se=2026-10-31T12%3A19%3A13Z&sr=c&sp=r&sig=xV6cfq3Iw%2Bu%2Fvss%2BTz176vLKRkGWz8eP92fy4%2F2RFes%3D)](https://help.symphonysummitai.com/summit-platform/docs/apex-mobile) |
| --- |

## Improvements

The following are new enhancements added in Crescendo (6.3):

- [Platform Studio](/summit-platform/docs/release-notes-crescendo-63#platform)
- [Design Studio](/summit-platform/docs/release-notes-crescendo-63#design-studio)
- [Mobile App](/summit-platform/docs/release-notes-crescendo-63#mobile-app)

### Platform Studio

| 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](https://help.symphonysummitai.com/summit-platform/docs/crescendo-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](https://help.symphonysummitai.com/summit-platform/docs/overview-crescendo). |
| 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](https://help.symphonysummitai.com/summit-platform/docs/overview-scheduler-crescendo). |
| 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](https://help.symphonysummitai.com/summit-platform/docs/overview-businessrule-crescendo). |
| 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](https://help.symphonysummitai.com/summit-platform/docs/actions-crescendo). |

### Mobile App

| Element | Improvement Name | Description |
| --- | --- | --- |
| Apex Mobile | The **Analyst** and **Approver** personas have been enabled. User Persona: End User | In the Apex Mobile, all Analyst and Approver personas have been enabled for the End User. For more information, refer to [Apex Mobile](https://help.symphonysummitai.com/summit-platform/docs/apex-mobile). |

## 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:** 1. Navigate to **Service Management** > **Design Studio** > **Application** > **Service Portal**. The service portal list page is displayed. 2. Click on any **Tenant** to verify the count of the records. | N/A |
| 69099 | When we click on **Change History** button in **Workgroup**, the values are not translated to 'Arabic' language. | **Steps:** 1. Navigate to **Design Studio** > **Application** > **Workgroup**. The **Workgroup** list page is displayed. 2. Select an existing **ID** from the list page. 3. Click the **Change History** icon from the top panel. The drop-down values are not translated to Arabic language. | 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:** 1. Log in to the Apex application as an Analyst. 2. Click **Bulk Update** icon. 3. Select the Incident IDs which needs to get bulk updated. 4. Click **Bulk Update**. The **Bulk Update** pop-up gets displayed. 5. Click **Field** drop-down and select the Field. 6. Click **Apply**. | 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**: 1. Log in to the Apex application as an **Admin**. 2. Navigate to the **Settings** icon > **Application** tab > **Themes**. | 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**: 1. Log in to the Apex Application as an Analyst. 2. Select **Service Management** application. 3. Navigate to **Incident** > **Manage Incidents**. The **Manage Incidents List** page is displayed. 4. Click **New**. Choose **Use Templates** option. The **Import Template** pop-up is displayed. 5. Choose the template and click **Apply**. The selected template will be applied. 6. Verify whether the value is populated for the **Tree View** control type. | N/A |
| 59436 | Uploaded image was not retained under the Header section of added Panel. | **Steps**: 1. Login to the Application as an Application Designer. 2. Navigate to **Design Studio** > Select **Module** > **Form Designer** > **New**. 3. Enter the details in all the steps and in the **Design Form** step drag and drop the **Panel**. 4. Click on gear icon and go to **Appearance** tab. 5. Under **Header** section, select the B**ackground Type** as **Image** and Upload the Image. 6. Click on **Save**, configuration must be saved successfully. 7. Submit the form and uploaded image under **Header** section of the **Panel**. | 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:** 1. Log in to the Apex application. 2. Click **Service Automation** application. 3. Verify whether the **Service Automation** page opens. 4. On the **Service Automation** page, click the![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-VQ9OFXYZ.png?sv=2026-02-06&spr=https&st=2026-10-31T11%3A19%3A13Z&se=2026-10-31T12%3A19%3A13Z&sr=c&sp=r&sig=xV6cfq3Iw%2Bu%2Fvss%2BTz176vLKRkGWz8eP92fy4%2F2RFes%3D)**Home** icon. 5. Click the **Service Management** application. 6. In the top panel, open **Service Management** dropdown, and select **Service Automation**. 7. The **Service Automation** page display the menu and the dashboard name from **Service Management**. | 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:** 1. Log in to the Apex application as an Application Admin. 2. Click **Settings > Design Studio**. 3. **From the Application tab in the left navigation panel, expand Access Control Center > User Role Mapping. The User Role Mapping list page is displayed.** 4. Click on **ID** of one of the User Role Mapping to edit it. 5. Click the **Publish To** step. 6. Click on **+ icon** to Add New filter set. 7. In the **Field Set** drop-down, type **Designation** and select Operator as ‘is’. 8. Check the Value drop-down. | 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:** 1. Log in to Apex application as an Analyst. 2. Navigate to **Incident** > **Manage Incidents.** 3. Validate if the **Manage Incident** page displays all Incidents. | Manage Incident Page is displaying all Incidents as expected. |
| 165698 | SLA values were not being updated even if the SLA conditions were met. | **Steps:** 1. Log in to the Apex application as an Application Designer. 2. Select the application as Service Management. 3. Select the required module. 4. Navigate to SLA Designer and configure the SLA conditions. 5. Raise one SR as an End User 6. Log in to the application as an Analyst and observe if SLA values are updated based on SLA condition. | 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:** 1. A **Text** box control must be configured, and encryption must be activated. 2. Create an SR with encrypted text in the text box control. **Steps:** 1. Log in to the Apex application as an Analyst. 2. Navigate to **Service Management** > **Service Request** > **Manage Service Requests**. The **Manage Service Requests** list page is displayed. 3. Open the previously created SR and verify the data in the text box control. | 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:** 1. Log in to the Apex application as an Analyst . 2. Navigate to **Service Request** > **My Service Request**. The **My Service Request** List page is displayed. 3. Click **New**. 4. Search for the created Catalog. The Catalog is displayed. 5. Click **View** **Detail**. The Catalog details are displayed. 6. Under **Specifications**, select **MV1**, choose **multi Grp** and enter **Remarks**. 7. Click **Save**. | 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:** 1. Log in to the Apex application as an Analyst. 2. Navigate to **Requests** > **Manage Service Requests**. The **Manage Service Requests** list page is displayed. 3. Click **ID** to open an existing Service Request. 4. Navigate to the **Assigned To** tab. The **Workgroup** and **Analyst** fields are blank. | 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**: 1. Log in to the Apex application. 2. Navigate to the **Settings** icon > **Design Studio > Application tab** > **Mailbox Configuration**. 3. On the **Mailbox Configuration** list page, click **MAILBOX ID** hyperlink to view the record details. 4. Click **Next** to proceed to the Configuration step. | 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**: 1. Log in to the Apex application as an **Analyst**. 2. Navigate to **Service Management** > **Change** > **Manage Change Requests**. The **Manage Change Requests** list page is displayed. 3. Click and open a **CR ID** hyperlink. 4. Select the status of the change request from the dropdown. | 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:** 1. Log in to the Apex application as an Application Designer. 2. Select the module as Change Management. 3. Configure the hyperlink label field while configuring the notification email. | 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:** 1. Log in to the Apex application as an Application Designer. 2. Navigate to **Design Studio** > **Module** > **Form Designer**. 3. Click **Manage Change Record**. 4. Navigate to **Design Form** > **Status**. 5. Click **Status** and edit the **Settings**. 6. Navigate to the **Data Source** tab. | The **Data Source** tab on the **Status c**onfiguration 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:** 1. Navigate to **Service Management** > **Design Studio** > **Module** > **API Configuration**. The API Configuration list page is displayed. 2. Select the **Domain** and **Sub Domain**. Click **New**. 3. Select the **API Group Name** as **OKTA Active Directory**. 4. In the **API Details** tab, API Get URL should be configured with (?limit=1) in the **URL** field and save the configuration with other mandatory fields. 5. Run the job and verify the imported users. | 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:** 1. Log in to the Apex application as an Analyst. 2. Select the application as **Service Management**. 3. Navigate to the **Analyst Dashboard**. 4. Select the application as **Service Management**. 5. Hover the mouse over the left menu. 6. Move the cursor outside the left menu. 7. Observe the behavior of the left menu. | 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:** 1. Log in to the Apex application. 2. Click the gear icon and select **Platform Studio**. 3. Under **Platform Master**, navigate to Common **Master Value**. 4. In the List View page, choose the **Master Type** from the dropdown menu, then click **Add Master Value**. 5. In the **Add Master Value** step, enter all the mandatory details. 6. By default, the **Active** toggle button is enabled, toggle it off to disable. | 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:** 1. Log in to **Apex** as an Analyst. 2. Navigate to **Incident** > **Manage Incidents**. The **Manage Incidents** list page is displayed. 3. Click the **ID** of the record created. 4. Navigate to the **Links** tab and click the linked record **ID**. 5. The page is redirected to the home page. | Linked records are now displayed through the **Links** tab of **Manage Incidents**. |
| 166145 (Patch 5) | Incident ticket hyperlink was not displaying correctly in the email notification. | **Steps**: 1. Log in to the Apex Application as an Analyst. 2. Navigate to **Analyst Dashboard** > **Incident** > **Manage Incident**. 3. Open any ticket. 4. Select **Send Email** option. 5. Select any notification template to send email. 6. Validate on the email if Hyperlink is functioning as expected. | Incident ticket hyperlink is working as expected in the email notification. |
| 1570 (Patch 5) | **Awaiting Approval** label was not completely displayed in the mobile application. | **Steps**: 1. Log in to the Apex Mobile as an **Analyst**. 2. Click the **Hamburger Menu** icon and navigate to **Change** > **Change Request** > **Manage Change Record**. The **Manage Change Record page** is displayed. 3. Verify the display of **Awaiting Approval** label. | **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**: 1. Log in to the Apex Mobile as an **Analyst**. 2. Click **Hamburger Menu** icon and navigate to the **Change** > **Change Request** > **Manage Change Record**. The Manage Change Record page is displayed. | 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:** 1. Create a new **Change Record**. 2. Ensure the **Status** of the **Change Record** is set to **Pending Requirements**. 3. On the **Manage Change Record** details page, select **Standard** from the **Change Type**. 4. In the **Import Template**, select **145 All (Core) Small Infra template** and click **Apply**. **Steps:** 1. Log in to the Apex application as an End User. 2. Navigate to **Change** > **My Change Request**. The **Change Record** List page is displayed. 3. Click the **CR ID** hyper link with the **Pending Requirements** status. 4. Change the **Status** from **Pending Requirements** to **Requirements Definition**. 5. Verify the **Assigned Change Manager** **Name** under **General** tab. 6. Click **Save**. | The **Assigned Change Manager** field value is displayed based on the validation controls in the **General** tab of the **Manag**e **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:** 1. Log in to the Apex application as an Application Designer. 2. Create a Sub Form and add the multivalued group. 3. Publish the form. 4. Log in to the application as an End User and navigate to the **My Service Request** page and click **New**. 5. Select the Sub Form, add the multivalued fields, and save the form. | 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**: 1. Log in to the Apex application as an Administrator. 2. Navigate to **Service** **Management** > **Platform** **Studio** > **API** **Hub** > **Explorer**. The **Explorer** page is displayed. 3. Click **Update** **a** **Record (PUT)** and enter the **Query** **Parameters** to be updated. 4. In the **Request** **Body** section, click **Add a Field**. Add the required fields and values. Click **Submit**. | 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**: 1. Log in to the Apex application as an Administrator. 2. Navigate to **Service** **Management** > **Platform** **Studio** > **API** **Hub** > **Explorer**. The **Explorer** page is displayed. 3. Select **Create Record (POST)**. 4. Select the subform created in the **Form** **Name** field. Enter all the mandatory details. 5. In the **Request** **Body** section, click **Add** **a** **Field**. Add the required fields and values. Click **Submit**. 6. Click **Send** to create the API. | 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:** 1. Log in to the Apex Application as an Application Designer. 2. Navigate to **Design Studio** > **Service Request** > Select Sub Form (Catalog). 3. Go to **Publish** step and change the Form to **Maintenance** and click **Submit**. 4. Configure attachment control for the Catalog form. 5. **Publish** the Form. **Steps:** 1. Log in to the Apex Application as an End User. 2. Navigate to **Service Request** > **My Service Requests**. 3. **My Service Requests – List** page is displayed. 4. Create Service Request with same the Catalog. 5. Log in as an Analyst. 6. Navigate to **Service Request** > **Manage Service Requests**. 7. **Manage Service Requests – List** page is displayed. 8. Click the **SR ID** created by the End User. 9. **SR Details page** is displayed. 10. Update the Service Request. 11. Observe for any errors message. | 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. | **Prerequisites**: 1. Business Rule must be configured for routing Service Requests to the workgroups. **Steps**: 1. Log in to the Apex application as an Analyst. 2. Navigate to **Service Management** > **Service Request** > **Manage Service Requests**. The **Manage Service Requests** list page is displayed. 3. Click **New** to create a Service Request. Enter all the mandatory details and **Save**. 4. The Approver must approve the service request. | 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**: 1. Configure multiple statuses such as Unsubmitted, Requirement Submitted, Requirement Approval, and Requirement Approved. 2. Configure business rules for notification status: Requirement Approval and Requirement Approved. 3. Configure Workflow for approving the change record with the conditions: - When the Status is **Requirement Approval**, an activity called **Set Value** is triggered, which updates the Status to **Requirement Approved**. - When the Status is **Requirement Submitted**, Workflow updates the Status to **Requirement Approval**. **Steps**: 1. Log in to the Apex application as an Analyst. 2. Navigate to **Service Management** > **Change** > **Manage Change Requests**. The **Manage Change Requests** list page is displayed. 3. Click **New** to create a Change Record. Enter all the mandatory details and **Save**. 4. The Change Record must be approved by the Approver for the notification email to be triggered. | 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:** 1. Log in to the Apex application as an Application Designer. 2. Select the Application as **Service Management** and Module as **Business Rule Designer**. 3. Configure **Business Rule Designer** with required Triggers and Conditions. 4. Raise an incident and apply the same condition to trigger the above-created Business Rule. 5. Observe the **History** for Business Rule execution. | 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**: 1. Log in to the Apex application as an Application Designer. 2. Navigate to **Design Studio**, select **Change Management** under **Module** option. Click **Workflow Designer**. The **Workflow List** page is displayed. 3. Click **New** to create a new Workflow Designer. 4. Drag and drop the **User Approval** component on the workflow canvas. The **User Approval** component is displayed. 5. Click and select **Configure Properties** or double-click the **Approval** component. The **User Approval - Properties** pop-up is displayed. 6. Select **User Selectable** under **Approval Type** and select **By Users**. 7. Click the **Approval** to be selected by drop-down and verify the details displayed. | 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**: 1. Log in to the Apex Mobile as an **Analyst**. The Apex Mobile Dashboard is displayed. 2. Verify the **Search Box** and the image on the Apex Mobile Dashboard. | 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:** 1. Log in to the Apex application as an Analyst. 2. Select the application as **Service Management**. 3. Navigate to **Change Request** > **Manage Change Record**. The **Change Record List** page is displayed. 4. Observe the records on the **Manage Change Record** list page. | 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:** 1. Log in to the Apex application as an Application Designer 2. Select the **Service Management** application and click the gear icon to open **Design Studio**. 3. Navigate to **Module** > **Change** > **Designers** > **Workflow Designer**. The Workflow List is displayed. 4. Click **New** or existing ID hyperlink. 5. Enter the required details in the **General** and **Set Trigger & Conditions** steps. 6. In the **Design Workflow** step, Drag and drop the **User Approval** option and click the kebab menu to select the Configure Properties option. 7. Enter the required information in the **General** tab. 8. From the **Approval Type** dropdown, select **Role-Based Approval**. 9. In the Select **Approval Role** (Dot Walking) field, type **Workgroup** and select **Analyst**. | In **Role-Based Approvals**, the owner workgroup is mapped as an approver in the **Workflow Designe**r. |
| 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**: 1. Log in to the Apex application as an Administrator. 2. Select **Service Management** application. 3. Click the gear icon and select **Platform Studio**. 4. Navigate to **API Hub** > **Explorer**. The **Explorer** page is displayed. 5. Select **Retrieve a Record (GET)** from the left panel. The **Retrieve a Record (GET)** details page is displayed. 6. Under the **General** tab, select the cloned Form from the **Form Name** drop-down. 7. Enter other mandatory details in the required fields. 8. Under the Query Parameters, enter the SR ID in **Auto Id (SR ID)** field. NOTE: Enter the SR ID which is raised from a cloned Form. 9. Enter the details under **Request Headers** and click **Send**. 10. Verify the details displayed under **Response** window. | The API fetches details of the SR created from a cloned Form and displays on the Response window successfully. |