--- title: "Crescendo 6.3.1.1 Patch 9" slug: "crescendo-6311-patch-9" updated: 2026-07-28T05:26:57Z published: 2026-07-28T05:26:57Z canonical: "help.symphonysummitai.com/crescendo-6311-patch-9" --- > ## 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 9 > [!NOTE] > 🎯 Now Live! > > **Release Date | 6th August 2025** ## Fixed Issues The following are the fixed issues in Crescendo 6.3.1.1 Patch 9. | Issue ID | Issue Description | Scenario | Resolution | | --- | --- | --- | --- | | 175019 | Users were experiencing page load delay when attempting to select multi-values under Advanced Filters. *Note: This issue is happening for all modules.* | **Steps:** 1. Log into the application as an Analyst. 2. Navigate to **Incident** > **Incident** > Manage Incidents. The **Manage Incidents** page is displayed. 3. Click **Advanced Filters**. Select multi-values for Advanced Filters. 4. Observe the values. | Page load delay is not occurring when attempting to select multi values under Advanced Filters. | | 174034 | When two emails were sent, **Email to Ticket** functionality created separate tickets for both, instead of updating the existing ticket. | **Prerequisites:** 1. Mailbox should be configured. 2. Notification Parser should be configured. 3. Job should run. **Steps:** 1. Send an email to the mailbox ID with a subject and body. 2. Send an email to the mailbox ID with a subject only. 3. Log in to Apex as an analyst. 4. Navigate to **Incident** > **Manage Incidents**. The Manage Incidents list page appears. 5. On the **Manage Incidents list** page, verify whether a ticket is created. | Tickets from the **Email to Ticket** functionality are updated when emails are sent, instead of creating new tickets. | | 175018 | Typing in the long text attribute was delayed; text input did not update immediately. | **Steps**: 1. Log in to the Apex Application as an **Analyst**. 2. Navigate to **Incident** > **Manage Incidents**. 3. Click **Incident ID** hyperlink and navigate to **Troubleshooting** tab. 4. Enter the details in the **Problem** long-text box. 5. Verify the delay in the text. | The text entered in the long-text box displayed without any issue. | | 175141 | In the **Classification** admin form configuration though Child Node was set as **Default** Node, in the **Manage Service Request** details page the value was not populated in the **Classification** field. | **Steps**: 1. Log in to the application as an Administrator. 2. Navigate to Service Request module. 3. Navigate to **Classification** admin form configuration. 4. Choose the **Tenant**. 5. Right click on a Child Node and choose it as **Default**. 6. Save the configurations. 7. Navigate to **Manage Service Request** list page. 8. Click **New**. 9. Choose **Tenant**. 10. Verify whether the default value is populated for the **Classification** field. | In the **Manage Service Request** details page the default configured value is populated in the **Classification** field. | ## Known Issues The following are the known issues in Crescendo 6.3.1.1 Patch 9. | 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 |