--- title: "Crescendo 6.3.1.1 Patch 12" slug: "crescendo-6311-patch-12" updated: 2026-07-28T05:23:43Z published: 2026-07-28T05:23:43Z canonical: "help.symphonysummitai.com/crescendo-6311-patch-12" --- > ## 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. # Crescendo 6.3.1.1 Patch 12 > [!NOTE] > 🎯 Now Live! > > **Release Date | 22nd August 2025** ## Fixed Issues The following are the issues fixed in Crescendo 6.3.1.1 Patch 12. | Issue ID | Issue Description | Scenario | Resolution | | --- | --- | --- | --- | | 173330 | The multiple uploaded attachments were not displayed. | **Steps:** 1. Log into the application as an End User. 2. Select the application as Service Request. 3. Navigate to **Request** > **My Service Request**. 4. Existing Catalog must have File Upload control with Allow Multiple Attachment. 5. Raise an SR by uploading multiple attachments. 6. Log in to the application as an Analyst. 7. Navigate to **Manage Service Request - Catalog Details** page and verify if all the uploaded attachments are displayed. | The multiple uploaded attachments are getting displayed. | | 174570 | After clicking **New**, the page was not loading for few seconds. | **Steps:** 1. Log in to the Apex application as an Analyst. 2. Navigate to **Service Request** > **My Service Requests**. The **My Service Request** list page is displayed. 3. Click **New**. Observe the duration of page load. | After clicking **New**, the page is loading without any delay. | | 175438 | In an **SR**, duplicate attachments were displayed under the **Description** field when a **Category** was selected or changed. | **Steps:** 1. Log in to the Apex application as an Analyst. 2. Navigate to **Service Request** > **Manage Service Request** > **Service Request List**. The **Service Request List** page is displayed. 3. Click **New** and in the **General** tab, select a **Tenant**. 4. In the **General** tab, upload an **Attachment**. Example: Uploading one file displays Attachment (1) in the Description field. 5. Select **Category,** verify the attachment count displayed in the **Description** field. | The **Attachment** count is displayed correctly under the **Description** field of the **SR** when a **Category** is selected. | | 175487 | When an **SR** was created from an **Incident** and a new file is attached, the file is not uploaded, and an error message was displayed: **Invalid file size. Maximum upload size is 25 MB**. | **Steps:** 1. Log on to the Apex application as an **Analyst**. 2. Navigate to **Incidents** > **Manage Incidents** > **Manage Incident List**. The **Manage Incident List** page appears. 3. Click **New**, attach a file, and create an Incident. Click **Save**. 4. Navigate to the **Links** tab. 5. Click **Create** > **Service Request**. 6. On the **SR** Details page, click the Attachment Control and select a new file. 7. Verify that the file is uploaded successfully. | When an **SR** is created from an **Incident** and a new file is attached, the file uploads successfully and a confirmation message is displayed. | | 171769 | In the **Send Email** functionality, emails were not triggering when the **To** field in the **Recipient** section contained **By Roles**. | **Steps**: 1. Log in to the Application as an Analyst. 2. Navigate to **Service Management** > **Incident** > **Manage Incidents**. Manage Incidents – List page is displayed. 3. Select **Incident ID** to send an email. 4. Click on the Send Email icon in the Incident. 5. In the **To** field select **By Roles** and enter other details. 6. Click **Submit** and verify if an Email is sent. | Emails are sent when **By Roles** is selected in the **To** field. | | 176488 | Post-upgrade, the created fields with Common Master configuration (parent and child) relationship were not displaying values. | **Steps:** 1. Create two fields and configure **Common Master** with parent and child relationship. | Post-upgrade, the created fields with Common Master configuration (parent and child) relationship are displaying values. | | 176540 | The **Common Master** values for **Root Cause Failure Code** and **Subcode** were not displayed in the **RCA** tab and displayed blank. | **Prerequisite**: Configure a new **Common Master** in the Incident Form and add values to it. **Steps**: 1. Log in to the **Apex** application as an **Analyst**. 2. Navigate to **Incident** > **My Incidents**. 3. Click **New** from the **Incident List** page. 4. Select a **Tenant** from the dropdown. 5. Click the configured **Single Choice** control and verify whether values are displaying in the dropdown. | The configured **Common Master** values display without issues. | | 176193 | Re-accessing the **SSO**-enabled URL without completing login resulted in a blank page instead of redirecting to the authentication page. | **Prerequisite**: Configure **SSO** configuration. **Steps**: 1. Type the **SSO** enable URL in the browser. 2. Verify if redirects to the **SSO** page for authentication. | **SSO** enabled URL redirects to the **SSO** page without any issue. | ## Known Issues The following are the issues fixed in Crescendo 6.3.1.1 Patch 12. | Issue ID | Issue Description | Scenario | Resolution | | --- | --- | --- | --- | | 84144 | Users are not able to create the duplicate Priority Matrix. | **Steps**: 1. Login to the application as an Application Designer. 2. Select **Service Management** application. 3. Click on settings icon and select the **Module** as **Problem.** 4. Navigate to **Configuration** > **Priority Matrix**. 5. Select already existing field value for the **Impact**, **Urgency**, **Priority** fields. 6. Verify the **Priority Matrix** configuration. | NA | | 79411 | User is not able to save the Target Form created through Form Relation when multiple files are attached in the Source Form. | **Steps**: 1. Login to the application as an Analyst. 2. Navigate to **Service Management** > **Incidents** > **Manage Incidents**. 3. Click **New** button on the list page. 4. Fill all the mandatory details. 5. Upload the file in **Attachment** field. 6. Click on **Save** button. 7. Access the same created by clicking on **ID** hyperlink. 8. Navigate to **Links** tab and click on **Create** button and select the module for which form relation is configured (Example: INC to SR.) 9. Verify the uploaded file in **Attachment** field. 10. Click **Save** button and verify whether user can save the Target Form (SR). 11. Verify the toast message. | NA | | 79372 | Users are experiencing alignment issue in the Create tab of Links tab in the Form Designer. | **Steps**: 1. Log in to the application as an Application Designer. 2. Navigate to **Service Management** > **Design Studio** > Select **Module** as **Incident** > **Form Designer**. 3. Select **Manage Incidents** form and place the form in **Maintenance**. 4. Navigate to **Design Form** step. 5. Click on the gear icon of **Links** tab. 6. Click on **Create** tab and verify the alignment of add icon '+'. | NA | | 171982 | The **Problem Record** status is not reflected on the linked **Incident** or **Service Request**, and the Parent-Child option is missing in the Link popup. | **Steps:** 1. Log in to Apex application. 2. Select **Service Management** application. 3. Navigate **Problem** > **Manage Problem** **Record.** The **Manage Problem Record** List page is displayed. 4. Click existing **PR ID** and navigate to **Links** tab. 5. Select Incident or SR. The **Link** pop-up appears. 6. In the pop-up, select the **Parent-Child** relationship from the dropdown. | NA | | 79887 | The **Define Conditions** step in the **Notification Parser** displays UI alignment inconsistencies and text translation issues after configuring line forms and define keys. | **Steps:** 1. Log in to the Apex application. 2. Navigate to **Settings** > **Design Studio** > **Application** > **Notification Parser**. The Notification Parser List is displayed. 3. Click **New** and fill in all mandatory fields. 4. Navigate to the **Parser Content** step. Fill in all required **Line** Form entries. 5. To add or update form data, select the relevant line form and configure the **Define Keys**. 6. Select **Define Conditions** step. | N/A | | 78560 | Only one email was converted into a ticket. The remaining emails were not processed or converted. | **Prerequisites:** 1. API Configuration is set up 2. Mailbox is configured correctly 3. Notification Parser is configured **Steps:** 1. Log in to the application as an Admin. 2. Navigate to **Design Studio** > **Application** > **Scheduler**. 3. Filter and locate the Scheduler configured during Mailbox setup. 4. Click **Scheduler run immediately** and refresh until the job displays **Success**. 5. Login as an Analyst. 6. Navigate to Manage Incident List page. 7. Verify if the tickets are created for all sent emails. | N/A | | 79604 | In the **Notification Parser**, a warning message for mandatory values displays even though all values are entered. | **Prerequisite:** A Filter is configured in the **Define Condition** step under **Parser Content**, where the **User-Defined Key** is set to **Symptom**, the **Operato**r is **Set** to contains, and the value is set to **Automation**. **Steps**: 1. Log in to the application as an **Application Designer**. 2. Navigate to **Application Tile** > **Notification Parser**. 3. Click the **ID** hyperlink of Mail to Incident parser from the list. 4. Click **Parser Content** step and delete all the Line Form entries that were previously added. 5. Observe that the filter in **Define Conditions** remains and click **Next**. | N/A | | 79461 | In the **Mailbox Configuration**, the warning message '*You have not entered all mandatory value(s)*.' displays even though all mandatory values are provided in the mail to create a ticket using the API. | **Steps**: 1. Log in to the application as an **Application Designer**. 2. Navigate to **Application Tile** > **Mailbox Configuration**. 3. Click **New** and enter the required details. Click **Next** in the **Configuration** and **Rules** steps. | N/A | | 79328 | The value is not getting binded for ‘Tree View’ control. | **Steps:** 1. Log in to the application as an End User. 2. Navigate to **My Incidents** and raise an incident. 3. Log in to the application as an Analyst. 4. Click on the above-created Incident ID hyperlink. The **Incident Details** page is displayed. 5. Observe the value for **Category** field. | N/A | | 79412 | On the **Manage Incidents – Details** page, a field-level inline message displays when the user uploads multiple files one after another in the **Attachment** control. However, the inline message does not display when the user uploads multiple files simultaneously. | **Steps**: 1. Login to the application as an **Analyst**. 2. Navigate to Service Management > Incidents > Manage Incidents. The Manage Incidents - List page is displayed. 3. Click **New** from the **Manage Incidents - List** page. 4. Enter the required details and attach the file in **Attachment** field one by one with file up to 24MB. 5. Verify the field level inline which will be displayed. | N/A | | 90353 | In the **User Incident Details** page, for **Category** and **Classification** fields the value is not getting binded. After page refresh the value gets binded. | **Prerequisite**: Incident should be created. **Scenario 1**: 1. Login as End User and navigate to **My Incidents** list page. 2. Click on the **Pending** tab and then click on **In Progress** tab. 3. Click on the **ID** link of the record. 4. Verify whether the value is populated for **Category** & **Classification** fields. **Scenario 2:** 1. Login as End User and navigate to My Incidents list page. 2. Click on the **ID** link of the record. 3. If the value is populated for **Category** & **Classification** field, then follow the below step. 4. Click on the **Update Incident** icon. 5. Enter the Message and click on **Save** button. 6. Then, verify whether the value is populated for **Category** and **Classification** fields. | N/A |