--- title: "Crescendo 6.3.1.1 Patch 14" slug: "crescendo-6311-patch-14" updated: 2026-07-28T05:21:00Z published: 2026-07-28T05:21:00Z canonical: "help.symphonysummitai.com/crescendo-6311-patch-14" --- > ## 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 14 > [!NOTE] > 🎯 Now Live! > > **Release Date | 20th September 2025** ## Fixed Issues The following are the issues fixed in Crescendo 6.3.1.1 Patch 14. | Issue ID | Issue Description | Scenario | Resolution | | --- | --- | --- | --- | | 174793 | The **'Wait for Condition**' action on the Main Form did not work as expected. | **Prerequisites**: 1. Configure the **Workflow Designer** for a main form and design a workflow with **Wait for Condition**. 2. The workflow triggers when a new incident is created. **Steps**: 1. Log in to the **Apex** application as an **Analyst**. 2. Navigate to **Incident** > **Manage Incidents**. The **Manage Incidents – List** is displayed. 3. Click **New** and enter the required details. 4. Click **Save**. 5. Verify if the configured workflow triggered and executed. | The **Wait for Condition** action is working as expected. | | 177886 | Some field information, such as **Manager** and **Location**, did not populate when creating a record through API. | **Steps**: 1. Open Postman app. 2. Enter the request for the **POST** method of the SR_LogServiceCatalog API. 3. Click **Send**. 4. Verify that all fields populate based on the created SR. | All field information, including **Manager** and **Location**, populates correctly when creating a record through API. | | 174341 | Users were unable to create New SLA in interaction module (call module). The SLA API *sla/api/SLAType/Save* is returning 500 Internal Server Error. | **Steps**: 1. Log in to the application as an Application Designer. 2. Select **Interaction** Module. (Call Module). 3. Navigate to **Designers** > **SLA Designer** > **SLA Type**. SLA Type list page is displayed. 4. Click **New**. 5. Enter the value for all the fields. 6. Click **Submit** to verify whether the SLA Type is saved. | Users can create new SLA in the Interaction module. | | 177967 | Users were able to see www.youtube.com on the web console that performed 3rd part API calls. | **Steps**: 1. Log in to the Application. 2. Open the Developer Tools. 3. Select Sources. 4. Observe if you can view [www.youtube.com.](/summit-platform/docs/www.youtube.com.) > [!NOTE] > Note > > At the code level if the configuration is set to false then this link is not displayed. If true, then it is displayed. | Users a not able to see [www.youtube.com](/summit-platform/docs/www.youtube.com) link on the web console. | | 176394 | The icon that had been removed from the **Category** configuration page still appeared as a broken image on the **Manage Service Requests** page. | **Steps:** 1. Log in to the application. 2. Navigate to **Service Management** > **Design Studio** > Select module as **Service Request** > **Configurations** > **SR Masters** > **Category**. 3. Remove the Icon from any of the nodes. 4. Click **Save**. 5. Navigate to **Manage Service Requests** page. 6. Select the **Tenant** from the drop-down. 7. Click **Category** tree control. 8. On the Select **Category** pop up page, verify the node for which Icon was removed. | The icon that had been removed from the **Category** configuration page does not appear on the **Manage Service Requests** page. | | 173471 | Approver notification was not triggered from the workflow after the first approver approved. | **Steps:** 1. Navigate to **Service Request Management** > **Manage Service Request**. The **Manage Service Request** page is displayed. 2. Navigate to **Approval Timeline**. 3. Observe the Approval Notification after the first level approval. | Approver notification is getting triggered from the workflow after the first approver approved. | | 178857 | Users redirected via SSO from the customer's My Apps portal were landing on the application's form-based login page instead of being automatically signed in. | **Steps:** 1. Log in to the Customer My Apps portal. 2. Click Apex application tile. 3. Observe the landing page. | Users redirected via SSO from the customer's My Apps portal are not landing on the application's form-based login page and getting signed-in automatically. | ## Known Issues The following are the known issues in Crescendo 6.3.1.1 Patch 14. | 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 |