--- title: "Release Notes Crescendo SP1 (6.3.1)" slug: "release-notes-crescendosp1-631" updated: 2026-07-29T11:27:57Z published: 2026-07-29T11:27:57Z canonical: "help.symphonysummitai.com/release-notes-crescendosp1-631" --- > ## 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. # Release Notes Crescendo SP1 (6.3.1) > [!NOTE] > 🎯 Now Live! > > **Release Date | 9th May 2025** Let’s dive into the key highlights, exciting improvements introduced, and a few known issues to keep an eye on. Every update brings something new, with a focus on enhancing the experience! ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Yellow Modern 3 Step Value Discipline Process Infographic Brainstorm.png?sv=2026-02-06&spr=https&st=2026-11-11T13%3A08%3A36Z&se=2026-11-11T14%3A08%3A36Z&sr=c&sp=r&sig=I%2FHoXBbxGNqbPb0uKQpHQFggOBx1SrOhyvcRCoL%2BdFE%3D) The following section provides key highlights, improvements introduced and known issues in Crescendo SP1 (6.3.1) release. - [Merged Releases](/summit-platform/docs/release-notes-crescendosp1-631#merged-releases) - [New Features](/summit-platform/docs/release-notes-crescendosp1-631#new-features) - [Improvements](/summit-platform/docs/release-notes-crescendosp1-631#improvements) - [Known Issues](/summit-platform/docs/release-notes-crescendosp1-631#known-issues) - [Fixed Issues](/summit-platform/docs/release-notes-crescendosp1-631#fixed-issues) > [!NOTE] > Post SP1 upgrade > > Ensure to configure and execute one time Notification Migration Job on the [Scheduler](https://help.symphonysummitai.com/summit-platform/docs/scheduler-system-defined-actions-crescendo631). ## Merged Releases Updates till the following releases have been merged into Crescendo SP1 (6.3.1) Release: - All Releases up to **6.3.0 B070 Patch 7** are merged to Crescendo SP1 (6.3.1) Release. ## New Features ### Design Studio Let's take a quick look at our Design Studio user persona. | ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/MSP Design Personas (1).png?sv=2026-02-06&spr=https&st=2026-11-11T13%3A08%3A36Z&se=2026-11-11T14%3A08%3A36Z&sr=c&sp=r&sig=I%2FHoXBbxGNqbPb0uKQpHQFggOBx1SrOhyvcRCoL%2BdFE%3D) | | --- | The following section provides a sneak-peek of the functionalities added for Design Studio. | [![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/RN_CARD_Paragraph(1).png?sv=2026-02-06&spr=https&st=2026-11-11T13%3A08%3A36Z&se=2026-11-11T14%3A08%3A36Z&sr=c&sp=r&sig=I%2FHoXBbxGNqbPb0uKQpHQFggOBx1SrOhyvcRCoL%2BdFE%3D)](https://help.symphonysummitai.com/summit-platform/docs/paragraph-1) | [![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/1(43).png?sv=2026-02-06&spr=https&st=2026-11-11T13%3A08%3A36Z&se=2026-11-11T14%3A08%3A36Z&sr=c&sp=r&sig=I%2FHoXBbxGNqbPb0uKQpHQFggOBx1SrOhyvcRCoL%2BdFE%3D)](https://help.symphonysummitai.com/summit-platform/docs/business-risk-value-mapping-crescendo631) | [![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/2(41).png?sv=2026-02-06&spr=https&st=2026-11-11T13%3A08%3A36Z&se=2026-11-11T14%3A08%3A36Z&sr=c&sp=r&sig=I%2FHoXBbxGNqbPb0uKQpHQFggOBx1SrOhyvcRCoL%2BdFE%3D)](https://help.symphonysummitai.com/summit-platform/docs/rating-control-crescendo631) | | --- | --- | --- | | [![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Risk Assessment Admin Forms (1).png?sv=2026-02-06&spr=https&st=2026-11-11T13%3A08%3A36Z&se=2026-11-11T14%3A08%3A36Z&sr=c&sp=r&sig=I%2FHoXBbxGNqbPb0uKQpHQFggOBx1SrOhyvcRCoL%2BdFE%3D)](https://help.symphonysummitai.com/summit-platform/docs/manage-change-record-transaction-form-crescendo631) | [![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/4(16).png?sv=2026-02-06&spr=https&st=2026-11-11T13%3A08%3A36Z&se=2026-11-11T14%3A08%3A36Z&sr=c&sp=r&sig=I%2FHoXBbxGNqbPb0uKQpHQFggOBx1SrOhyvcRCoL%2BdFE%3D)](https://help.symphonysummitai.com/summit-platform/docs/overview-brd-crescendo631) | [![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-NQTZZ729.png?sv=2026-02-06&spr=https&st=2026-11-11T13%3A08%3A36Z&se=2026-11-11T14%3A08%3A36Z&sr=c&sp=r&sig=I%2FHoXBbxGNqbPb0uKQpHQFggOBx1SrOhyvcRCoL%2BdFE%3D)](https://help.symphonysummitai.com/summit-platform/docs/panels) | | --- | --- | --- | | [![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-V5LN1TUC.png?sv=2026-02-06&spr=https&st=2026-11-11T13%3A08%3A36Z&se=2026-11-11T14%3A08%3A36Z&sr=c&sp=r&sig=I%2FHoXBbxGNqbPb0uKQpHQFggOBx1SrOhyvcRCoL%2BdFE%3D)](https://help.symphonysummitai.com/summit-platform/docs/enable-special-approver-1) | [![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-IWZXUCCQ.png?sv=2026-02-06&spr=https&st=2026-11-11T13%3A08%3A36Z&se=2026-11-11T14%3A08%3A36Z&sr=c&sp=r&sig=I%2FHoXBbxGNqbPb0uKQpHQFggOBx1SrOhyvcRCoL%2BdFE%3D)](https://help.symphonysummitai.com/summit-platform/docs/search-box-1) | | ## Applications The following section provides key highlights and Application-wise description of new features introduced in Crescendo SP1 (6.3.1) Release. - [Service Management](/summit-platform/docs/release-notes-crescendosp1-631#service-management) ### Service Management Let's take a quick look at our Service Management user personas. | ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Designs Risk Assessment (6).png?sv=2026-02-06&spr=https&st=2026-11-11T13%3A08%3A36Z&se=2026-11-11T14%3A08%3A36Z&sr=c&sp=r&sig=I%2FHoXBbxGNqbPb0uKQpHQFggOBx1SrOhyvcRCoL%2BdFE%3D) | ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Designs Risk Assessment (5).png?sv=2026-02-06&spr=https&st=2026-11-11T13%3A08%3A36Z&se=2026-11-11T14%3A08%3A36Z&sr=c&sp=r&sig=I%2FHoXBbxGNqbPb0uKQpHQFggOBx1SrOhyvcRCoL%2BdFE%3D) | | | --- | --- | --- | The following section provides a sneak-peek of the functionalities added for Service Management. | [![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Risk Assessment Admin Forms(1).png?sv=2026-02-06&spr=https&st=2026-11-11T13%3A08%3A36Z&se=2026-11-11T14%3A08%3A36Z&sr=c&sp=r&sig=I%2FHoXBbxGNqbPb0uKQpHQFggOBx1SrOhyvcRCoL%2BdFE%3D)](https://help.symphonysummitai.com/summit-platform/docs/risk-assessment-overview-crescendo631) | [![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Risk Assessment Admin Forms.png?sv=2026-02-06&spr=https&st=2026-11-11T13%3A08%3A36Z&se=2026-11-11T14%3A08%3A36Z&sr=c&sp=r&sig=I%2FHoXBbxGNqbPb0uKQpHQFggOBx1SrOhyvcRCoL%2BdFE%3D)](https://help.symphonysummitai.com/summit-platform/docs/analyst-manage-change-record-crescendo631) | [![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-0K2BRG6C.png?sv=2026-02-06&spr=https&st=2026-11-11T13%3A08%3A36Z&se=2026-11-11T14%3A08%3A36Z&sr=c&sp=r&sig=I%2FHoXBbxGNqbPb0uKQpHQFggOBx1SrOhyvcRCoL%2BdFE%3D)](https://help.symphonysummitai.com/summit-platform/docs/rca-mechanism) | | --- | --- | --- | | [![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/RN Card - Copilot (44).png?sv=2026-02-06&spr=https&st=2026-11-11T13%3A08%3A36Z&se=2026-11-11T14%3A08%3A36Z&sr=c&sp=r&sig=I%2FHoXBbxGNqbPb0uKQpHQFggOBx1SrOhyvcRCoL%2BdFE%3D)](https://help.symphonysummitai.com/summit-platform/docs/clone-1) | | | | --- | --- | --- | ## Improvements The following are new enhancements added in Crescendo SP1 (6.3.1): - [Platform Studio](/summit-platform/docs/release-notes-crescendo-63#platform) - [Design Studio](/summit-platform/docs/release-notes-crescendo-63#design-studio) ### Platform Studio | Element | Improvement Name | Description | | --- | --- | --- | | Common Masters | Versatility Included for Common Masters: Increased Character Limit and Inclusion of Special Characters for naming Master Type and Master Value | Increasing the character limit for naming Master Type and Master Value along with inclusion of special characters. This enhancement allows descriptive identifiers and reduces ambiguity. For more information, refer to [Master Type](https://help.symphonysummitai.com/summit-platform/docs/master-type-1) and [Master Value](https://help.symphonysummitai.com/summit-platform/docs/master-value-1). | ### Design Studio | Element | Improvement Name | Description | | --- | --- | --- | | Form Designer | Enhanced Conditional Visibility for Paragraph Form Controls | Introduced **Validations** tab to set hidden conditions to control a paragraph form control’s visibility. This enhancement ensures it appears only when specific criteria are met. For more information, refer to [Paragraph](https://help.symphonysummitai.com/summit-platform/docs/paragraph-1). | | Form Designer | Form Name Flexibility Enhancement: Increased Limit and Special Character Support | The character limit for **Form Name** field under **General** step is increased from 40 to 100. It also allows you to include special characters such as $, &, (, ),- and _. Improve form naming by extending the character limit and allowing more special characters for greater flexibility and better user experience. For more information, refer to [Define Form Characteristics](https://help.symphonysummitai.com/summit-platform/docs/define-form-characteristics-1). | | Notification Designer | Provision to refer Dynamic Fields in Notification Template | Notification Templates are configured with dynamic field attributes from the selected Table. When the template is used within the application only the dynamic attributes are referenced. For more information, refer to [Notification Designer](https://help.symphonysummitai.com/summit-platform/docs/notification-designer-overview-crescendo631). | | Scheduler | Advancement in handling existing notification templates through Scheduler | Run a one time Scheduler Job to migrate the existing notification templates to function in such a way that, only the dynamic operators are referenced when used in the Application. For more information, refer to [Scheduler](https://help.symphonysummitai.com/summit-platform/docs/scheduler-system-defined-actions-crescendo631). | | Service Portal | Introduced Incident Management Templates to make workflow more efficient | Introduced **Incident Rule Management Templates** under the Table dropdown in the Properties of Search Results within the Search Box under General Widgets. This allows users to configure search results with predefined templates, improving incident rule management and search customization. For more information, refer to [Search Box](https://help.symphonysummitai.com/summit-platform/docs/search-box-1). | | Service Portal | New Service Catalogs are here to help you move through tasks quickly and smoothly | Introduced **Catalogs** under the Table dropdown in the Properties of Search Results within the Search Box under General Widgets. This allows users to configure search results with predefined templates, improving incident rule management and search customization. For more information, refer to [Search Box](https://help.symphonysummitai.com/summit-platform/docs/search-box-1). | ## 6.3.1 Known Issues The following section provides details of known issues in 6.3.1 release: | Issue ID | Issue Description | Scenario | Workaround | | --- | --- | --- | --- | | 76416 | Users are experiencing issues upon configuring the Formula Control for multiple rating controls. | **Steps**: 1. Log in to the Apex Application as an Application Designer. 2. Navigate to **Design Studio** > **Change Module** > **Form Designer**. 3. Select **Manage Change Record**, place the form in **Maintenance** mode. 4. Go to the same **Mange Change Record** form in the Design step configure Formula Control. 5. Drag and drop Formula Control on the Design Canvas. 6. Configure **Properties**, click **Advance** tab. 7. In **Build the Formula here** Text Field, type $ and add rating control chips. 8. From last press left arrow and use $ to configure. 9. Observe for any issues. | N/A | | 77079 | The system is not allowing to save the configured Rating Control. An error message is displayed "* already exists as a Rating Control. Please rename /delete the existing control. Please change Data Source Table*" even though label name is not matching with the deleted controls. | **Steps**: 1. Log in to the Apex Application as an Application Designer. 2. Navigate to **Design Studio** > **Change Module** > **Form Designer**. 3. Select **Manage Change Record** place the form in **Maintenance** mode. 4. Go to the same **Mange Change Record** form in the **Design** step configure Survey Control. 5. Drag and drop **Rating** control on the Design Canvas. 6. Enter **Title** name and other required details in the Rating control and click **Save**. 7. Observe the below error: "* already exists as a Rating Control. Please rename /delete the existing control. Please change Data Source Table*" | N/A | | 77103 | Change History is displaying numerical values in the place of options for the configured questions on the Business and Operational Risk. | **Prerequisites**: 1. **Rating Control** with **Radio** Shape and **Formula** control must be configured in the **Business** and **Operational Risk** in the Mange Change Record Transaction. 2. Main from should be configured with the Access Role Template. **Steps**: 1. Log in to the application as an Analyst. 2. Select the application as **Service Management** and the module as **Change**. 3. Navigate to **Form Designer** > **Manage Change Record**. 4. Select **CR ID** configured with Risk Questions in **Business and Operational Risk**. 5. Navigate to **Risk** tab. 6. Take the Risk Questionnaire by selecting the options on the configured the **Business and Operational Risk**. 7. Click **Save** in the **Manage Change Record** Form. 8. Go to **Change History** and verify the selected options values for the **Business and Operational Risk**. | N/A | | 77672 | Users are experiencing lag in text while typing in the **Symptom** and **Description** field. | **Steps**: 1. Log in to the application as an Analyst. 2. Select **Service Management**. 3. Navigate to **Incident** > **Manage Incidents**. 4. Incident Form - List page is displayed. 5. Click **New** to create an Incident. 6. Enter values in **Symptom** and **Description** field. 7. Verify if there is lag while typing in the field area. | N/A | | 77649 | Column Filters are not working on the details page, such as Manage Incident details page. | **Steps:** 1. Log in to the **Application** (App: Service Management) as an Analyst. 2. Click on the **Incident** icon. 3. Click on the **Manage Incident** form. 4. Click on **ID** hyperlink of any Incident. 5. Click on the user **Record History**. 6. Validate the column filters. | N/A | | 77636 | If the default view filter is cleared and if navigated to other page and back to current page, then records are not displayed as per the applied filter and also on the ‘Tenant’ tab incorrect record count is displayed. | **Prerequisites**: 1. Log in to the application as an Analyst. 2. Default filter should be applied (**Workgroup > Dynamic > Logged in User > Workgroup**). **Steps:** 1. Click on the **‘Filter’ icon > ‘Advance Filter**’ popup should be displayed. 2. Click on the ‘+ Add Filter Set’ and choose a field, operator and value and click **Apply**. 3. Click on the **‘Save as New View’** and provide **View name**. 4. Check the **‘Set as Default’** checkbox and click **Save**. 5. Verify the records count in **‘Tenant’** tab. 6. Navigate to **‘Advance Filter’** popup and click ‘**Clear All**’ button. 7. Navigate to **‘Manage Service Request**’ and navigate back to ‘**Manage Incidents**’ list page. Default View saved in above step 3, will be applied. 8. Verify whether the records related to default view is displayed. Verify whether the records count in **‘Tenant’** tab is based on the applied default view. | N/A | | 77694 | Error message 'Something went wrong. Please Try again”. validation message is displayed, while saving the **'Create Templates**' from Manage Change Record Details. | **Prerequisite**: Change Request should be created. **Steps**: 1. Log in to the application as an Analyst. 2. Select the application as Service Management and the module as Change. 3. Navigate to the **Manage Change Request** list page. 4. Open the created **CR ID > CR** details page will be displayed. 5. Click On the '**Create Templates**' button. 6. The '**Save Template**' popup page should be displayed. 7. Enter the Value into '**Template name**' and verify. | N/A | | 76942 | In the **Manage Change Request,** expanding the BR History tab initially shows **No Records Found**. However, when expanded second time, the BR details load correctly. | **Steps**: 1. Log in to the application as an Analyst. 2. Navigate to **Change** > **Manage Change Record**. The **Manage Change Record** List page is displayed. 3. Select any existing **CR ID** hyperlink. 4. On the **Manage Change Record** details page, select the **Change History** icon. 5. The **Audit Logs** for the record are displayed. 6. Navigate to **BR History** tab. Next to the date, select the **Expand** icon. 7. Verify the Logs. | N/A | | 77244 | The **Advanced Filter** pop-up displays **No results found** message when the user searches for a value in the **Workgroup** field, even though the value exists. | **Prerequisites**: 1. The Analyst must be on the **Manage Incident** List page. 2. The **Default Filter** (Dynamic - Logged In User - Workgroup) must be applied. **Steps**: 1. Log in to the application as an Analyst. 2. Navigate to **Incidents** > M**anage Incidents**. The **Manage Incidents** List page is displayed. 3. Click the ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-X1VVGRXZ.png?sv=2026-02-06&spr=https&st=2026-11-11T13%3A08%3A36Z&se=2026-11-11T14%3A08%3A36Z&sr=c&sp=r&sig=I%2FHoXBbxGNqbPb0uKQpHQFggOBx1SrOhyvcRCoL%2BdFE%3D) **Filters** icon and then select **Advanced Filter** icon. The **Advance Filer** pop-up appears. 4. Under **By Properties**, click **+ Add Filter** **Set**. 5. From the **Field** dropdown, select **Status**. 6. Select the **Is One Of** Operator and choose multiple values from the **Value** dropdown list. 7. Select the **Add** icon to add another filter row. 8. Similarly, configure the second row with the required **Field**, **Operator**, and **Value**. 9. Click **Apply** and verify that the correct results are displayed. | N/A | | 77362 | In the **Manage Problem Record** module, under **5 Why Analysis**, consider allowing multiple problem statements to be added before approving the RCA. After the RCA is approved, the system should automatically create the corresponding remediation actions | **Prerequisite**: In the **Manage Problem Record**, **5 Why** control must be configured in consumer form. **Steps**: 1. Log in to the application as an Analyst. 2. Navigate to **Problem** > **Manage Problem Records**. The Manage **Problem Records List** page is displayed. 3. Click **New** and in the **General** tab, enter all the mandatory fields. 4. Navigate to **RCA** tab, expand **RCA Methodology**. 5. Select the **5 Why Analysis** Methodology and enter **Problem Statement** for 5 Whys. 6. Click **Save** and verify. | N/A | | 77518 | End User is unable to view the created **Standard Template** in the **Import Template** popup while selecting **Change Type** as Standard. | **Prerequisites**: - CR must be created for the conditions such as **Change Type** as Normal and **Category** as Small. - Enable **Propose For Standard Change**. - Specify the **Standard Template Name**. **Steps:** 1. Log in to the Apex application as an Analyst. 2. Select the application as **Service Management** and **Module** as **Change**. 3. Navigate to **Manage Change Request List** page. Click **New**. 4. Select the **Tenant**. 5. Select the **Change Type** as Standard. The **Import Template** popup is displayed. 6. Verify the above-created Standard Template. | N/A | | 77698 | 1. Data is not loading after saving the record with the 5 Why analysis. 2. Data selected in 'Manage Problem Record' is not showing on the 'Approve Problem Record' page. | **Prerequisites:** **5 Why** control must be configured **Manage Problem Record** form. **Steps:** 1. Log in to the Apex application as an Analyst. 2. Select the application as **Service Management** and **Module** as **Problem**. 3. Navigate to **Manage Problem Record** page. 4. Select the T**enant** and specify the required mandatory fields. 5. Click **Save** to save the record. Open the same record and click **Authorize Record**. 6. Select the **Status** as RCA Submitted. 7. Navigate to **RCA** tab, select **Methodology** as 5 Why. 8. Specify the mandatory fields. Click **Save**. 9. Open the same record and verify the data. | N/A | | 77630 | Even though values are selected in the drop-down, the check boxes are not selected. | **Steps:** 1. Log in to the Apex application as an Analyst. 2. Select the application as **Service Management.** Navigate to **Manage Incidents – List** page. 3. Click **Filter** icon. 4. Click **Add Filter**. Select the field as **Workgroup**, Operator as **Is One Of** and select the required check boxes as values. 5. Click **Apply**. Again, click **Filter** icon and click **Advance Filter** icon. 6. Click **Apply**. Again, click **Filter** icon. The **Advance Filter** popup is displayed. 7. Click **Value** field for Workgroup field. 8. Verify if selected values check boxes are selected. | N/A | | 77697 | When a form name with 100 characters is specified, in the **Role** **Template**, **Screen** **Selection** stepper does not display the form name correctly. | **Prerequisite**: Application Designer must be on the Form Designer List page. **Steps**: 1. Navigate to **Service** **Management** > **Design** **Studio** > **Module** > **Incident** > **Form** **Designer**. 2. Click **New** and select **Start** **from** **Scratch**. 3. On the **General** page, enter 100 characters for the **Form** **Name.** **For** **example**: Enterprise_Incident_Management_Form_HR_IT_Facilities_Report_Log_Tracking_System_v1_2025_UIUX & Ticke 4. Enter all the other mandatory details and **Publish** the form. 5. Navigate to **Application** > **Access** **Control** **Centre** > **Role Template.** 6. Navigate to **Screen** **Selection** stepper. | N/A | | 77653 | An Analyst who is part of the Information Technology tenant's Master Workgroup can access records they should not see, even though they do not have access to the Human Resource tenant workgroup. Additionally, the Save button is incorrectly enabled for them in this context. | **Prerequisites**: 1. The user must be an Analyst in the Information Technology tenant’s Master Workgroup. 2. The same Analyst must not have access to the Human Resource Tenant. **Steps**: 1. Navigate to **Service** **Management** > **Incident** > **Manage** **Incidents**. The **Manage** **Incidents** list page is displayed. 2. Open any Incident in the Information Technology tenant. 3. In another browser window open the same incident in Human Resource tenant. 4. The user must be redirected to the Manage Incidents list page. | N/A | | 76936 | In the Problem Management module, the validations on the RCA tab are not functioning according to the specified conditions. | **Prerequisite**: Validations must be configured for the fields in the RCA multivalued group. **Steps**: 1. Navigate to **Service** **Management** > **Design** **Studio** > **Problem** > **Manage** **Problem** **Records.** 2. Select a Problem Record and navigate to **RCA** tab. 3. Click **Add**. | N/A | | 77600 | The configured Workflow on a Sub Form that is further with configured with Create Record functionality, is not working as expected. Record is not created after workflow initiation. | **Prerequisites:** 1. Workflow should be configured on Sub Form (VPN Access). 2. App Designer should be on the Design Workflow step. **Steps:** 1. Drag and drop **User Approval** component and configure it. 2. Drag and drop **Create Record** component and configure it with the below attributes, **Module**: Workorder **Form Type**: Sub Form **Form**: New Joinee Laptop Allocation. 3. Click **Save** and publish the Workflow. 4. Create a record that match to the above workflow Conditions. 5. Complete the workflow. Verify if the record is created. | N/A | | 77641 | The changes made in the properties of the **Methodology** attribute in the **Manage Problem Record** form is reflecting in the **Approve Problem Record** form. This is also seen the other way round. > [!NOTE] > Note > > The Approve Problem Record form is clone of the Manage Problem Record. | **Prerequisite:** Clone Approve Problem Record Form from Manage Record Form. **Steps:** 1. Log in to the Apex Application as an Application Designer. 2. Select **Service Management** Application. 3. Click settings icon and select **Design Studio**. 4. Navigate to **Problem Module** > **Form Designer** > **Manage Problem Record**. 5. Put the form in **Maintenance** mode. 6. Select the **RCA** tab and change **Methodology** attribute. 7. Observe for any conflict in the **Approve Problem Record** (Cloned Form). | N/A | | 77004 | Fishbone view diagram is not displaying upon clicking the icon that is present in the Approve Problem Record page. Upon clicking the icon, the entire panel is collapsing and inconsistency observed in Fishbone icon on the Manage Problem Record and Approve Problem Record pages. | **Steps:** 1. Log in to the Apex Application as an Application Designer. 2. Select **Service Management** Application. 3. Navigate to **Problem Management**. 4. Select **Manage Problem Record**. 5. Create **Problem Record**, enter all the mandatory fields and click **Save**. 6. Go to the same **Problem Record** and click **RCA** tab. 7. Add RCA by selecting the fields. 8. Submit the **Problem Record**. 9. Navigate to the **Approve Problem Record** page, click on **RCA** tab. 10. Click on diagram in RCA section and verify. On the same window click **Show All Types** and verify. | N/A | | 77624 | After Reconciliation acceptance, the workflow timeline was not displayed. None of the workflows were picked. | **Prerequisite**: Asset must be displayed in **Instore**, **Allocated**, **Deactivate** and **Reactivate** statuses. **Steps**: 1. Log in to the Apex application as an ITAM Analyst. 2. Select as **Asset Management** application. 3. Click **Fixed** in the submenu pop-up and navigate to **Fixed Asset List** page. 4. Click the **Allocate** status **Asset Code** hyperlink. Verify the displayed values. 5. Click the Reconciliation option, enter all the details in the **Reconciliation** popup. Click **SAVE**. 6. Click **CANCEL** on Asset Details page. 7. Log in to the Apex application as an End User. 8. Navigate to End User reconciliation page. 9. Click the Asset Code hyperlink. Click **Reconciliation** option and accept the reconciliation action. 10. Navigate to **Fixed Asset** list page and click the **Asset Code** hyperlink. 11. Verify the workflow timeline. Click the kebab menu icon and select **Deallocate** option. 12. Enter all the mandatory values and click **Save**. Verify the picked workflow. | N/A | | 77291 | **Symptom/Description** text disappeared in the UI. | **Steps**: 1. Log in to the Apex application as an Analyst. 2. Select Service Management application. 3. Navigate to **Incident** > **Manage Incident**. The **Manage Incident List** page is displayed. 4. Click **New** and select the desired **Tenant**. 5. Copy and paste the images to **Symptoms** and **Description** field. 6. Click the **Maximize** icon. 7. Enter the text into the **Symptoms** and **Description** field. 8. Click the edit icon and verify the entered text. | N/A | ## 6.3.1 Fixed Issues No bugs resolved in Crescendo 6.3.1 release—just enhancements to improve your experience. ## Patches Things just got better—check out the latest patches in this release: - [6.3.1 Patch 3](/summit-platform/docs/release-notes-crescendosp1-631#631-patch-3) - [6.3.1 Patch 2](/summit-platform/docs/release-notes-crescendosp1-631#631-patch-2) - [6.3.1 Patch 1](/summit-platform/docs/release-notes-crescendosp1-631#631-patch-1) ## 6.3.1 Patch 3 The following section provides key improvements introduced, Fixed Issues and known issues in Crescendo SP1 (6.3.1) Patch 3 release. - [Merged Releases](/summit-platform/docs/release-notes-crescendosp1-631#merged-releases-in-patch-3) - [New Feature](/summit-platform/docs/release-notes-crescendosp1-631#new-feature) - [Improvements](/summit-platform/docs/release-notes-crescendosp1-631#improvements) - [Known Issues](/summit-platform/docs/release-notes-crescendosp1-631#known-issues-in-patch3) - [Fixed Issues](/summit-platform/docs/release-notes-crescendosp1-631#known-issues-in-patch3) ### Merged Releases in Patch 3 This Patch 3 release is merged with the following releases: - Crescendo SP1 (6.3.1) build# 20250415.2 Release - HF10 Patch Releases - Crescendo 6.3.0 Patches > [!NOTE] > Note: > > Performance related changes are merged with this release. ### New Feature The following section provides a sneak-peek of the functionalities added for Design Studio in Crescendo SP1 (6.3.1) Patch 3 #### Design Studio Let's take a quick look at our Design Studio user personas. | ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/MSP Design Personas (1).png?sv=2026-02-06&spr=https&st=2026-11-11T13%3A08%3A36Z&se=2026-11-11T14%3A08%3A36Z&sr=c&sp=r&sig=I%2FHoXBbxGNqbPb0uKQpHQFggOBx1SrOhyvcRCoL%2BdFE%3D) | | --- | The following section provides a sneak-peek of the functionalities added for Design Studio. | | | --- | ### 6.3.1 Patch 2 ## 6.3.1 Patch 1