Customer Fixed Issues and Known Issues Elbrus SP1 HF03
| Previous Versions: << Sierra << Sierra HF01 << Sierra SP1 << Sierra SP1 HF01 << Sierra SP1 HF02 << Sierra SP1 HF03 << Denali << Denali HF01 << Denali HF02 << Denali HF03 << Denali SP1 << Denali SP1 HF01 << Tahoe << Tahoe SP1 << Tahoe SP3 HF01 (V1) << Elbrus << Elbrus SP1 << Elbrus SP1 HF01<< Elbrus SP1 HF02
On this page: Customer Fixed Issues | Known Issues
Merged Releases
The following Hotfix versions are merged with this release:
Customer Fixed Issues
This section describes the issues reported by the customers and their fixes in Elbrus SP1 HF03.
Asset Management
Issue Number | Issue Description | Scenario | Resolution |
---|---|---|---|
137291 | Field Order Configuration was not working properly for Asset Management module.
| Steps:
| Field Order Configuration works successfully for Asset Inventory without any issues after the resolution. |
Incident Management
Issue Number | Issue Description | Scenario | Resolution |
---|---|---|---|
137916 | Inactive role templates were visible in AD Import Configuration page. | Steps:
| Inactive role templates are not visible in the AD Import configuration page after the resolution. |
Known Issues
This section describes the known issues detected by the Summit Dev and QA team in the release, Elbrus SP1 HF03 Release.
Issue ID | Issue Description | Scenario | Workaround |
124911 | Cost is displayed incorrectly as CPI calculation is not working properly. | Pre-Requisites:
Steps:
| Not applicable |
124863 | On the Copy Service request tab, when Different Caller is selected, unable to enter the username or other details on the Select User pop-up. | Prerequisites:
Steps:
| Type in the Username in the Different Caller option instead of searching the username. |
124867 | In the copy service request, when an SR is created for a catalog and the same catalog is modified by adding new attributes such as a multivalued dropdown (or any other attributes), Scenario 1: The record added for the new multivalued dropdown displays for the existing record. Scenario 2: Oops an error occurred error message is displayed when clicked on the pagination grid and the entire grid is not visible. | Prerequisites:
Steps:
| NA |
110901 | For Additional Information tab of Rule Template page, unable to attach the files based on the configuration done for the Attachment Limit (Single or Multiple) field on Form Builder page. | Prerequisites:
| N/A |
100922 | An error ‘Opps! An error occurred’ or a Saved Successful message was displayed for all the modules, if the mandatory configuration fields were saved with a space (empty) value. | Scenario – I 1. Navigate to Incident > SLA Configurations > Urgency. 2. Select a Tenant. 3. Click Add New from left panel. 4. Press Space Key in Urgency Name field and click SUBMIT Scenario – II 1. Navigate to Problem Management > SLA Violation Reason. 2. Select a Tenant. 3. Click Add New from left panel. 4. Select the Violation Type from the list. 5. Press Space Key in SLA Violation Reason field and click SUBMIT. | N/A |
105119 | After submission, the text is getting converted to code for Question and Answer fields. | Prerequisites: 1. Navigate to Knowledge > User > New Knowledge Record. The New Knowledge Record details page is displayed. Specify the mandatory fields. Make sure for Question field use keyboard Enter key. Click Submit. 2. Navigate to Knowledge > User > Knowledge Record List. The Knowledge Record List page is displayed. Open any KB article with Status as Published. The Knowledge Record details page is displayed. Click COPY KNOWLEDGE RECORD link under Action panel. Check for the Answer field. | N/A |
100352 | When a Change Record (CR) is created with ‘special characters’ in status, it does not display any data in Change Record list page. | Prerequisites: 1. Create a 'status' having special characters such as (*satus_test*). 2. Create the CR. Steps: 1. Log in as approver. 2. Navigate to Change > Change record list. 3. Click on the Filters icon. 4. Select the 'Tenant' field as ALL. 5. Select the previously created 'status'. 6. Click Apply. 7. Verify the results, after applying the status filter with special characters. | N/A |
100760 | The ‘Category’ filters on the Change Record (CR) list page do not display any data results when you select ALL Tenant and Category. | Steps: 1. Navigate to Change > User > Change Record list. 2. Select the 'Tenant' field as ALL. 3. Select the field as Category. 4. Click Apply. 5. Check the results displayed on the Change Record list page. | The Category filter works fine, when you select individual Tenant and Category. |
100781 | When a ‘User Contact Number’ is used to filter records on the list page of IM/SR/PM, it does not fetch any data records. | Below is just an example from Incident Management list page. It also applies to SR and PM list pages too where User Contact Number is used. as filter: Steps: Incident Management (IM) 1. Navigate to Incident > Manage Incident > Incident List. The Incident List page is displayed with list of incidents. 2. From Filter options, select User Attributes 3. Click Apply. 4. Verify the results, after applying the User Contact Number filter. | N/A |
100796 | The ‘Time Selection’ option is not displayed to an Analyst on the SR list page, when Equals (=) operator is selected for Time Filter. | Steps: 1. Log in as an Analyst. 2. Navigate to Request > Service Request List. 3. Select the Time related Filter and choose Equals (=) operator. 4. Click Calendar icon. 5. Check if you are getting the Time Selection option or not in Calendar popup. | N/A |
100798 | The filter option ‘<=’ operator for Log Time Filter used by an Analyst on the SR list page, does not yield proper filter results. | Steps: 1. Log in as an Analyst. 2. Navigate to Request > Service Request List. 3. Select the Log Time filter and choose operator (<=). 4. Click Calendar icon. 5. Select date and time for an already existing SR. 6. Click Apply. 7. Check if you are getting the filter results. | N/A |
100808 | The View names created by an Analyst for IM/SR/PM/CM modules with long Japanese names are getting out of the container, unlike the English long names. | Steps: 1. Log in to the Application as an Analyst. 2. Navigate to Request > Service Request List and create a view with long Japanese name and apply view. 3. Navigate to Incident > Incident List and create a view with long Japanese name and apply view. 4. Navigate to Problem > 5. Navigate to Change > Change Record List and create a view with long Japanese name and apply view. 6. Verify the view name in Japanese language text which goes out of the container. | N/A |
100813 | The Assigned To drop-down does not display the User list. | Prerequisite: The key <add key="App:MultiLanguageEncodingEnabled" value="true" /> is set to True in webconfig file. Steps: 1. Navigate to Incident > User > Manage Incidents > Incident List. In the Incident List Click Incident ID hyperlink. The Incident ID details page is displayed. | N/A |
111673 | Attachment details deleted during editing are not captured in the Change History. The same issue persists in Problem, RCA, and Diagnostic tabs.
| Steps:
| NA |
108668 | After adding the Consumable Asset, a “No Data” message is displayed however, it is visible in the SEARCH ASSET popup.
| Prerequisites:
Steps:
| Asset Attributes can be made mandatory in the action panel of Form Builder page by selecting Add Validation Rules for saved controls. |
110654 | The uploaded file name is not displayed on the Preview and Update Category page when the user clicks the Update Category icon. | Prerequisites:
Steps:
| NA |
108230 | While creating a Report, if the report name was greater than 40 characters system displayed an error. | Steps:
| Reports are getting created successfully even when the report name is greater than 40 characters. |
111814 | Due to performance issue in Database (DB), the Incident remarks are not updating in the event history. | Prerequisite:
Bug Reproduction Steps:
| NA |
127523 | In the Summit Mobile App on iOS devices, when trying to delete the OTP entry using the backspace on the virtual keyboard, the previous entries of the OTP were not getting deleted. For Example: When a user entered three digits from the six-digit OTP and was on the fourth placeholder of the OTP, tried to delete the previous digits by clicking the backspace button. However, the app did not allow the entry to be deleted. Note This issue is also applicable for mPIN. | Prerequisite: Log in to the iOS device.
| Place the cursor on the last entered entry in the OTP placeholder and click the backspace button to delete the entries. |
Confluence Cloud Migration Alert: Please refer to known issues you may encounter in Confluence Cloud: https://eitdocs.atlassian.net/wiki/x/wDGwAQ