- 07 Oct 2024
- 6 Minutes to read
- Print
- PDF
Release Notes v6.1.0.1 HF06
- Updated on 07 Oct 2024
- 6 Minutes to read
- Print
- PDF
New Features
Following enhancement introduced in this v6.1.0.1 HF06 release.
Improvement Name | Improvement Description | Benefits |
SLA Restart Feature when the SLA is in Active or Completed state. User Persona: Application Designer | This enhanced feature allows to Restart an SLA for the defined condition in the Filter Set based on its Active or Completed state. For more information, refer to SLA Restart. |
|
Known Issues
The following section provides details of known issues and workarounds in Apex v6.1.0.1 HF06:
Issue ID | Issue Description | Workaround |
157172 | Refer back option is not available in the Workflow to refer back a record. | N/A |
157411 | Scheduler was configured to notify the escalation to the selected Record Attribute Groups. Based on the condition match, it should trigger to the specific user of the selected group. Prerequisites:
Steps:
| N/A |
155464 | Text files with extension .txt are not getting attached to the tickets. | You can attach files with 33 extensions to the tickets. The allowed extensions of these 33 file types are: .3gp,.m4v/MP4,.docx,.png,.html,.pdf,.ppt,.mp3,.ogg,.eml,.ogv,.odt,.wav,.mp4/M4V,.m4a,.pptx,.xlsx,.msg, .jpeg,.zip,.xls,.pps,.gif,.doc,.wmv,.ppsx,.txt,.avi,.mpg,.jpg,.webp,.json, and .sql |
154734 | The attachments with .eml and .msg extensions are unavailable in the tickets created through email-to-ticket functionality. | N/A |
157384 | Mandatory field’s data was not getting displayed. | N/A |
157501 | In the Change Management (CM) module, while users can select the Primary Owner, they cannot select the Secondary Owner. Secondary Owner is a multiselect control which is currently not supported. |
|
157501 | During workflow configuration, users can select the Primary Owner of the workgroup as approver, however, system does not currently support the selection of a Secondary Owner as an approver. The Secondary Owner workgroup option is a multi-selection control, which is not supported currently. |
Fixed Issues
The following section provides details of fixed issues in Apex v6.1.0.1 HF06:
Issue ID | Issue Description | Scenario | Resolution |
---|---|---|---|
157422 | In the Change Management module, certain records requiring approval from at least one approver, as per the configured Workflow, were still displaying a "Pending for Approval" status even after one approver has approved it. | Prerequisites:
Steps:
| In the Change Management module, records requiring approval from at least one approver, as per the configured Workflow, show status as ‘Approved’ after being approved by at least one approver. After approval from one approver, the status for other approvers is displayed as Approval Not Required. |
157734 | The configured role was not mapping to the user. | Steps:
Note This is applicable for User Role Mapping at Application level as well. To validate the above steps, navigate to Design Studio > Application > Access Control Center > User Role Mapping. | Configured Role is mapping correctly to the user. |
156437 | Reminders for both new and old records are sent multiple times to notify the recipients. | Steps:
| Reminders are sent only for new records to notify the recipients. |
157954 | Analysts were unable to link any incident or other records to an incident. | Steps:
| The Link dropdown functions correctly, allowing to link incident- or other records to an incident. |
157477 | In the Change Management module, undo button was not working as expected in the Workflow configuration. | Steps:
| In the Change Management module, undo button is working as expected in the Workflow configuration. |
156996 | The parent and child relationship was not working in the pre-production instance. | Steps:
| Parent and child relationships are working in the pre-production instance. |
157155 | In the Service Request (SR), when a Work Order (WO) was created through the SR, not all fields were displayed correctly in the WO form. Additionally, the auto-linking did not occur for the new WO generated from the SR link. | Steps:
| When linking a Work Order (WO) to a Service Request (SR), all the fields in the Work Order form are displayed as expected. |
157952 | The attached email was not getting parsed from the inbox and the remaining emails were not getting parsed. | Steps: The email with .msg attachments were not getting parsed as the content type was coming as ‘null’ for emails. | The attached emails are getting parsed and .msg files are getting attached as .eml files. |
157753 | Rich Text editor was not working as expected. | Steps:
| Rich Text editor is working as expected. |
154161 | Customer wanted a new feature in the Change Management (CM) module, so that data entered in PLANNED START TIME and PLANNED END TIME should not change and follow the below protocol.
| Steps:
| The PLANNED START TIME and PLANNED END TIME are displaying as desired. |
69387 | While importing user data from Azure AD, records with an empty User Name column value were also being stored in the user table. This was causing issues on specific pages while fetching user details. | Steps:
| Mandatory value checking for User Name has been implemented for Azure AD Import. |