Customer Fixed Issues and Known Issues
Customer Fixed Issues
This section describes the issues reported by the customers and their fixes in the release, Alps SP1.
# | Issue | Resolution |
|---|---|---|
| 54441 | Incorrect time was displayed in the exported CSV file (Reports > Select the module > Click the New Report icon > Under DATA SOURCES tab, select the required report with the date and time fields > Click CONTINUE TO FIELDS > Select the date/time field from the drop-down list > Specify the Format > Click PREVIEW > Click CSV icon to export the report). This issue was occurring while exporting the reports with the date and time fields into CSV format. For example, if the time in the report was displayed as 18:00:00 PM and after exporting the report in the CSV file, the time was displayed as 6:00:00 AM. | Now, the user can select the newly added option yyyy-MM-dd HH:mm under the Format drop-down list to get the correct time in the exported CSV file of the reports. |
Known Issues
This section describes the known issues detected by the SummitAI Dev and QA team in the release, Alps SP1.
Issue |
|---|
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). |
| On the NETWORK DEVICE VIEW page (Operations > User > Views > Network Device View), duplicate devices are displayed when Add For Monitoring is selected while discovering more Network Devices on the DISCOVERY page (Admin > Advanced > Discovery & Monitoring > Discovery > Select the Tenant from the Filters pop-up > Click SUBMIT to view the DISCOVERY page > Click ADD NEW from the ACTIONS panel > Specify all the required fields and select the Add For Monitoring field). |
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). |
| 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). |
(#59826) All the users are getting notification e-mails in the last configured language irrespective of the language configured on the NOTIFICATION TEMPLATE page (Admin> Advanced> Notification> Notification Template> Select a Tenant > Click ADD NEW > Specify all the required fields > Click SUBMIT). |