- Created by Former user , last modified by Mayuresh Balaji Kamble on Apr 19, 2024
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 2 Next »
Customer Fixed Issues and Known Issues
Customer Fixed Issues
This section describes the issues reported by the customers and their fixes in ALPS SP1 HF05. The bug fixes for the bugs found in the following versions are also merged with this release. Please refer to the respective Release Notes for details.
- 5.6 SP2 HF18
- 5.7 SP5 HF08 (#59842, #56320, #62744, #62472, #57594, #59388, #62058)
- 5.7 SP6 HF05
# | Issue | Resolution | ||||||||||||||||||||||||||||||
Few of the Analysts were getting access to the Modules that were not part of their configured License Edition. Example:
The Analysts with Business Edition License were also able to access the Change Management or Problem Management or other modules, which are not part of Business Edition License. Prerequisites: Ensure that that the Business and the Enterprise Licenses are applied in the Application. Bug Reproduction Steps:
| Now, the Analysts can access only those Modules, which are included in the License type. | |||||||||||||||||||||||||||||||
64369 | An Oops error message was getting displayed when a CI record was opened on the CONFIGURATION ITEM LIST page. Bug Reproduction Steps:
| Now, a CI record can be opened from the CONFIGURATION ITEM LIST page without any error. | ||||||||||||||||||||||||||||||
64370 | The Global Search was not displaying any search result while searching for any text value. The Global Search was able to display search results only for integer values. This issue was found after upgrading SummitAI version to ALPS SP1 HF02. Bug Reproduction Steps:
| Now, Global Search is displaying search results while searching for text value. | ||||||||||||||||||||||||||||||
63153 63522 | The Analysts were unable to update the Status of Service Requests to Resolved using Bulk Update. A warning message, "None of the SRs are updated.", was displayed. Bug Reproduction Steps:
| Now, the Analysts can update the Status of Service Requests to Resolved using Bulk Update without any error. | ||||||||||||||||||||||||||||||
63139 | If the user logged into the Application after repetitively logging in and logging out, an error message, “You have logged in from other device.”, or the Duplicate Login pop-up page was displayed. This issue was occurring even after logging off from the Application and closing the browser window. Bug Reproduction Steps:
| Now, no Duplicate Login or error message is displayed when the user tries to log into the Application after repetitive log in/log out actions. Note: The corrections are made for SSO authentication only. | ||||||||||||||||||||||||||||||
56926 | The Data and Graphs were spanning across multiple pages while generating a PDF of the BI Dashboard. This Issue was occurring because of incorrect formatting. Bug Reproduction Steps:
| To resolve BI Dashboard report formatting issue, include the following key in the Web.config file: | ||||||||||||||||||||||||||||||
63134 | The Pending Incident Feedback link on the End User Dashboard page was navigating to the MY INCIDENTS page but none of the Incidents were listed on the page. This link should open up the MY INCIDENTS page displaying the list of Incidents that are pending for Feedback. Bug Reproduction Steps:
| Now, on clicking the Pending Incident Feedback link on the End User Dashboard page, MY INCIDENTS page opens up displaying the list of Incidents pending for Feedback. | ||||||||||||||||||||||||||||||
64987 | The Incident Symptom was picking up the Primary Symptom instead of the Secondary Symptom that was defined while raising the Incident from the End User Dashboard page. Prerequisites:
Bug Reproduction Steps:
| Now, the Incident Symptom is picking up the correct Primary or Secondary symptom that is entered while raising the Incident from the End User Dashboard. | ||||||||||||||||||||||||||||||
63221 | There was a spelling mistake in the e New Value column of the Checklist tab, rue instead of True. This error was found on the Incident SUMMARY pop-up page of the Daily Incident Report. Prerequisites:
Bug Reproduction Steps:
Note: The issue occurs for all statuses of the Incident when the Checklist task is met. | The spelling mistake in the New Value column of the Checklist tab is corrected. | ||||||||||||||||||||||||||||||
63411 | The Category field was blank by default on the OPERATIONAL LEVEL SPECIFICATION page. It was populating, ALL, value only after an Incident Management criterion was added. Bug Reproduction Steps:
| Now, by default ALL is displayed in the Category field on the OPERATIONAL LEVEL SPECIFICATION page for the Incident Management section. Also, a icon is added in the field to revert back to ALL after a specific Category is selected. | ||||||||||||||||||||||||||||||
63434 | No data was displaying in the Location and Manager fields on the USER details page. Also, the user was not able to search Location and Manager while modifying the USER page details. This issue was occurring for both single and multi-domain users. Bug Reproduction Steps:
| Now, the Location and Manager data is displayed on the USER page. Also, the user is able to search Location and Manager while modifying the USER page details. | ||||||||||||||||||||||||||||||
63792 | Some of the users who were not having access to a Catalog were able to raise the SRs for such Catalogs using the New Service Request page Application URL shared by a user who was having access to that particular Catalog. Prerequisites:
Bug Reproduction Steps:
| Now, when a user not having access to a Service Catalog tries to log a Service Request for that Service Catalog using the Application URL shared by another user who is having access to the Service Catalog, a validation message is displayed and is not allowed to raise SRs for the Service Catalog ,"You do not have access to the Service Catalog, (CATALOGNAME)." | ||||||||||||||||||||||||||||||
63821 | The Summary tab on the PENDING SERVICE REQUEST REPORT page was not showing the correct count. This issue was occurring when the Role Template for the user was configured as Customer in the Show Only User's field under the REPORT SCREENS section. Prerequisites:
Bug Reproduction Steps:
| Now, the Summary tab on the PENDING SERVICE REQUEST REPORT page is showing the correct count. | ||||||||||||||||||||||||||||||
64003 | The Analyst details were not getting saved on the ANALYST page when the Analyst details were imported for a Workgroup for the first time. This issue was occurring for Analysts who were not part of any of the Workgroups before. Prerequisites: Adding New User
Importing Analyst
Bug Reproduction Steps:
| Now, the Analyst details are saved on the ANALYST page when the Analyst details are imported for a Workgroup (even for the first time).
| ||||||||||||||||||||||||||||||
64448 | An error message was displayed when an Analyst was trying to open an Incident from the INCIDENT LIST page.. Bug Reproduction Steps:
| Now, the Analysts can open and view Incidents from the INCIDENT LIST page without any error. | ||||||||||||||||||||||||||||||
62926 | The newly added Asset Category fields were not displaying for the older Assets in the Asset Allocation e-mail notification to the End Users if the newly added Category field was empty. Bug Reproduction Step: Add New Asset Category Fields
Add Assets
| Now, all the Asset Category fields are displaying in the Asset Allocation e-mail notifications sent to the End User for both older and new Assets. | ||||||||||||||||||||||||||||||
The Incident IDs that were getting generated while Monitoring for down Servers, Devices, or Links, were not in the continuous Incident ID series. This issue was occurring when the session was timed out before all the Incident IDs were generated for the down Servers, Devices, or Links. Example: While Monitoring the Servers, if 20 Servers were down and only 10 Incidents were created as Incident ID 101, 102, and so on till Incident ID 110, and the session timed out. When the session was restored, all the data was rolled back and none of the Incidents were created. During the next Monitoring, when the next Incident ID was created for a down device, it was starting from Incident ID 111. | Now, Incident IDs that are generated for down Servers, Devices, or Links are not rolled back when session times out. After the session is restored, the Application creates Incident IDs in continuation with the last Incident ID logged. As per the example, all the Incidents are logged for down devices from Incident ID 101 - 120 even if session times out in between while generating the Incident IDs. Also, during the next Monitoring, when the next Incident ID is logged, it starts from Incident ID 121. | |||||||||||||||||||||||||||||||
65343 64758 | An error message, 'Cannot upload the attachment file', and , 'Attachments failed to upload', was displayed when an Incident was raised from the SummitAI Mobile App using SSO login. The Incident was getting created as expected but the attachments was not getting uploaded or downloaded. | Now, the attachments that are attached while raising the Incidents using the SummitAI Mobile App using SSO login can be uploaded and downloaded without any error message. |
Known Issues
This section describes the known issues detected by the SummitAI Dev and QA team in the release, Alps SP1 HF05.
Issue |
The Username, E-mail ID, Emp Id, and values for few of the columns are not displayed in the columns under the DEALLOCATED ASSETS section on the ASSET DETAILS pop-up page when the Checker refers back Assets of Deallocation Transaction type.(#67805) Precondition:
Bug Reproduction Steps:
Check the Username and E-mail ID for the Asset. The Username, Email ID, Emp id and values for few of the columns are not displaying under the DEALLOCATED ASSETS section on the ASSET DETAILS pop-up page |
On the FIXED ASSET INVENTORY page, only added Assets with Maker Checker configuration are displayed when Referred Back is selected in the Checker Status drop-down list on the FILTERS pop-up page. (#65848). Required configuration:
Bug Reproduction Steps:
|
On the ADMIN DETAILS page (Admin > Advanced > Password Management > Administrator > Click ADD NEW on the ACTIONS panel > Specify all the details > Click SUBMIT > Select the Domain Name on the LIST page), the Password field is not displaying the GUID or Encrypted ID of the password and the field is empty. This issue is found when the user is logging into the SummitAI application using Microsoft Internet Explorer browser. |
On the Incident Management FORM BUILDER page (Admin > FORM BUILDER > Select a Tenant > Select Module as Incident Management > Click Add on Actions panel> Select Display At as Additional Information or General Area or TFS Area > Click Next), when a user configures single Parent and multiple Child using Common Master, the collective values of both Child 1 and Child 2 are displayed in Child 1 and Child 2 drop-down lists. |
On the Service Request Management FORM BUILDER page (Admin > FORM BUILDER > Select a Tenant > Select Module as Service Request > Click Add on Actions panel> Select Display At as Additional Information or General Area or TFS Area > Click Next), when a user configures single Parent and Multiple Child using Common Master, the collective values of both Child 1 and Child 2 are displayed in Child 1 and Child 2 drop-down lists. |
Overlapping of content is observed on the Pagination bar of all the pages having lot of records (typically in the range of 5 digits). |
The configured Bulletin Board (Admin > Advanced > Notifications > Bulletin Board > Select the Tenant > Click ADD NEW to configure the Bulletin details > Click SUBMIT) is displayed on the END USER DASHBOARD page even if the user does not have access to the selected Tenant and Domain. |
Broken image of the logo is displayed in the application when the logo image is deleted from the APPLICATION SETTINGS page (Admin > Basic > Infrastructure > Application Settings). Workaround: The users need to re-login to the SummitAI application after deleting the logo. |
On the AUTO-RESOLUTION SERVICE REQUEST CONFIGURATION and AUTO-RESOLUTION INCIDENT CONFIGURATION page (Admin > Basic > Infrastructure > Tenant > Select Domain > Select Tenant which is configured with Service Request/ Incident Management module > Click CONFIGURE DETAILS on the ACTIONS panel > Under the For End Users tab, select a reason form the Enable Reminder to Callers for Pending Reasons drop-down list > Enable Auto-Resolve Service Requests/ Auto-Resolve Incidents check box > Click Set Fields for Auto-Resolving Service Requests/ Set Fields for Auto-Resolving Incidents link), the users can set the auto-resolution criteria by specifying only white space (not numbers and alphabets) in the Response SLA Reason, Resolution SLA Reason, and Solution fields. |
The following issues are observed in BI Custom Reports:
|
The Change Record is not created when the CR Requester and Customer Approver are same. This issue occurs even though Do Not allow Customer Approval of CR check box is selected on the Change Management TENANT configuration page. This issue occurs only for the first time when the Tenant is configured. Workaround: The Administrator needs to unselect and again select the Do Not allow Customer Approval of CR on the Change Management TENANT configuration page (Admin > Basic > Infrastructure > Tenant > Select the respective Tenant for which this issue is occurring > Click CONFIGURE DETAILS on the ACTIONS panel > Enable Do Not allow Customer Approval of CR check box and click SUBMIT > Clear Do Not allow Customer Approval of CR check box and then click SUBMIT, again). |
The new SLA Value of an Incident is not displayed on the CHANGE HISTORY pop-up page (Incident > User > Manage Incidents > Incident List > Select the required Incident ID from the list > Click CHANGE HISTORY on the ACTIONS to view the change history of the selected Incident) when an incident is moved from New status to In-Progress using Notification Services. |
The Pending Reason of an incident is still displayed on the CHANGE HISTORY pop-up page (Incident > User > Manage Incidents > Incident List > Select the required Incident ID from the list > Click CHANGE HISTORY on the ACTIONS to view the change history of the selected Incident), when an Orchestration Script fails and the respective Incident is moved back from Pending to In-Progress. |
The notification e-mails related to escalation and jobs are triggered only in English language irrespective of the configured language on the NOTIFICATION TEMPLATE page for all the modules (Admin> Advanced> Notification> Notification Template> Select a Tenant > Click ADD NEW > Specify all the required fields > Click SUBMIT). |
- No labels