- 03 Sep 2024
- 5 Minutes to read
- Print
- PDF
Release Notes v6.1.0.1 HF04
- Updated on 03 Sep 2024
- 5 Minutes to read
- Print
- PDF
New Features
There are no new features or enhancements in this v6.1.0.1 HF04 release.
Known Issues
The following section provides details of known issues and workarounds in Apex v6.1.0.1 HF04:
Issue ID | Issue Description | Workaround |
154734 | The .eml and .msg attachments are not available in the tickets created via email-to-ticket functionality. | N/A |
155129 | The page loads more slowly when using the IF condition to create Work Orders in the Workflow Designer. | N/A |
154572 | Scheduler jobs such as Mail Parser jobs are getting stuck in an in-progress state and not getting completed. As a result of which new tickets are not getting created. | Republish scheduler of the affected mailbox after changing its status to maintenance. |
155464 | In email to ticket integration, entire emails were being attached as attachments, and occasionally, .txt files were being ignored. | N/A |
152921 | Upon logging to the application, https://<domainname.com>/ users were experiencing Form Under Maintenance intermittent issue. On the Incident, SR, or CR or any pages in the Platform Studio or Design studio. A lot of API executions were displaying as loop in app exception logs. | N/A |
155583 | System displayed the following warning message even without making any changes in the record. "You have Unsaved changes. Are you sure you want to cancel?" | N/A |
Fixed Issues
The following section provides details of fixed issues in Apex v6.1.0.1 HF04:
Issue ID | Issue Description | Scenario | Resolution |
---|---|---|---|
155220 | Category nodes in the General tab of the new incident were in expanded format. | Steps:
| Category nodes are displayed in collapsed format. |
155522 | The More placeholder was displayed for Symptom and Description on the Manage Incidents list page even if the text field was not too long. | Steps:
| If the Symptom or Description is not too long, the More placeholder is not displayed. |
155712 | The linked Work Order created by the designed workflow was not displayed in the Links tab of the SR. | Prerequisite: For a Sub Form or a Catalog, Workflow should be configured using the If condition and Create Record components. Steps:
| The Work Order linked to the SR is displayed in the Links tab. |
154766 | The success message after logging or updating an incident was not proper. | Steps:
| When new incident is created following message is displayed – Incident ID: XXXX created successfully. When incident is updated, following message is displayed – Incident ID: XXXX updated successfully. |
154147 | Slowness issue was reported while loading a page. | Prerequisite: Log in to Apex application with Analyst access. Steps:
| Page load time is within the acceptable duration and records are displaying correctly. |
155221 | User's First Name and Last Name were displayed when selecting a username for sending an email. | Steps:
| User's email ID is displayed when searching for a user to send an email. |
155469 | Time entry details for the General Type Service Window were not displayed for the 8*5 Problem Record Service Window. | Steps:
| The time entry details in the General Type Service Window are displayed without any issues. |
154474 | The configured Categories for the selected catalogs were not displayed after publishing. | Prerequisite: Create a new Service Request (SR) Category and Catalog. Steps:
| In the Category section, the configured categories are displayed as expected. |
155293 | In IncidentManagement module, View Other Workgroups filter was not maintaining its state when saved as a view. While the switch from off to on worked correctly, the reverse was not working. | Steps:
| View Other Workgroups filter is working as desired. |
155890 | When the user tried to print the Incident Details form using CTRL + P, the page was blank. | Steps:
| The Incident Details form can be printed using CTRL + P option without any issues. |
155230 | User could not raise a Service Request (SR) using a Catalog From to which the CC field was added.
The following error was displayed:
“Something went wrong. Please try again.”
The SR was submitted successfully when any value was entered in the CC field. The issue occurred when the CC field was blank.
Note: The CC field is a non-mandatory field. | Prerequisite:
Steps:
| User can raise a Service Request successfully without entering any value in the CC field. |
154033 | Users were having trouble in identifying more information in the Messages tab of a record. The three dots(...) which indicates more text must be replaced by …more with bold. | Steps:
| Messages tab displays …more on the record where more information has to be displayed. |
155446 | SLA Rule Stop condition was not working as expected upon selecting the correct option from the Status dropdown. | Prerequisite:
Steps:
| SLA Rule Stop condition is working as expected. |
155215 | System was not parsing the content based on the condition | Steps:
| System is able to parse the content based on the conditions |