--- title: "Crescendo 6.3.1.2 Patch 14" slug: "crescendo-6312-patch-14" updated: 2026-07-28T05:06:42Z published: 2026-07-28T05:06:42Z canonical: "help.symphonysummitai.com/crescendo-6312-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.2 Patch 14 > [!NOTE] > 🎯 Now Live! > > **Release Date | 7th January 2026** ## Fixed Issues The following are the issues fixed in Crescendo 6.3.1.2 Patch 14. | Issue ID | Issue Description | Scenario | Resolution | | --- | --- | --- | --- | | 180483 | The **Workgroup** and **Analyst** attributes were not copied to the Service Request when an Incident was converted to a Service Request. | **Steps**: 1. Log in to the application as an Analyst. 2. Navigate to **Incident** > **Manage Incidents**. The **Manage Incidents – List** is displayed. 3. Click **CR ID** hyperlink. 4. Click **Kebab** menu from the Incident Banner and select **Convert Incident To**. 5. Select **Service Request**. 6. Verify the **Workgroup** and **Analyst** attributes. | The **Workgroup** and **Analyst** attributes are copied from the **Incident** to the **Service Request** during conversion without any issues. | | 180426 | When Okta Authentication is configured, the incident links in the email notification received by an analyst, lead the link to Dashboard page and not the Incident details page, when business rule is configured. | **Prerequisites**: - Ensure that you have a business rule configured which sends an email notification with the link to Incident details page. - Okta Authentication must be configured. **Steps:** 1. Open the email notification for the incident as an Analyst. 2. Check the link in email notification. 3. Click the Incident link and open it in browser. 4. Verify if the link is taking you to the Incident Details page or the Dashboard page. | The link if Incident sent in the email notification to an Analyst works correctly and leads them to the Incident Details page even when OKTA authentication is configured. | | 180324 | CR Approvals were not showing in the Approvals Quick Link menu. However, was displaying under the filter view. | **Prerequisite**: Configure a workflow for the CR. **Steps**: 1. Login into the Application. 2. Navigate to **Change** > **Manage Change records** > Click **New**. 3. Fill all the mandatory details and submit the CR. 4. Once submitted, the CR should be in Pending for approval status. 5. Switch to the approver account and click on the Quick Approval Icon. 6. Verify if the CR is showing as pending for approval or not. 7. Navigate to the Approve Change records page and check if the CR is pending for approval or not | CR Approvals are displaying in the Approvals Quick Link menu. | | 179890 | The Approver was not getting Approval Notifications under **Approval** pop-up. | **Steps:** 1. Log in to the Apex application as an Analyst. 2. Navigate to **Change** > **Manage Change** > **Approver Change Requests**. The **Approve Change Requests – List** page is displayed. 3. Observe the Approval Notifications. The Approver is getting Approval Notifications under **Approval** pop-up. | The Approver is getting Approval Notifications under **Approval** pop-up | ## Known Issues The following are the known issues in Crescendo 6.3.1.2 Patch 14. | Issue ID | Issue Description | Scenario | Workaround | | | --- | --- | --- | --- | --- | | 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 | | | 81008 | Problem record status not reflected in linked Incident/SR; Parent-Child option missing in **Link Service Request** and **Link Incident** popup. | **Steps:** 1. Log in to the Apex application as an Analyst. 2. Navigate to **Service Management** > Select the module as Problem. 3. Navigate to **Problem** > **Manage Problem Records**. The **Problem Records List** page is displayed. 4. Click **Problem Record ID** hyperlink. The **Problem Record Details** page is displayed. 5. Navigate to **Links** Tab > Click **Link** drop-down. Select the Module as Service Request or Incident. 6. Observe the **Status** of the Problem Record on the displayed pop-up. | N/A | | | 91051 | The **RCA Required** toggle switch still appears for a moment on **Major Incident** pop-up. | **Steps**: 1. Navigate to **Incident**. The Incident List page is displayed. 2. Click **Major Incident ID** hyperlink. The Major Incident Details page is displayed. 3. Disable **RCA Required** toggle switch under **Prioritization**. | N/A | | | 91002 | Analyst Dashboard is taking more then 36 sec to load the Page | | N/A | | | 91561 | Major Incident>‘RCA Required’ Toggle Briefly Appears Then Disappears on Major Incident Popup & Problem Record Not Created on Incident Resolution. | | N/A | | | 92737 | In the Approval Grid, the Forwarded To user details are not displayed. | | N/A | | | 93677 | Schedular is getting Failed, when Recipients = AdminTable.Created By or AdminTable.Updated By is configured. | | N/A | | | 94140 | When Level 1 Approver Rejects the Referred Back request, then in Approval Timeline - Graphical View the approval node is not Highlighted in Red and Workflow Processed is not displayed. | | N/A | | | 94153 | When Level 2 Approver Refer Back to Requestor and then to Level 1 Approver, in the Approval Timeline the Level 2 node is displayed twice. | | N/A | | | 94408 | In Data Source tab, when filter is applied then after saving the Value field is not rendered. | | N/A | | | 96685 | In the User Filter Popup, when a Search action is performed using the User ID then correct Search results are not fetched. | | N/A | | | 96725 | In the Reallocate popup after save action if navigated back then value is not retained for the Site dropdown. | | N/A | | | 97207 | In the Platform Studio, when a Form is cloned then the controls are not copied and rendered in the Cloned Form - Design Form stepper. | | N/A | | | 98158 | In the Form Designer, able to add other fields into multi valued group. | | N/A | | | 98214 | Though only Level 1 & Level 4 Approver is obtained, but in the Workflow Diagram all Level Approver diagram is rendered which is incorrect. | | N/A | | | 98548 | In the condition builder for Value dropdown when mouse scroll or clicked on downward arrow icon the next set of values are not listed. | | N/A | | | 98573 | If Multi Choice control are present inside the Multi Valued panel, then the values are not binded & displayed. Instead, blank chip is displayed. | | N/A | |