- 17 Oct 2024
- 8 Minutes to read
- Print
- PDF
Release Notes v6.1.0.1 HF07
- Updated on 17 Oct 2024
- 8 Minutes to read
- Print
- PDF
Improvements
Following improvement is introduced in this v6.1.0.1 HF07 release.
Improvement Name | Improvement Description | Benefits |
Configure Attachment Properties in Global Settings User Persona: Super Admin | Add new extensions in the Global Settings on the Platform with CR Approval. For more information, refer to Attachment Properties. |
|
Configure File Extension Properties User Persona: Application Designer | Configure File extension properties on File Upload control that allow you to select required File Type extensions on the Forms. For more information, refer to File Upload -Form Designer. |
|
Designer Execution Sequence User Persona: Application Designer | Configure the executing order of Business Rule, Workflow and SLA while publishing a form. For more information, refer to Publish document in Form Designer. | Flexibility to publish a form with required execution order for Business Rule, Workflow and SLA. |
Fixed Issues
The following section provides details of fixed issues in Apex v6.1.0.1 HF07:
Issue ID | Issue Description | Scenario | Resolution |
---|---|---|---|
157172 | When approver referred an incident back, the Incident status did not change to Refer Back as expected. | Prerequisites:
Steps:
| When an Approver, Refers Back an Incident, the status of the Incident is successfully changed to Refer Back. |
158381 | Incorrect records were displayed on the list page of Manage Change Requests for a specified date range when selected in the Advanced Filter. Note: The issue is same for the Lis pages of Manage Incidents, Service Requests, Knowledge Records, and Problem Records. | Steps:
| Correct records are displayed on the list page of Manage Change Request for a specified date range when selected in the Advanced Filter. |
157856 | Even though Include In Template button was disabled, the downloaded CMDB template from Infrastructure as a CI still retrieved data from deleted fields. | Prerequisites:
Steps:
| The downloaded CMDB template from Infrastructure as a CI contains only the configured fields. |
158641 | Emails were not processed to tickets due to an in-correct email address. | Steps:
| The invalid Email IDs entered in CC/TO/BCC fields are skipped and the ticket gets created successfully after the resolution. |
157400 | The filter got reset when navigated to next page while searching for a user under User List page in Platform Studio. | Steps:
| The filter does not get reset when navigated to next page while searching for a user under User List page in Platform Studio. |
158752 | The Response SLA was considered for weekends, and the wrong deadline was displayed even though weekends were not selected in the Service Window configuration. | Steps:
| The Response SLA consideration is done accurately for the days defined in Service Window. |
157421 | There was a mismatch in the Workaround SLA value in the Incident detail page and Incident list page. | Steps:
| The Workaround SLA value in the Incident detail page and Incident list page is same. |
158196 | Some images in Incident were not displayed properly. If there were two images in the email body, one displayed correctly while the other did not. | Steps:
| Multiple Images are displayed properly in the email body. |
156831 | The breadcrumb menu, which displays the navigation trail of the previous sections, was not displayed. | Steps:
| The breadcrumb menu displays the navigation trail of the previous sections. |
157501 | In the change management workflow, for role-based approval, admin was unable to select the secondary owner for the workgroup. | Steps:
| In the change management workflow for role-based approval, the admin can select the secondary owner for the workgroup. |
154734 | .eml and .msg attachments were not attached to the tickets created through email to ticket functionality. | Steps:
| .eml and .msg attachments are attached to the tickets created through email to ticket functionality. |
157671 | The minimum height configuration was not working as expected for Long Text control in the Form Designer. | Steps:
| The minimum height configuration is working as expected for Long Text control in the Form Designer. |
155215 | Mandatory validation messages were not appearing for Rich Text Editor field, whenever the validation condition was met. | Steps:
| Mandatory validation messages are appearing for Rich Text Editor field, whenever the validation condition is met. |
158262 | The Data Type for Effort field was displaying older values. | Steps:
| The Data Type for Effort field is displaying values as expected. |
157392 | The Impact, Urgency, Priority and Risk values were being displayed in alphabetical order instead of being displayed according to the sort order specified during their creation. | Prerequisite: 1. Navigate to Admin form (Which contains Sort Order) configuration page by putting form under Maintenance > Select Render as Fields as Sort Order. Steps: 1. Log in to the Apex application. 2. Navigate to Problem > Manage Problem Records > Click Configurations. 3. Select a form which contains sort order. For e.g., Impact, Urgency, Priority and Risk. 4. Click New > Enter all the mandatory details. 5. Enter the Sort Order (1) > select the Active checkbox > click Save. 6. Again, click New > Enter all the mandatory details. 7. Enter different Sort Order (9) > Select the Active checkbox > click Save.
| The Impact, Urgency, Priority and Risk values are being displayed according to the sort order specified during creation. |
156565 | In the Change Management module, Role Based Approval using Dot Walking was not working. A multi-select dropdown had been configured to list various workgroups. Based on the selected workgroup(s), the primary owners should automatically be assigned as approvers in the workflow. | Steps: 1. Navigate to Design Studio > Select the Module > Workflow Designer. 2. Click the Workflow ID which is created in Workflow Designer page. 3. Navigate to Design Workflow step. 4. Double click on User Approval component.
| Role Based Approval using Dot Walking is working as desired. |
Known Issues
The following section provides details of known issues and workarounds in Apex v6.1.0.1 HF07:
Issue ID | Issue Description | Scenario | Workaround |
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 are visible. | Steps:
| N/A |
157794 | The downloaded CMDB template from Infrastructure as a CI does not successfully import unique values. | Steps:
| N/A |
158385 | Service Request fields display blank data during the update of ticket and do not update further until the form is refreshed. | Steps:
| N/A |
156854 | The column width adjustment made in the Incident list page by dragging the separator does not persist after navigating to an Incident detail page and reverting to the list page. | Steps:
| N/A |
158316 | Change Category is not reflected in Set Trigger & Conditions under Workflow. | Steps:
| N/A |
157411 | The Scheduler configured to notify escalation to the record attribute group is not triggering the notification. | Prerequisites:
Steps:
| N/A |
158184 | Users are unable to upload values for child fields in the import template. | Steps:
| N/A |
158186 | The Long Text field is not getting displayed in expandable and scrollable format. | Prerequisite: Incident Status must be Closed. Steps:
| N/A |
158615 | Category field was unavailable to filter for both Incident Management (IM) and Service Request (SR) list page. | Steps: 1. Log in to the Apex application. 2. Navigate to Incident > My Incidents. My Incidents list page is displayed. 3. Click icon to add Filters and search for Category in the search bar.
| N/A |