- 17 Jan 2025
- 25 Minutes to read
- Print
- PDF
Release Notes v6.1.0.1 HF10
- Updated on 17 Jan 2025
- 25 Minutes to read
- Print
- PDF
Improvements
Following improvement is introduced in this v6.1.0.1 HF10 release.
Improvement Name | Improvement Description | Benefits |
Configure Appsettings Key for the notifications sent from Scheduler, Business Rule, and Workflow Designer. User Persona: App Designer | Enables you to configure attachment based on the Latest or All attachments present in selected attributes, along with the mentioned refresh time. For more information, refer Attachment. |
|
Fixed Issues
The following section provides details of fixed issues in Apex v6.1.0.1 HF10:
Issue ID | Issue Description | Scenario | Resolution |
---|---|---|---|
163799 | While saving the Admin Form, the system displayed the following error message. “Something went wrong. Please try again later.” | Steps:
| System does not display any error message while saving Admin Form configurations and the configurations get saved successfully. |
163507 | After adding the table as User the other fields such as Tenant were not displaying any values for the same CR. | Steps:
| After adding the table as User the other fields such as Tenant are displaying values the same CR. |
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).” |
| The validation error message verbiage is changed from “Review the validation error on the bottom of the control(s).” to “Specify the mandatory field(s).” |
160642 | In the Change Management module, an error occurred message was displayed while saving the Change Record Template. | Prerequisites:
Steps:
| The Change Record Template is saved successfully without any error message. |
160596 | There was an issue while creating a Change Record (CR) for a particular Change Category. | Prerequisites:
Steps:
| CR is successfully created for the selected Change Category. |
161214 | The error message was not displayed when the Planned Start Time is less than Lead Period. | Steps:
Note The Planned Start Time should be less than the Lead Period (1day). | The error message is displayed when the Planned Start Time is set to less than the Lead Period. |
164348 | In the User Role Mapping, the Next button in the Define Access step, and the Update button in the Publish step did not work after a condition was configured. Note: This issue also occurred while updating existing User Role Mapping records, where the Next button in the Define Access step, and the Update button in the Publish To step were not working. | Steps:
| The Next button in the Define Access step and the Update button in the Publish To step of the User Role Mapping section are working as expected. |
160586 | The Mailbox was not getting connected as the wrong API Endpoints were set in the API Configuration. | Prerequisite: Configure API for Mailbox. Steps:
| Mailbox gets connected after the correct API Endpoints are set in API Configuration. |
160624 | Notifications sent from Business Rule was displaying blank on email, for that contained Grid component of Owner or Analyst column and which was not assigned to any Analyst. | Prerequisites:
Steps:
| Notifications sent from BR is displaying with Analyst names and these contain Grid with Owner / Analyst column. |
161948 | In the Problem Management, the Approver could not view the Root Cause Analysis (RCA) Fishbone Diagram on the RCA tab of the Manage Problem Records Details page. | Prerequisite: Create a Problem Request (PR) and add the RCA details in the RCA tab in the created PR. Steps:
| The Fishbone Diagram for Approver is displayed without any issue. |
161581 | An error occurred when the Approver attempted to open the Relationship tab on the Approve Change Request page. The following error message was displayed: | Prerequisite: The Relationship tab must be configured in Approve Change Request form under Form Designer. Steps:
| The Relationship tab displays relevant data on the Approve Change Request page without any errors. |
161220 | The Left Navigation side panel was missing intermittently post-upgrade. | Steps:
Note: The issue persisted in all the Service Management modules. | The Left Navigation side panel is visible in all the Service Management modules. |
162090 | Error "At least one field should be filled" was displaying when adding a record for a multi-valued group under the Test tab for a Change Record. | Prerequisite: A multi-valued group should be created under the Test tab for a Change Record. Steps:
| Records under the Test tab for a Change Record are getting saved successfully. |
161212 | Common Master values were not getting disabled. Although marked as inactive, those values continued to appear in the Catalog dropdown list. | Prerequisites:
Steps:
| The inactive Common Master values are now disabled and are not displayed on the form. The functionality is working as expected. |
161283 | The Business Rule condition did not function since the Category Priority And Service Window Matrix and multi-select Categories were not available to configure as Dynamic in the Incident module. | Prerequisites:
Steps:
| The Business Rule condition works as expected since the Category Priority And Service Window Matrix and multi-select Categories are available for Dynamic configuration in the Incident module. |
162108 | Under Notification Parser, extra fields were automatically added as blank values under Actions > Update Record > Criteria. | Steps:
| Criteria field displays values correctly without any blank values in Actions > Update Record under Notification Parser. |
161422 | Users were unable to remove the Days entry from the Efforts field as they were not able to save the configuration. | Steps:
| After removing Days entry from the Efforts field, users are able to save the configuration successfully. |
161910 | Information was not updated in User Communication for Change Record through email to ticket functionality. | Steps:
| Information is successfully updated in the User Communication for Change Record through email to ticket functionality. |
161291 | Functionality to create a ticket of a different module from a ticket of another module was not working. | Steps:
| Functionality to create a ticket of different module from a ticket of another module is working as expected. The new record gets linked to the source record and it appears under the Links tab. |
163243 | The page displayed unauthorized access while trying to switch roles if the landing page was configured as a consumer end page in the User Profile. | Prerequisite: The Landing page should be set as a consumer end page in the User Profile. Steps:
| The page displays properly when the roles are switched while the landing page is configured as a consumer end page in the User Profile. |
163871 | The Work Order created from the links tab in the Manage Change Request page was not listed. It displayed the following error message: "An error occurred while processing your request” This error was displayed on both the Manage Change Requests and Manage Work Order pages. | Steps:
| The Work Order created from the Links tab in the Manage Change Request page is displayed successfully without any errors. |
163864 | The Requestor field was editable at the Approve Change Requests page at the Awaiting Approval status. | Steps:
| The Requestor field is not editable after the disabled validations are applied. |
162668 | There was a display bug in the Notification Parser menu. | Steps:
| There are no display bugs in the Notification Parser menu. |
163786 | In the Scheduler, the column mapping did not update the user.country field when the value was empty in the AD Import Azure Call API function. | Steps:
| The default column mapping values are chosen for the AD Import Azure Call API in the Scheduler. |
163762 | In the Change Management module's admin forms such as Impact, the Tenant dropdown was empty and did not show any options. | Prerequisites:
Steps:
| The Tenant dropdown shows all the tenants configured for the admin form. |
163869 | Priority field was not auto populated when Urgency and Impact values are selected on the Manage Change Request page. Change Records were submitted without a Priority value. | Prerequisite: Priority Matrix should be configured. Steps:
| Priority field gets auto populated based on Urgency and Impact values on the Manage Change Requests page. |
163402 | The existing Parser rules were not editable. | Prerequisite: App Designer must be on the Notification Parser list page. Steps:
| The existing Parser rules are editable. |
163762 | The email to ticket functionality while using a single-tenant setup was not working because the form validation rules table contained multiple form control validations. | Prerequisites:
Steps:
| After removing the single tenant validation rules table, the email to ticket functionality is working as expected. |
163867 | In Change Notification Template, while configuring Grid, in the Configure Columns section some of the column Fields were blank. Grid columns were disappearing after saving the configuration. Hence, values were not populated in the email notifications. | Steps:
| In the Notification Template, while configuring Grid, in the Configure Columns section of column Fields are displaying with values. |
164347 | In any transactional pages or list pages, the Show record per page and the options to move to next page were not working. | Steps:
| In any transactional pages or list pages, the Show record per page and the options to move to next page work successfully without any issues. |
164446 | On the Incident, Service Request, and Work Order List pages, the Sort Order and Column Filter did not function correctly. The Column Filter did not filter the data properly, and the Sort Order did not sort the data as expected. | Steps:
| The Sort Order and Column Filter on the list pages are functioning as expected. |
163892 | Business Rules were not working for Incident tickets. | Prerequisites:
Steps:
| Business Rules are processed for Incident tickets. |
164486 | Pagination was not working as expected on all the Admin, Transaction forms and on the Designer list pages. | Steps:
| Pagination works as expected on all the Admin, Transaction forms and Designer list pages. |
164343 | While configuring Business Rule Designer, in the Condition stepper when the below conditions were added, the designer was experiencing issues:
Due to this, the created Business Rule for Auto status update to ECAB Approval was not processing. | Steps:
| While configuring the Business Rule Designer, in the Conditions step, the Change Type Field is displaying Values in the list. The created Business Rule for Auto status update to ECAB Approval is processing as expected. |
164115 | The Analyst Dashboard displayed details of all the tenants in the same dashboard. | Steps:
| The Analyst Dashboard displays the data based on the logged in user workgroup access. |
Known Issues
The following section provides details of known issues and workarounds in Apex v6.1.0.1 HF10:
Issue ID | Issue Description | Scenario | Workaround |
159893 | 50 % SLA breached notification has not triggered for the Response SLA and Workaround SLA between 5th to 23rd October due to Elapsed Time scheduler Job failure. | Steps:
Note Notification is not triggered for 50% SLA breached Incidents. | N/A |
161386 | Filters on the List page is not working as expected on the Service Management application. | Steps:
| N/A |
156119 | Options in the Value field for the Change Category condition are not populating while configuring Workflow for a Change Record. | Steps:
| N/A |
161173 | Deadline SLA is not working in Problem Management Module. | Steps:
Note The SLA is configured based on specific statuses and will follow according to the selected. | N/A |
161247 | On creating a new Incident, the customer names do not appear in the Customer field on the General tab. | Steps:
| N/A |
161162 | The Change Record (CR) can be submitted without attaching the mandatory file in the Upload field. | Steps:
|
N/A |
161220 | In the Analyst Dashboard, the Left Panel does not appear after maximizing the page. | Steps:
| N/A |
159014 | An error message (“Error obtaining a build status”) is displayed while exporting one month of data using the newly created Daily Incident Report. | Steps:
| N/A |
159521 | Fields that are hidden using Validation controls are becoming visible after submitting the Change Request (CR). | Steps:
| N/A |
161210 | In the CMDB module, certain company fields are not populating data appropriately while bulk updating CIs. | Steps:
| 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 |
70616 | The screen keeps loading while approving the CR. | Steps:
| N/A |
161442 | The Application Designer is unable to save the configuration after removing Days from the Efforts field. | Steps:
| N/A |
160518 | After clicking More option, the full message is getting displayed in a single line. | Steps:
| N/A |
70853 | There is a delay in loading the Manage Change Requests list page while selecting the Clear All Filters in the Advance Filter pop-up. | Steps:
| N/A |
161283 | Business Rule in the Incident Management module is not functioning as expected when applied to a dynamic table. | Prerequisites:
Steps:
| N/A |
159748 | The Manage Change Requests list page is taking more time to load after clicking Apply in the Advance Filter pop-up. | Steps:
| N/A |
160541 | The Reopen Reason value is not visible in the Change History on the User Incident Details page. | Steps:
| N/A |
160544 | Apex application is loading slow whenever a ticket is opened. | Steps:
| N/A |
70589 | There was a two-hour delay for the bulk allocation of 10,000 records on the Fixed Asset List page. | Prerequisite: Asset should be displayed in Instore and New status. Steps:
| 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 |
161212 | Common Master values are not being disabled. Despite being marked as inactive, these values continue to appear in the dropdown list of the catalogs. | Steps:
| N/A |
161349 | Cancellation remarks are captured as encrypted values in the Change History of Manage Incidents when it's cancelled from the User Incident (My Incident) form. | Steps:
| N/A |
161412 | Workgroup name does not display properly on Change Request Details page. | Prerequisite: Additional Workgroup Approver custom field must be configured in Form Designer. Steps:
| N/A |
161406 | The Title of Requests (Description) field in Change Management is getting resized. | Steps:
| N/A |