--- title: "Crescendo 6.3.1.2 Patch 11" slug: "crescendo-6312-patch-11" updated: 2026-07-28T05:09:19Z published: 2026-07-28T05:09:19Z canonical: "help.symphonysummitai.com/crescendo-6312-patch-11" --- > ## 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 11 > [!NOTE] > 🎯 Now Live! > > **Release Date | 12th December 2025** ## Fixed Issues The following are the issues fixed in Crescendo 6.3.1.2 Patch 11. | Issue ID | Issue Description | Scenario | Resolution | | --- | --- | --- | --- | | 181474 | When a new form is created using 'Use Existing Form', the newly created form was not displayed in the **Role Template screen > Screen Selection (3rd step)**. | **Prerequisites** 1) Log in as an **App Designer**. 2) Create a New form using 'Use Existing Form'. **Steps:** 1) Log in as an Administrator. 2) Click **Service Management > Access Control Center > Role Template**. 3) Navigate to the 3rd step - Screen Selection. 4) Verify if the newly created form is displayed in the **Customer Info** section and **Access Control Center** section. | The newly created form is now successfully displayed in the **Role Template screen > Screen selection** respective sections. | | 181840 | When **Special Approver** is configured in the Workflow with **Approval Type** set as **Static** and but user added as **Additional Approver**, the additional approver was not receiving notificaitons for ticket Approver under the List for approvals. | **Prerequisites** 1) Ensure that you have configured a workflow with a Special Approver, Approval type is static and a user is added as an Additoinal Approver in the workflow. **Steps:** 1) Log in as an **Approver** who is configured as an **Additional Approver**. 2)Check the **Approval** at the top of the Title bar if Approval notificaiton was received for a ticket or in the Service Rquest > Approver Service Request if the same ticket was sent for approval using the special approver Workflow configuration. | The Additional Approver is now receiving the tickets for which the user is configured as a Special Approver. | | 181188 | The **Bulk Import/Export** and **View History** pages often loaded as blank with no data displayed. | **Steps**: 1. Log in to the Apex application as an **Analyst**. 2. Navigate to **Asset Management** > **Manage Asset** > **Fixed**. The **Fixed – List** page is displayed. 3. Click **Bulk Import** or **Export** icon. 4. Verify if the page load appropriately. | The **Bulk Import/Export** and **View History** pages are displayed without any issue. | | 181665 | The analyst could not be removed from the workgroup even though no incidents were associated with the analyst. In addition, the **Action Record** window for the analyst with associated incidents did not display any records. | **Steps**: 1. Log in to the application as an **Analyst**. 2. Navigate to Application Settings > Analyst(s). The **Analyst(s)** page is displayed. 3. Click **ID** hyperlink. 4. Click **Remove** icon corresponding to the Analyst name. | The analyst could remove without any issue. | | 181780 | The admin form data was not updating through POSTMAN. | **Steps**: 1. Log in to the application. 2. In the API Explorer select **PUT** Method. 3. Select Form Type as **Designer**. 4. Select **Tenant** and **Form Name**. 5. In the Request Body click **Add a Field**. 6. Select **Tenant** as Field and Value as required on the Set Request popup screen. 7. Payload is created, use this on POSTMAN and observe if the admin form data is updated. | The admin form data is updating through POSTMAN as expected. | | 180855 | CI details page was opening blank even though all CI data displayed correctly in the list page. | **Steps**: 1. Log in to the application. 2. Navigate to Infrastructure as CI form. 3. Delete the **Category** field. 4. **Save** and **Publish** the form. 5. Navigate to Infrastructure as CI list page. 6. Access the existing records and verify whether the values are binded. 7. Verify whether able to create a new CI record. 8. Verify whether values are binded for the newly created record. 9. Verify whether able to update the CI. | CI details page is displaying as expected. |