---
title: "Release Notes v6.1.0.1 HF08"
slug: "release-notes-v6101-hf08"
updated: 2025-03-28T09:05:36Z
published: 2025-12-17T09:27:34Z
canonical: "help.symphonysummitai.com/release-notes-v6101-hf08"
---

> ## 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 HF08

## Improvements

Following improvement is introduced in this v6.1.0.1 HF08 release.

| **Improvement Name** | **Improvement Description** | **Benefits** |
| --- | --- | --- |
| Implement color coded icons on **SLA Remaining Time** column in the List page. Applicable to all the modules that include SLA. **User Persona**: Analyst | The SLA progress bar on the list page of Incident and SR Modules display elapsed time with (%) percentage. New icons that display state of SLA is displayed next to the progress bar to help color blind users. For more information, refer [Manage Incident List](https://help.symphonysummitai.com/summit-platform/docs/list-page-manage-incident#sla-remaining-time) and [Manage Service Request List](https://help.symphonysummitai.com/summit-platform/docs/manage-service-request-list-page#sla-remaining-time). | - Easily identify the SLA Status with a quick glance on the List page. - Hover over on the SLA progress bar provide accurate details about the elapsed time without the need for navigation to each record. |

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

NoteFor more information on prerequisites of Apex v6.1.0.1 HF08, refer [this link](/summit-platform/docs/prerequisites-1).

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

## Fixed Issues

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

| Issue ID | Issue Description | Scenario | Resolution |
| --- | --- | --- | --- |
| 159531 | In the CR, **Multi-Valued Group** was displaying HTML tags. | **Steps**: 1. Log in to the Apex application as an Analyst. 2. Navigate to **Service Management** > **Change****Management** > **New Change Request**. 3. Enter details in the **Multi-Valued Group** and validate. | In the CR, **Multi-Valued Group** is not displaying HTML tags. |
| 158933 | User was unable to clear one or more **Tenant** value(s) in the field while configuring an SLA. | **Steps**: 1. Log in to the Apex application as an Application Designer. 2. Select **Design Studio** > **Incident Management** > **SLA Designer** > **SLA Value**. 3. Verify **Response SLA** and **Resolution SLA** Tenant values, validate by clearing any one Tenant. NoteThe SLA Rule/Value must be non-default and in create mode. | One or more **Tenant** values can be cleared while configuring an SLA. |
| 156842 | **SLA Remaining Time** colors on the records were not useful for color blind users and change was requested. | **Steps**: 1. Log in to the Apex application as an Analyst. 2. Navigate to **Incident Management** > **New**. 3. Create a new Incident. 4. Validate the SLA colors and icons on SLA Remaining Time on the Incident List page. NoteThis is applicable across modules where the SLA is considered. | **SLA Remaining Time** colors and icons on the list page are displaying according to the requested change. |
| 157787 | There were significant delays when opening the list page, particularly when handling a large number of records. Additionally, the "AD Azure Import" scheduler was unresponsive and failed to open as expected. | **Prerequisites:** 1. Log in to the Apex application. 2. Navigate to **Design Studio** > **Scheduler** > click **New.** 3. In the **General** tab, fill in all the mandatory fields. 4. Select **Scheduler** **Type** as **Custom** **Event**. 5. Select **Web Server** from the dropdown menu of **Execute at** > click **Next.** 6. In the **Frequency** tab, select the **Schedule Type** as **Recurring**. 7. Select the **Daily Frequency** as **One Time.** 8. Fill in all the other mandatory fields > click **Next**. 9. In the **Actions** tab, select the **Call API** and configure the API and the required field mappings > click **Publish.** **Steps:** 1. Log in to the Apex application. 2. Navigate to **Design** **Studio** > **Scheduler**. 3. Click on the ID hyperlink. 4. Navigate to **Actions** tab > **Call API** > **Advance Configuration** > **Days to Archive Records**. Provide the number of days of which you want to archive the records. The minimum number of days is 1. If no input is provided, the default is 28 days. 5. To view the archived records, click![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-1730206875500.png) to view the job history > enable **Include Records Impacted from Archived Data**. | Data Archive feature is implemented in Call API, that allows to archive all impacted records. So, list page loads without any delay. |
| 158719 | When logging a new incident on the **New Incident** page, the **Requestor** field was limited to search requestors by username only. | **Steps:** 1. Log in to the Apex application. 2. Select the required module from the App Portal. 3. Navigate to **Incidents** > **My Incidents**. 4. Click **New**. 5. Specify the username or email ID in the **Requestor** field to search the requestor. | When logging a new incident on the **New Incident** page, the **Requestor** field allows to search requestors by username and email ID. |
| 157794 | The downloaded CMDB template from **Infrastructure as a CI** does not successfully import unique values. | **Steps:** 1. Log in to the Apex application. 2. Navigate to **CMDB** > **Infrastructure as CI**. 3. Click ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-1730284535618.png)**Import** icon and select **Upload File**. 4. Select the required fields and click **Download.** 5. Download the CMDB template and add unique values under the **Serial Number** column in the template. 6. Click **Next** and upload the downloaded CMDB template. | The downloaded CMDB template from **Infrastructure as a CI** imports unique values. |
| 159248 | When loading a list, the first load had an inaccurate page count and failed to load all items. For example, if the page was set to load 50 records, it only loaded 20. This issue occurred when viewing the list of incidents. | **Steps**: 1. Log in to the Apex application as an Analyst. 2. Navigate to **Service** **Management** > **Incident** > **Manage** **Incidents**. **Manage** **Incidents****List** page is displayed. 3. Change the **View** to **All open Items**. 4. Click the first record on the list page and click **Cancel**. 5. Changed the **View** to **See All Closed Things.** 6. On the list page, change the pagination value to 20. Set the refresh interval as one minute. 7. After one minute, refresh and verify the records count. | The list page loads all the records as per the page count without any errors. |
| 155633 | User could not set the custom Approvers from Custom Workgroups in the Workflow Designer. | **Steps**: 1. Log in to the Apex application as an Application Designer. 2. Select **Service** **Management** application and click the gear icon to select **Design** **Studio**. 3. Select the required module from **the Module** drop-down. 4. Select **Workflow** **Designer** and click **New**. 5. Provide the relevant details in **General** and **Set** **Trigger** **&** **Conditions** and navigate to **Design** **Workflow** step. 6. Drag and drop the **User Approval** option and click the kebab menu to select the **Configure** **Properties** option. 7. Provide the required information in the **General** tab. 8. Select **Role****-Based Approval** from **Approval** **Type** drop-down. 9. Under **Select Approval Role (Dot Walking)** field, type **Workgroup** and select **Analyst**. | User can set the custom approvers from Custom Workgroups in the Workflow Designer successfully without any issues. |
| 158267 | The user created a **View** on the **Manage** **Incidents** **List** page, and it worked as expected. However, when the page was refreshed, it displayed **Save as a New View** and **Save Changes** even though the filter had not changed. | **Steps**: 1. Log in to the Apex application as an Analyst. 2. Navigate to **Service****Management** > **Incidents** > **Manage** **Incidents**. **Manage** **Incidents** **List** page is displayed. 3. Create and save a **View** as per the requirement. Refresh the page and verify the result. | **View** functionality saves and displays the views created without any issues. |
| 157411 | Notifications were not getting triggered to the **Record Attribute Group** recipients in the configured Scheduler. | **Steps:** 1. Log in to the Apex application. 2. Click **Scheduler** > click **New**. 3. Select **Scheduler Type** as **Custom** **Events**. 4. Fill in all the mandatory details > click **Next**. 5. Fill in all the details in **Frequency** step > click **Next**. 6. Click **Notify Recipients** in **Actions** step. Select **Single Record per Notification** from **Records to be sent for Notification** dropdown. 7. Navigate to **Recipients** > select **Record Attribute Group** in the **To** field > search and add the recipients. When selecting the Record Attribute Group, only groups configured for the same tables as the Scheduler (under the **General** tab) are visible. 8. Select the **Group**. 9. Click **Next** > **Publish**. **Note:** - This feature is currently not applicable for **Cc** and **Bcc** fields. - While configuring **Record Attribute Groups**, if the **Priority** and **Impact** values are same for two users, then notification is sent to both the users. | Notifications are getting triggered to the **Record Attribute Group** recipients in the configured Scheduler. |
| 158267 | The configured **View Filter** functioned properly on the **Incident** list page until a refresh occurred. After refreshing, the filter disappeared, and only the **Save as New View** and **Save Changes** options were visible. | **Steps**: 1. Log in to the Apex application as an **Analyst**. 2. Navigate to **Incident** > **Manage Incidents**. The **Incident** list page is displayed. | The configured view filter continues to function correctly after refreshing the Incident list page; however, the **Save as New View** and **Save Changes** options do not appear. |
| 159401 | In the **Manage Service Requests**, the **Asset Customer** values were not displayed despite being configured, which restricted the user from selecting the **Requestor** value from the field. | **Steps**: 1. Log in to the Apex application as an **Analyst**. 2. Navigate to the **Manage Service Requests** and click **SR ID** hyperlink. 3. In the **Specifications** tab, select serial number from the list. 4. Select **Requestor** value from the list, if the values are not displayed to select in the **Asset Customer** field. | The configured Asset Customer values are displaying without any issues. |
| 158770 | In the **Service Request** module, when an analyst was creating an SR for an end user, the validation controls were not displayed. | **Prerequisites:** 1. Navigate to **Design** **Studio** > **Module**. Select the module as **Service** **Request**. 2. Click **Form** **Designer**. 3. Create a new **Service** **Catalog** form with **Validation** controls. **Steps:** 1. Log in to the Apex application as an Analyst. 2. Navigate to **Service** **Request** > **Manage** **Service** **Requests**. 3. Click **New** to create a new service request. 4. Enter the required details on the **General** tab. 5. On the **Catalog** **Details** tab select the created catalog. | The validation controls are displayed and working as expected in the **Service** **Request** module. |
| 158186 | The Long Text field was not getting displayed in expandable and scrollable format. | Prerequisite: Incident **Status** must be Closed with **Steps**: 1. Navigate to **Manage Incident** details page. 2. Click Incident ID hyperlink. 3. Observe the **Long Text** field. | The Long Text field is getting displayed in expandable and scrollable format. |
| 154848 | When selected saved view, it was not displaying the records per page as per the saved view on the list page. | **Prerequisite**: In **Manage Service Request List** form builder page, specify **Default Records per Page** as 10 per page. **Steps**: 1. Navigate to **Manage Service Request list** page and filter the page with some values. 2. The records are displayed with filtered data. 3. Manually modify the Records per page. For Example: 20 4. Save this view. 5. Refresh the list page and the filtered records will refresh and again it will display default records per page as 10. 6. Select the Saved view with 20 Records. 7. Observe the page view default value. | When selected saved view, it is displaying the records per page as per the saved view on the list page. |
| 158184 | Unable to upload values for child fields in the Import Template. | **Prerequisites:** 1. Create a field in **Common Master** with a parent value and another field as the child value of the parent field. 2. Add these fields as single-choice dropdowns and map them as parent and child. 3. Download the Template in the Analyst configuration and add the parent and child values according to the dropdown option. **Steps:** 1. Log in to the Apex application as an Analyst. 2. Navigate to **CMDB** > **Configuration** **Item** > **Infrastructure** **as** **a** **CI**. 3. Click the **Import** icon on the top panel and select **Upload File**. 4. Fill the mandatory fields and click **Next**. 5. Upload the file and click **Submit**. | Values can be uploaded for the child fields in the Import template. |

## **Known Issues**

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

| **Issue ID** | **Issue Description** | **Scenario** | **Workaround** |
| --- | --- | --- | --- |
| **159252** | **Duplicate user accounts seen within the application.** | **Steps:** 1. **Log in to the Apex application.** 2. **Validate the user list.** | **N/A** |
| 155725 | On the **Priority Matrix** **List** page in **Change Management** module, the ID number resets when a new Priority Matrix is configured. | **Steps:** 1. Log in to the Apex application. 2. From the **Module** tab, select **Change.** 3. Navigate to **Configurations** > **Change** **Matrices.** 4. Click **Priority Matrix.** 5. Click **New** to configure a Priority Matrix. 6. Select all the required fields and click **Save**. | **N/A** |
| 159073 | Unable to import CMDB Network and Server data. | **Steps:** 1. Log in to the Apex application as an Analyst. 2. Navigate to **CMDB** > **Configuration Item** > **Infrastructure as a CI**. 3. Click **Import** icon on the top panel and select **Upload File**. The **Import Records** pop-up is displayed. 4. Enter the **Tenant** and **Form Type** and select the **Download Template** as Excel. Click **Download**. 5. Fill the required data in the template. 6. Click the Import icon and click **Next**. 7. Upload the file and click **Submit**. | N/A |
| 157447 | The filter is not working on the **Business Rule Designer** list page. | **Steps:** 1. Log in to the Apex application as an Application Designer. 2. Navigate to **Design** **Studio** > **Module** > **Business** **Rule** **Designer**. 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**. | N/A |
| 159451 | The preproduction environment is too slow and not responsive for an extended time. | **Steps**: 1. Log in to the preproduction environment and verify the speed of the application. | The application pool should be recycled in a shorter duration to release the memory. |
| 159403 | On the **Service Request** and **Incident** list pages, the **Search** icon is not displayed. | **Issue I** - Incident Steps: 1. Log in to the Apex application. 2. Navigate to the **Incident** > **My Incidents**. **Issue II** – Service Request 1. Log in to the Apex application. 2. Navigate to the **Service Request** > **My Service Requests**. | N/A |
| 158685 | The Apex application is intermittently slow when entering any notes or messages in the **User** **Communication** and **Private** **Logs** tabs for the **Incident** and **Service** **Request** modules. | **Steps:** 1. Navigate to **Incident** > **Manage** **Incidents**. 2. Click any **Incident** **ID** to open an incident. 3. Click the **Messages** tab and type any message in the **User** **Communication** or **Private** **Logs**. | N/A |
| 159206 | While searching for any ticket number using the global search option, the Apex application is running slow. | **Steps:** 1. Navigate to **Analyst** **Dashboard**. 2. Search for any existing ticket by entering the ticket ID number. | The application pool should be recycled more frequently to free up memory. |
| 157447 | In the **Business** **Rule** **Designer**, the default view is set in the **Filters**, yet the filters are displaying incorrect values. | **Steps:** 1. Navigate to **Design** **Studio** **Module** > **Business Rule Designer**. 2. On the list page, click **View**. Click **Add New View**. 3. Click **Add Filter** to add new filter values. Click **Apply**. 4. Click **Save as New View**. Enter a name for the view and select the "**S****et as Default**" checkbox. 5. Click **Save** to save the default view. 6. Close the **Business** **Rule** **Designer** page. 7. Reopen the **Business** **Rule** **Designer** page to view the default filter. | To view the total number of Business rules created, check the pagination count. |
| 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 |