---
title: "Release Notes v6.1.0.1 HF09"
slug: "release-notes-v6101-hf09"
updated: 2025-08-13T05:50:46Z
published: 2025-12-17T09:27:34Z
canonical: "help.symphonysummitai.com/release-notes-v6101-hf09"
---

> ## 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 v6.1.0.1 HF09

## [](/new-tech-platform-mirror/docs/sneha-clone-apex-release-note-template#service-management)

- [Fixed Issues](/summit-platform/docs/release-notes-v6101-hf09#fixed-issues)[](/summit-platform/docs/release-notes-v6101-hf06#known-issues)
- [Known Issues](/summit-platform/docs/release-notes-v6101-hf09#known-issues)
- [Limitation](/summit-platform/docs/release-notes-v6101-hf09#limitation)

## Fixed Issues

The following section provides details of fixed issues in Apex v6.1.0.1 HF09:

| 162507 | When using the Import option to upload CIs to CMDB, an error message “Error occurred while processing record” is displayed. | **Steps:** 1. Log in to the Apex application as an Analyst. 2. Navigate to **CMDB** > **Infrastructure as a CI**. The list page of **Infrastructure as a CI** is displayed. 3. Click the **Import** icon and select **Upload File**. 4. Enter the required details in the **General** step, download the **CMDB** template, and fill the downloaded template with the **CI** data. 5. Click the **Import** icon, fill in the required details in the **General** tab, and click **Next**. 6. Click **Upload File** to upload the filled data template. Click **Submit**. An error message is displayed. | The following are the steps for configuration. **Steps:** 1. Check appsettings.json. "SummitApiInfo": { "ApiKey": "",}. The ApiKey should have a value. 2. Create a user with API Key Authentication and copy the API key using Copy icon in User page under Authentication tab. 3. Add the API Key under “SummitApiInfo” section in the appsetting.json file for Summit.RabbitMQ.Subscribe, Form Designer and common APIs. |
| --- | --- | --- | --- |
| 162506 | Users were experiencing SSO Authentication issue with the second **SAML** from the configured SAML list. This issue was faced when two users from different domains were imported and SSO was enabled. | **Steps**: 1. Log in to the Apex application. 2. Navigate to **Platform Studio** > **Access Control Centre** > **Add Authentication** > **SAML**. 3. Add multiple SAMLs. 4. Validate if the SSO Authentication is working as expected using **SAML**. | Users are able to successfully authenticate with the configured second **SAML** from the **SAML** list. |
| 159807 | **Priority** value for Change Records (CRs) was not automatically populating based on the selected **Urgency** and **Impact** values, although the Priority Matrix was correctly configured. | **Steps:** 1. Log in to the Apex application. 2. Navigate to **Change** > **Change Request** > click **Manage Change Requests** to view Manage Change Requests list page. 3. Click CR ID hyperlink to view the CR details. 4. Verify that value of **Priority** for the CR is correct as per the selected **Urgency** and **Impact**. | **Priority** value for Change Records is automatically populating based on the selection of **Urgency** and **Impact** values, as per the configured Priority Matrix. |
| 160139 | The **Child** field was not displayed while accessing a newly created **Service Request** with parent-child dependency. | **Prerequisites:** 1. Create the Parent and Child **Master** types with one master value in each. 2. Create few single-choice controls having **Common** **Master** as a data source in the required SR **Catalog Sub-Forms**. **Steps:** 1. Log in to the Apex application as an **End User**. 2. Navigate to the **Service** > **My** **Service** **Requests**. The **My Service Requests** list page is displayed. 3. Select all fields including drop-down fields having **Common Master** as data source. 4. Open the newly created SR. 5. Verify if all the fields are rendering properly. | Parent-child fields are rendering properly while accessing the newly created **Service Request**. |
| 157447 | The **Filter** was not working in the **Business Rule Designer** list page. | **Steps:** 1. Log in to the Apex application as an **Application Designer**. 2. Navigate to the **Design Studio** > **Module** > **Business Rule Designer**. The **Business Rule Designer** list page is displayed. 3. Click **View** drop-down and **Add New View**. 4. Click **Add Filter** and add filters (Status is New and Business Rule Name contains Major) . 5. Click **Apply** and on the list page, click **Save as New View**. 6. Enter the **View Name** and enable the **Set as Default** check box. 7. Click **Save**. | The **Filter** is working as per design in the **Business Rule Designer** list page. |
| 160213 | In the **Change** **Management** module, in the **Manage** **Change** **Requests** form the version number was displayed incorrectly. | **Steps:** 1. Log in to the Apex application as an **App** **Designer**. 2. Navigate to **Design** **Studio** > **Module**. Select the module as **Change** **Management**. 3. Click **Form** **Designer**. 4. Click and open the **Manage Change Request** form. Verify the version number on the top panel. 5. On the **Publish** step, change the status of the form to **Maintenance**. 6. Verify the version number incremented by one on the top panel. 7. On the **Design** **Form** step, perform any change to any control. 8. Change the status of the form to **Published**. 9. Verify the version number incremented by one on the top panel. | The version number in the **Manage** **Change** **Requests** form is displayed appropriately. |
| 159940 | The word limitation feature did not function correctly for the following **Rich Text Editor** fields in the **Manage Change Requests** form: - **Change Title** - **Change Description** - **Trigger for Change** | **Steps**: 1. Log in to the Apex application as an **Application Designer**. 2. Navigate to the S**ervice Management** > **Settings** icon > **Design Studio** > select **Change** module > **Form Designer** > **Manage Change Requests**. 3. Add long text in the **Rich Text Editor**. 4. Click **Settings** icon to view the **Long Text** dialog box. 5. Select **Validations** tab and select the **Less Than** validator to mention the number of characters. 6. Click **Next** and publish the **Form**. | In the **Manage Change Requests** form, the word limitation feature is working without any issue. |
| 160327 | Issue with the **Date Picker** field on the **Catalog Form** under the **Service Request** module. A discrepancy in time zone settings caused the issue. When the system operated in a UTC+ time zone, it incorrectly subtracted the date difference, resulting in the date being set to the previous day. | **Steps**: 1. Log in to the Apex application as an **End User**. 2. Select the **Service Management** application. 3. Navigate to **Service Request** > **My Service Requests**. **My Service Requests List** page is displayed. 4. Click **New** to raise a new **Service Request (SR)**. 5. Select the required **Catalog** **Form** and verify the **Date Picker** field. | The **Date Picker** field on the **Catalog** **Form** under **Service Request** works fine without any issues. |
| 160595 | System was displaying and invalid object error while publishing the form when form was created using existing table option. | **Steps:** 1. Navigate **Design Studio** > **Form Designer**. 2. Create a Form using existing table by choosing **Form Table** as Existing Table under **General** step. 3. Publish the form | System does not display any error while publishing the form when form is created using existing table option. |
| 160272 | The **Scheduler** status in the **CMDB** module was not updated according to the specified conditions. | **Steps:** 1. Log in to the Apex application. 2. Navigate to the **Module** and select **CMDB** from the dropdown. 3. In the **Designers** section, click **Scheduler**. 4. Click **New** to create a new schedule. 5. In the **General** step, fill in all the required details and select **Infrastructure as a CI** from the **Table** dropdown, then click **Next**. 6. In the **Frequency** step, provide the required details and click **Next**. 7. In the **Condition** step add filter conditions using the **Add Filter Set** option. 8. In the **Actions** step, configure **Update Fields** action. 9. Under **Advance Configuration** section, the default value 100 is displayed in the **Batch Size** field. 10. Click **Publish** to publish the **Scheduler**. NoteThe ideal **Batch Size** for processing records is between 50 and 200. | The **Scheduler** status in the **CMDB** module is updated based on the configured **Batch Size** specified in the **Update Fields** tab. |
| 159856 | User was unable to add more characters to the Signature in the **Notification Element** editor. | **Steps**: 1. Log in to Apex Application. 2. Navigate to **Design Studio** > **Module** > **Notification Designer** > **List** page. 3. Click **New**, to create a new notification designer. 4. Enter **General** details and select **Email** Medium. 5. Create Notification Element with image and other details in the **Description** field. 6. Click **Submit.** 7. Verify if the Notification Element accepts more characters. | User can add more characters to the Signature **Notification Element**. |
| 160524 | **Work Order** created from **Change Record** was not displayed as Relationship under the **Links** tab. | **Steps**: 1. Log in to Apex Application as an Analyst. 2. Navigate to **Change** > **Manage Change Requests**. 3. Select **CR ID** and then click on the **Links** tab. 4. Create **Work Order** and verify if displaying as **Relationship**. | **Work Order** created from **Change Record** is displayed as Relationship under the **Links** tab. |

## **Known Issues**

The following section provides details of known issues and workarounds in Apex v6.1.0.1 HF09:

| **Issue ID** | **Issue Description** | **Scenario** | **Workaround** |
| --- | --- | --- | --- |
| 157876 | The View list in Incident queue is empty after closing the Incident page. | **Steps:** 1. Log in to the Apex application as an **Analyst**. 2. Navigate to **Incident** > **Manage** **Incidents**. The **Manage** **Incidents** list page is displayed. 3. Click **View** > **Saved** **Views**. NoteThis scenario occurs inconsistently and only in specific situations. | N/A |
| 159895 | When trying to upload a .txt file with the content **<?xml version="1.0" encoding="UTF-8" standalone="yes"?>** in the **Attachments** tab for Incidents, an error message "Invalid file content" is displayed. | **Step****s:** 1. Navigate to **Incident** > **Manage** **Incidents**. 2. Click **New** to create a new incident. 3. In the **Attachments** tab, upload a .txt file that includes the content **<?xml version="1.0" encoding="UTF-8" standalone="yes"?>**. 4. On the **Manage** **Incidents** **List** page, click any Incident ID. 5. In the Attachments section, upload a .txt file that includes the content **<?xml version="1.0" encoding="UTF-8" standalone="yes"?>**. | N/A |
| 159748 | Business Rule is not getting executed for Service Request (SR) in new state. | **Prerequisites:** 1. Log in to the Apex application. 2. Click![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-1731577695297.png)> **Design** **Studio**. 3. Select **Module** as **Service** **Request**. 4. Navigate to **Designers** > click **Business Rule Designer** > click **New**. 5. In the **General** step, fill in all the mandatory fields > click **Next**. 6. In the **Trigger** step, fill in all the mandatory fields > click **Next**. 7. In the **Condition** step, select the condition > click **Next**. 8. In the **Actions** step, fill in all the mandatory fields > click **Next** > Click **Publish**. **Steps:** 1. Log in to the Apex application. 2. Navigate to **Service** **Request** > click **My Service Requests** to go to Service Request list page. 3. Click **New** to log a new SR using a catalog. 4. Click the ID hyperlink of the created SR from the list page. The status of the SR is ‘New’. 5. Click![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-1731578173566.png)> **Change History**. |  |
| 156119 | When adding a condition for the Change Category in Workflow Designer, the Tree View control fails to load values for Infrastructure. | **Steps**: 1. Log in to the Apex application as an Application Designer. 2. Navigate to the **Service Management** > **Settings** icon > **Design Studio** > **select Change module** > **Workflow Designer**. 3. Click **New** to create a new **Workflow**. 4. Enter the required details and click **Save**. 5. Click **Next** to navigate to **Set Trigger & Conditions** step. 6. Click **Add Filter Set** to add new condition. 7. Select the following fields with corresponding values: 1. **Field** – Manage Change Requests 2. **Operator** – Is 3. **Value** – Infrastructure | N/A |
| 159521 | Fields that are hidden using Validation controls are becoming visible after submitting the Change Request (CR). | **Steps**: 1. Log in to the Apex application as an **Application Designer**. 2. Navigate to the **Service Management > Settings icon > Design Studio > select Change module > Form Designer > Manage Change Request**s. 3. Drag and Drop the **Long Text** in the **Rich Text Editor**. 4. Click gear icon to view the L**ong Text** dialog box. 5. Select **Validations** tab and configure fields as **Hidden** and **Conditions Meet** - When category is **Version Upgrades**. 6. Click **Next** and publish the form. 7. Log in to the Apex application as an **End User**. 8. Navigate to **Change** > **My Change Requests**. 9. Select the required **Tenant** and **Category**. 10. Verify the fields that are hidden when all other mandatory details are filled and submitted. | N/A |
| 159934 | Automated Work Orders are not created from the Workflow. | **Prerequisite**: 1. A **Workflow** must be configured for the **Service****Requests** to create automated **Work** **Orders**. **Steps**: 1. Log in to the Apex application. 2. Select the **Service****Management** application. 3. Navigate to **Service Request** > **My Service Requests**. 4. The **My Service Requests List** page is displayed. 5. Click **New** to create a **Service Request (SR)**. 6. Enter all the required details and click **Submit**. | N/A |
| 159942 | In the **Change Management** module, when adding a change category in the **Workflow**, setting the **Trigger** **Condition**, and clicking on **Save**, the fields become blank every time. | **Steps**: 1. Log in to the Apex application. 2. Select **Service Management** application. 3. Click the gear icon and select **Design Studio**. 4. Select **Change** from the **Module** drop-down. 5. Select **Workflow Designe**r. The **Workflow Designer List** page is displayed. 6. Click **New** to create a new Workflow. 7. Enter all the relevant details in the **General** step and click **Next**. 8. Enter the details in the **Set Trigger & Conditions** step, click **Save**, and verify the result. | N/A |
| 159182 | The validation error message verbiage to be changed from “Review the validation error on the bottom of the control(s).” to “Review the validation error under the missing field(s).” | **Steps:** 1. Log in to the Apex application as an End User. 2. Navigate to **Manage Incidents** > Click **New.** The **Incident details** page is displayed. 3. Select the required **Tenant** and click **Save**. 4. Observe the toast message. | N/A |
| 159377 | For few catalogues the following error is appearing while submitting it. “Something went wrong. Please try again.” | **Steps**: 1. Navigate to **Manage Service Request** page 2. Submit the catalog and observe the submission. | N/A |
| 160276 | Information in the **Assigned To** section, including **Work Group** and **Analyst**, is missing when saved or resolved Service Requests (SRs) are opened. | **Steps:** 1. Log in to the Apex application. 2. Navigate to **Service Request** > **Manage Service Requests**. The **Manage Service Request** List page is displayed. 3. Click **SR ID** hyperlink. 4. In the **Assigned To** section of saved and resolved SRs, verify the **Work Group** and **Analyst**. | N/A |
| 159014 | The user is encountering a 504-error message when attempting to export **Daily** **Incident** report. | **Steps:** 1. Navigate to **Reports** > select module as **Incident**. 2. Click **Reports**. 3. Open the **Daily** **Incident** report. 4. Click **Filter** and choose the **Registered** **Time** for a duration of one month. Click **Export**. | **Daily** **Incident** report data can be exported for one month only. |
| 158685 | The UI occasionally experiences significant lag while typing the **Messages** and **Notes to Self** sections. | **Steps:** 1. Log in to the application. 2. Navigate to **Incidents** > **Manage Incidents**. The **Manage Incident List** page is displayed. 3. Click **Incident ID** hyperlink. 4. In the **Messages** tab, enter description for **Messages** and **Notes for Self** sections. NotesThis issue is applicable to Service Request (SR) module as well. | N/A |
| 157384 | Users are experiencing issue after submitting the new SR Catalog. The mandatory fields with data values are disappearing. | **Steps**: 1. Log in to the Apex application. 2. Navigate to **Service Request** > **My Service Request** > **Select any Catalog**. 3. Enter values for all the mandatory fields. 4. Click **Submit**. 5. Open the SR in **Manage Service Request** list page and verify the fields under **Catalog Details** tab. | N/A |
| 160204 | **Issue 1**: User logged a new incident by assigning a Workgroup, after submitting the Status displays as New and Workgroup attribute is null. **Issue 2**: After assigning the ticket to Analyst, the status of the ticket will display as In-progress, if the same ticket is opened again the Status will change to Assigned. The Workgroup and Analyst attributes will be null. **Issue 3**: If we map any role template to the Category based, the dropdown values options are not displayed | **Steps**: 1. Log in to the Apex Application. 2. Navigate to **Incident** > **Manage Incidents** >**Incident List page**. 3. Click **New**. 4. Validate the **Status** field. | N/A |

## **Limitation**

Convert Incident to Service Request functionality is not working as intended within the Incident module.