- 17 Dec 2024
- 8 Minutes to read
- Print
- PDF
Release Notes v6.1.0.1 HF05
- Updated on 17 Dec 2024
- 8 Minutes to read
- Print
- PDF
New Features
There are no new features or enhancements in this v6.1.0.1 HF05 release.
Known Issues
The following section provides details of known issues and workarounds in Apex v6.1.0.1 HF05:
Issue ID | Issue Description | Workaround |
154734 | Attachments with .eml and .msg extensions are not getting attached to the tickets created via email to ticket functionality. |
|
155464 | Attachments were not parsed accurately, and entire emails were added as an attachment. |
|
156516 | The error message “An error occurred while processing your request” is displayed while trying to close Incident INC00248. It cannot be closed even after modifying fields, changing workgroup, changing states, etc. | N/A |
156607 | Users were experiencing discrepancies in the Service Requests Analyst Dashboard. All the information on the Dashboard was incorrect. Example: SRs resolved this month showed 1833, but the actual SRs Resolved Today show more than that. Similarly, all widgets and data information displayed on the Analyst dashboard were inaccurate. | N/A |
156996 | In Manage Incident form of Asset Management module, the Customer field should auto-populate based on the Serial Number field, and Requestor field should auto-populate based on Customer field. However, this is not working as desired. | N/A |
156837 | Menu: When pinned, sub menu gets unpinned at each refresh. Steps:
| N/A |
156567 | Inactive workgroups appear in the Workgroup dropdown when creating records. | N/A |
156819 | In the Message and Note widgets of the Apex application, there was excessive vertical space between lines in the entered text. | N/A |
Fixed Issues
The following section provides details of fixed issues in Apex v6.1.0.1 HF05:
Issue ID | Issue Description | Scenario | Resolution |
---|---|---|---|
156171 | There was a mismatch in the values of Workaround SLA Remaining Time and Resolution SLA Remaining Time for Incidents with Pending status on the list page and on the ticket details page. | Steps:
| The values of Workaround SLA Remaining Time and Resolution SLA Remaining Time for pending Incidents on the list page and ticket details page is the same. |
157237 | Work Orders created from the ServiceRequest Workflow were not linked in the Relationship (Links) tab. | Steps:
| Work Orders created from the Service Request Workflow are linked and displayed successfully in the Relationship (Links) tab. |
155856 | There was no provision to copy the content from the Change History page. | Prerequisite: Analysts should not have access to the specific workgroup. Steps:
| Copying of Timestamp and other content is possible in the Change History page. |
156943 | In the Change Module after CR submission, users were experiencing UI issue. Inappropriate arrow shape was visible on the CR ID’s Approval Timeline. | Steps:
| On the CR ID, Approval Timeline UI is displayed appropriately. |
156933 | Hyperlink in User Communication section under Messages tab in Incident and Service Request details page is not visible as a clickable link if the text length does not meet the threshold to trigger the "More" option for expanded view. | Steps:
| Hyperlink in User Communication section under Messages tab in Incident and Service Request details page is visible as a clickable link. |
157038 | User could not make any changes to three ServiceRequests (SRs) which belonged to the same catalog called AccessRequest. | Prerequisite:
Steps:
| User can make any changes to SRs belonging to the AccessRequest catalog without any issues. |
156895 | The values in Service Requests were not updated even when the Business Rule was operational. | Steps:
| The values in Service Requests are getting updated. |
157062 | The Incident Management list page column for User Location did not display any records. | Steps:
Note The records are displayed when user location is applied as a filter. | User Location records are displayed in the Incident Management list page. |
156822 | Spacing between categories in the category list of a new Incident form was too wide. | Steps:
| Spacing between categories in the category list of a new Incident form is optimized for better user experience. |
156075 | Advance Filter on the List page was not working as expected in the Incident Module. Example: After adding a filter Requestor.Customer in Manage Incidents form, let's say you have selected the values as Requestor.Customer = <customer_name>. However, if you want to change the value in the filter and search, the search was not working. The user had to click outside the text box and then go back for the value to take effect. | Steps:
| Advance Filter on the list page works appropriately. |
156126 | In any module, while creating an Incidenttoproblem ticket using FormRelations user was unable to add fields in the Target field as it gave a “Duplicate Field” error. | Steps:
| Users can add fields under The Target value option in Form Relations. |
156508 | The Category list was not sorting in alphabetical order. | Steps: 1. Login to the Apex application. 2. Navigate to Incident > Manage Incidents. 3. Click New > Select Tenant > Click on Category icon. 4. Verify if the Category and Sub-Category lists are sorted in alphabetical order. | The Category list is getting sorted in alphabetical order. |
156606 | On the Analyst and End user Dashboards, additional configured service portals were displayed, though access was not provided. | Steps:
| On the Analyst and End user Dashboards, only the configured service portals to which access is granted are displayed. |
157240 | Level 1 approvers were not able to choose the Level 2 approvers which are configured as User Selectable. | Steps:
Next,
Next,
| Level 1 approvers can choose the Level 2 approvers, which are configured as User Selectable. |
155563 | The refresh interval did not work as per the configured refresh interval on the Incident and Service Requests List page. | Steps:
| The refresh interval functions correctly as per the configured time interval on the Incident and Service Requests List page. |
155697 | After opening any Incident or Service Request, the title of tab was displaying <Customer_Name> instead of Incident or SR. | Steps:
Note The above is applicable for Service Request module as well. | Upon opening any Incident or Service Request, the title of tab displays Incident/Service Request number. |
157156 | In the Knowledge module, when selecting Manage Knowledge Records, the breadcrumb was incorrectly displayed as New Knowledge Records instead of Manage Knowledge Records. | Steps:
| The breadcrumb name is displayed as designed. |
154572 | The Mail Parser Job related to Payroll Incidents was continuously in-progress and was not restarting automatically. | N/A | This issue is managed by the Scheduler API Timeout configuration. Based on the specified timeout duration, the job will automatically restart if it has been in-progress for an extended period. |
Improvements
Improvement Name | Improvement Description | Benefits |
---|---|---|
Retrieve and update user profile pictures using Microsoft Graph API. | Configure the Azure_User_Profile_Image_API in the API Configuration that can be used to retrieve user profile images from Azure AD.
|
|