- 12 Dec 2024
- 10 Minutes to read
- Print
- PDF
Release Notes v6.1.0.1 HF09
- Updated on 12 Dec 2024
- 10 Minutes to read
- Print
- PDF
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:
| 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:
| 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:
| 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:
Steps:
| 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:
| 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:
| 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:
| Steps:
| 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:
| 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:
| 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:
Note The 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:
| 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:
| 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:
Note This 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. | Steps:
| N/A |
159748 | Business Rule is not getting executed for Service Request (SR) in new state. | Prerequisites:
Steps:
| |
156119 | When adding a condition for the Change Category in Workflow Designer, the Tree View control fails to load values for Infrastructure. | Steps:
| N/A |
159521 | Fields that are hidden using Validation controls are becoming visible after submitting the Change Request (CR). | Steps:
| N/A |
159934 | Automated Work Orders are not created from the Workflow. | Prerequisite:
Steps:
| 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:
| 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:
| 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:
| N/A |
159014 | The user is encountering a 504-error message when attempting to export Daily Incident report. | Steps:
| 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:
Notes This 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:
| 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:
| N/A |
Limitation
Convert Incident to Service Request functionality is not working as intended within the Incident module.