Customer Fixed Issues and Known Issues Elbrus SP2
| 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
On this page: Customer Fixed Issues | Known Issues
Merged Releases
- The following Hot Fix Releases of are merged with Elbrus SP2 Release.
Customer Fixed Issues
This section describes the issues reported by the customers and their fixes in Elbrus SP2 Release.
Agentless Discovery
Issue ID | Issue Description | Scenario | Resolution |
---|---|---|---|
132626 | Agentless Discovery was not working as email ID was not present for the user. | Steps:
Note: The user initiating the Discovery job must provide an active Email ID to receive notifications. | Agentless Discovery works appropriately after the resolution. |
Platform
Issue ID | Issue Description | Scenario | Resolution |
---|---|---|---|
48647 | Under Asset Management, unique and mandatory field values should be able to add/update the asset by standard API.
| Steps:
Add Asset *Unique Key Violation: Request: { "ServiceName": "AM_AddAsset_Details", "objCommonParameters": { "_ProxyDetails": { "ProxyID": 0, "ReturnType": "JSON", "APIKey": "6CE2tl6ochPHQbVVVHlM1XJlcqjOm+NB/M5KNLFpopo=", "AuthType": "APIKEY" }, "oAM_Asset_MasterParam": { "_Instance": "Info", "_Category_ID": "desktop1", "_Stores": "Anil\\South India\\Karnataka\\Bengaluru\\Summit IT store" }, "oAM_Asset_DetailsParam_items": { "items": [ { "_Attribute_Name": "Serial no", "_Attribute_Value": "PF3326P6" }, { "_Attribute_Name": "Unique ID", "_Attribute_Value": "0002" }, { "_Attribute_Name": "RAM SIZE", "_Attribute_Value": "10GB" }, { "_Attribute_Name": "Version", "_Attribute_Value": "V1" } ], "hasMore": true } } } Response: { "Errors": "UNIQUEKEYVIOLATION : Serial no : PF3326P6", "Message": "", "Output": "", "TokenID": "302882D92D3CA3ADB782A59F82969A93188FD8F B447962B277CFAF044C31F2488C1899C1AAFF48A64B3A5366BD23C9 ED7828BFBF632F9D2C6027276A0D9CCA3B53762614C82085168C931 26CF5AD09B9F6DF384F773CCE692FA902F08AE78477EC721A5C91BE 6002185B66FDCAFC07D2CF448B957CE6ED829D16488D23BEB8DE66C E806286D29509696C84C7BE552490", "OrgID": 0, "OutputObject": null, "OutputID": 0, "Input": null } *Invalid Attribute Request: { "ServiceName": "AM_AddAsset_Details", "objCommonParameters": { "_ProxyDetails": { "ProxyID": 0, "ReturnType": "JSON", "APIKey": "6CE2tl6ochPHQbVVVHlM1XJlcqjOm+NB/M5KNLFpopo=", "AuthType": "APIKEY" }, "oAM_Asset_MasterParam": { "_Instance": "Info", "_Category_ID": "desktop1", "_Stores": "Anil\\South India\\Karnataka\\Bengaluru\\Summit IT store" }, "oAM_Asset_DetailsParam_items": { "items": [ { "_Attribute_Name": "Serial no12345", "_Attribute_Value": "PF3326P6" }, { "_Attribute_Name": "Unique ID", "_Attribute_Value": "0002" }, { "_Attribute_Name": "RAM SIZE213", "_Attribute_Value": "10GB" } ], "hasMore": true } } } Response: { "Errors": "Error saving asset details: Invalid Attribute Names : 'Serial no12345','RAM SIZE213'", "Message": "", "Output": "", "TokenID": "C58D03EBE8EF81DBD19B316BEF7D92E161DFF 294CD54526F77745B9B1E57CA4EFC0D4B8F9FE5B7490ADD6F0D03 2DBD6950B2F39970A4DDCAD5183BA02D660BB108B9FE604DAE735 999512FA75F38291A2B09124B633EB567AA40544DDDCEE3D9D74A 5FB19F434C63DDA37D29C8FCDEFF6EC30EF6F5DE325E3A5D5620D 3B32B8EACC0E19E47D1C181CEC169ECFBE82DB1", "OrgID": 0, "OutputObject": null, "OutputID": 0, "Input": null } *Mandatory Field checks Request: { "ServiceName": "AM_AddAsset_Details", "objCommonParameters": { "_ProxyDetails": { "ProxyID": 0, "ReturnType": "JSON", "APIKey": "6CE2tl6ochPHQbVVVHlM1XJlcqjOm+NB/M5KNLFpopo=", "AuthType": "APIKEY" }, "oAM_Asset_MasterParam": { "_Instance": "Info", "_Category_ID": "desktop1", "_Stores": "Anil\\South India\\Karnataka\\Bengaluru\\Summit IT store" }, "oAM_Asset_DetailsParam_items": { "items": [ { "_Attribute_Name": "Serial no", "_Attribute_Value": "PF3326P6" } ], "hasMore": true } } } Response: { "Errors": "Error saving asset details: Please provide value for mandatory Attribute : 'RAM SIZE','Unique ID'", "Message": "", "Output": "", "TokenID": "058389FAFBCEBE14B9C27A0C98311A3B0 D7BEF541241D7F866A6ADCB8A245C03B32F092AC4521EDD83 B24D6E02D91E360660B78CE58C47347CC9ED129D7DF867261 DE5AD402D818AF6A5E96F9E4D7D271D3D4E2C89135183AFF6 F6F5E61919046FD877FFDB7A08E33CC7602FCC76D928074EB 39714D6F09D479434BE1D1C62848E806320061C3993B7B3DB48CFC42D80", "OrgID": 0, "OutputObject": null, "OutputID": 0, "Input": null } Update Asset *Unique Key Violation: Request: { "ServiceName": "AM_UpdateAsset_Details", "objCommonParameters": { "_ProxyDetails": { "ProxyID": 0, "ReturnType": "JSON", "APIKey": "6CE2tl6ochPHQbVVVHlM1XJlcqjOm+NB/M5KNLFpopo=", "AuthType": "APIKEY" }, "oAM_Asset_MasterParam": { "_Instance": "Info", "_Category_ID": "desktop1", "_Asset_ID": "6406" }, "oAM_Asset_DetailsParam_items": { "items": [ { "_Attribute_Name": "Serial no", "_Attribute_Value": "PF3326P1" }, { "_Attribute_Name": "RAM SIZE", "_Attribute_Value": "10GB" } ], "hasMore": true }, "oAM_Asset_Allocation": { "_ReAllocate": "false" } } } Response: { "Errors": "UNIQUEKEYVIOLATION : Serial no : PF3326P1", "Message": "", "Output": "", "TokenID": "C65FB8E4463A359ECE1E919C875698FC9C0DB1A6E0EC045FABC4E387B468 2D39718D2B991598EAE47FF91F92F972A435FFE3ED95BB351E612210767EF1100D8F87773098 631E795281A37BDCD91389339CECF87A8109C12FDB824B6F3C3A3BB3011CFC8D9ED099BF14B8 614C4DB70BD2A18D515C26A25712FCFDA58754912B3C3532753459F612A14A9D01A4ABF79C9B", "OrgID": 0, "OutputObject": null, "OutputID": 0, "Input": null } *Invalid Attribute Request: { "ServiceName": "AM_UpdateAsset_Details", "objCommonParameters": { "_ProxyDetails": { "ProxyID": 0, "ReturnType": "JSON", "APIKey": "6CE2tl6ochPHQbVVVHlM1XJlcqjOm+NB/M5KNLFpopo=", "AuthType": "APIKEY" }, "oAM_Asset_MasterParam": { "_Instance": "Info", "_Category_ID": "desktop1", "_Asset_ID": "6406" }, "oAM_Asset_DetailsParam_items": { "items": [ { "_Attribute_Name": "Serial no12345", "_Attribute_Value": "PF3326P1" }, { "_Attribute_Name": "RAM SIZE123", "_Attribute_Value": "10GB" } ], "hasMore": true }, "oAM_Asset_Allocation": { "_ReAllocate": "false" } } } Response: { "Errors": "Error Updating asset details: Invalid Attribute Names : 'Serial no12345','RAM SIZE123'", "Message": "", "Output": "", "TokenID": "5C9C01BD28BC3C47344D72EA0ECAD88BBB1470D744AB042BA601A 2649BDEBD2FF037A29FAD94AC5D43FAD89DF617573079826B35DE7E19464C6ECD5712 D31F897305579B1DB1267FC231C2F130B5078B3F181356226A4BBA57A6E832F712A2C 8F44B2F44388E7B0AC3796B17EFDF67449635140ACFE242CE45F26B5B486E5AB98AA4C BD05199EF55D355A78CF5B3C13A", "OrgID": 0, "OutputObject": null, "OutputID": 0, "Input": null } | The Asset is added and updated successfully as per the API. |
Known Issues
This section describes the known issues detected by the Summit Dev and QA team in the release, Elbrus SP2 Release.
Issue ID | Issue Description | Scenario | Workaround |
133775 | Unable to click Classification and Category field drop-down list values, as the page is getting expanded. | Prerequisites:
| NA |
133347 | The Business Rule was not getting saved without configuring Update fields. | Steps:
| NA |
133344 | Getting oops error for specific business rules. | Prerequisite:
Steps:
| NA |
111719 | Audit logs are not getting tracked after ending the session. | Prerequisites:
Steps:
| NA |
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 |
133780 | The selected Catalog Category is not displaying under Subject Header in the Service Request Details Page. | Pre-Condition:
Steps:
| NA |
133693 | Unable to Navigate to the Next Page after clicking Next while creating the New Service Request. | Pre-Condition:
Steps:
| NA |
132272 | The caller field does not populate search results while creating a new incident for user. | Steps:
| NA |
133384 | User was getting redirected to the BUSINESS RULE List Page post clicking on the SUBMIT button in the BUSINESS RULE configuration page. | Steps:
| NA |
Confluence Cloud Migration Alert: Please refer to known issues you may encounter in Confluence Cloud: https://eitdocs.atlassian.net/wiki/x/wDGwAQ