--- title: "Crescendo 6.3.1.2 Patch 3" slug: "crescendo-6312-patch-3" updated: 2026-07-28T05:16:33Z published: 2026-07-28T05:16:33Z canonical: "help.symphonysummitai.com/crescendo-6312-patch-3" --- > ## 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 3 > [!NOTE] > 🎯 Now Live! > > **Release Date | 31st October 2025** ## Fixed Issues The following are the issues fixed in Crescendo 6.3.1.2 Patch 3. | Issue ID | Issue Description | Scenario | Resolution | | --- | --- | --- | --- | | 177022 | The requester was unable to save or update the **Knowledge Base** (KB) article because the Save button was greyed out after the article was referred back by the approver. | **Steps**: 1. Log in to the **Apex** application as an **Analyst**. 2. Navigate to **Knowledge** > **Approve Knowledge Records**. The **Approve Knowledge Records** – **List** page is displayed. 3. Click **Article ID** hyperlink. 4. Update the required details and click **Save**. | The requester is able to save and update the KB article after the article is referred back by the approver, and the **Save** button is now active. | | 175115 | Added field names and Values were not visible after saving and reopening the same record. | **Steps**: 1. Log in to the application. 2. Navigate to **Design Studio**. 3. Click Application. 4. Navigate to **Access Control Center** > **User Role Mapping**. 5. Open Any Existing Role. 6. Go to **Publish** to stepper. 7. **Add Filter Set** (Add any field and Value). 8. Click **Update**. 9. Go to list and open the Same Role. 10. In **Publish** stepper verify the Added field Value name. | Added field names and Values are visible after saving and reopening the same record. | | 177211 | Users were experiencing an error as “something went wrong” when a password protected file was uploaded in the Attachment field when creating an Incident. | **Steps**: 1. Log in to the Application. 2. Select **Service Management**. 3. Navigate to **Incident** > **Manage Incident** > **My Incidents**. 4. Click **New**. 5. Enter the required details and upload the password protected excel file in the **Attachment** field. 6. Verify if an error is displayed. | Users are not experiencing any errors when uploading password protected excel file in the Attachment field. | | 175116 | **Asset Management** module menu screen was displayed with half options. | **Steps**: 1. Log in to the Application Analyst. 2. Select **Asset Management**. 3. Select **Asset Management** and verify if the options are displayed completely. | Asset Management module menu screen displays completely with all the information. | | 178125 | The values configured under the **Source Values** section in the **Set Values** tab were not being retained after saving. | **Steps:** 1. Log in to the Apex application as an App Designer. 2. Navigate to **Form Relations** > **Form Relations Details** > **Set Values**. 3. Observe Source Values. | The values configured under the **Source Values** section in the **Set Values tab** are being retained after saving. | | 176856 | The City (parent) and Site (child) fields were set up with a parent-child mapping in the Allocate/Reallocate popup under Assets. The Site values loaded correctly on the list page but displayed 'No results found' in the popup. | **Steps:** 1. Navigate to **Asset Management** > **Asset** > **Fixed**. 2. Add City (parent) and Site (child) fields with parent child relationship (common master) in Allocate pop-up. 3. Add City (parent) and Site (child) fields with parent child relationship (common master) in Fixed main form. 4. Configure same common master parent child in both popover and common master. 5. In main form field name should be same (give same label name for child field). 6. Open popover and observe the child options are loading w.r.t parent value. | The Site values loaded correctly on the popup as well. | | 179375 | The **Manage Incidents List** page was not loading correctly. | **Steps:** 1. Log in to the Apex application as an Analyst. 2. Navigate to **Incident** > **Manage Incidents**. 3. Observe the loading of **Manage Incident List** page. | The **Manage Incidents List** page is loading correctly. | | 175815 | The refer-back Workflow details did not appear in the popup after the approver referred-back the **CR**. | **Steps**: 1. Log in to the **Apex** application as an **Analyst**. 2. Navigate to **Change** > **Manage Change Record**. 3. Click **New**, enter the required details, and click **Submit**. 4. Refer- back the CR and verify the **Workflow** popup for refer-back details. | The **Workflow** popup displays the refer-back details after the approver refer-back a CR. | | 178125 | The Error Log icon displayed twice in Error Log column. | **Steps:** 1. Log in to the Apex application as an App Designer. 2. Navigate to **Design Studio** > **Scheduler**. The **Scheduler List** page is displayed. 3. Create a scheduler record. 4. Scheduler should be in failed state. 5. Click **Job History**. 6. Observe the Error Log icon in **Error Log** column. | The Error Log icon displays only once **Error Log** column. | | 179459 | A **500 Internal Server Error** was displayed when the user navigated from the **Access Level** step to the **Screen Selection** step on the **User Role Template Details** page. | Steps: 1. Navigate to **Settings** > **Application Settings** > **Application** tab > **Access Control Center** > **User Role Template**. 2. The **User Role Template** page is displayed. 3. Click **New** and enter the required details, click **Next**. 4. In the **Access Level** step, enter the required details and click **Next**. | The user can navigate from the **Access Level** step to the **Screen Selection** step on the **User Role Template Details** page without any issues. | ## Known Issues The following are the known issues in Crescendo 6.3.1.2 Patch 3. | 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 |