--- title: "Crescendo 6.3.1.1 Patch 5" slug: "crescendo-6311-patch-5" updated: 2026-07-28T05:29:57Z published: 2026-07-28T05:29:57Z canonical: "help.symphonysummitai.com/crescendo-6311-patch-5" --- > ## 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 5 > [!NOTE] > 🎯 Now Live! > > **Release Date | 25th July 2025** ## Fixed Issues The following are the issues fixed in Crescendo 6.3.1.1 Patch 5. | Issue ID | Issue Description | Scenario | Resolution | | --- | --- | --- | --- | | 174241 | Users were unable to select **Workgroup** when an SR or Workorder was created from an Incident. | **Steps**: 1. Log in to the application as an Analyst. 2. Navigate to **Incident** > **User** > **Manage Incidents** > **Incident List**. Manage Incident List page is displayed. 3. Click **Incident ID** hyperlink from the list. 4. Click **Link** and **Create**. 5. Choose SR or workorder, a new tab will open (SR details/Work order details). 6. Validate if you can select any **Workgroup** and observe if the value will clear immediately. | Users are able to select the **Workgroup** when an SR or WO is created from an Incident. | | 174782 | In the **Service Portal**, the uploaded image was shown as a broken link and deleted components are restored after publishing, and the changes were not saved. | **Steps:** 1. Log in to the Apex as an Application Designer. 2. Select **Service Management** application. 3. Navigate to **Design Studio** > **Application** > **Service Portal**. The **Service Portal** list page is displayed. 4. Select a **New** or existing Service Portal. 5. In **General** step, enter all the required details and select the persona. 6. In the **Design Porta**l step, navigate to **Layout** > **Layouts**. Drag and drop a layout onto the canvas. 7. Select the **Settings** icon, to configure the properties. 8. On the **Appearance** tab, upload an image and click **Save**. 9. Click **Save** on the **Design Portal** and then select **Next**. 10. Navigate to **Pulish** tab and select **Published**. 11. Log in as the persona selected in the **General** tab. 12. On the dashboard, select **Click to view Service Portal**. 13. Verify if the image is uploaded successfully. | In the **Service Portal**, the uploaded image appears correctly, after publishing, and the changes are saved successfully. | | 174767 | An error message was displayed when the incident module report was being opened. | **Steps:** 1. Log in to the Apex application as an End User. 2. Navigate to **Reports** > select **Incident** module from the list. 3. Click any Report widget and verify the report. | The Incident report is displayed without any issue. | | 174914 | After submitting feedback, the ticket was not displaying any update on the ticket. | **Prerequisite:** Incident Status must be in Resolved. **Steps:** 1. Log in to the Apex application as an End User. 2. Navigate to **Incident** > **Manage Incident**. Click the **Incident ID** hyperlink. The **Incident Details** page is displayed. 3. Click **Provide Feedback** icon. 4. Provide the feedback and submit it. 5. After submitting, navigate back to **Provide Feedback** popup. | After submitting feedback, the ticket displays the update. | ## Known Issues The following are the known issues in Crescendo 6.3.1.1 Patch 5. | 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 | | 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 | | 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 | | 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 | Status indicates the current stage or condition of an incident, problem, change, or service request within its lifecycle.