#

Issue

Resolution

62222

False alerts were getting triggered for the Availability Parameters configured using Script-based monitoring. This issue was occurring if the Output Status value was text instead of 0 or 1 or Up or Down. Due to the unknown text value as output, false alerts were triggered.

Bug Reproduction Steps:

1. Log in to the Application.
2. Click Operations.
3. Click Server View under Views.
4. On the SERVER VIEW page, the FILTERS pop-up page is displayed. Select the Tenant and other required filter options to view the Servers.
5. Click SUBMIT.
6. Click the Host Name to view the details.
7. Under the SCRIPTS tab, the Availability Parameter status was not displaying 0/1 or Up/Down. Instead, it was displaying a text value.

Now, no false alerts are triggered for the Availability Parameter configured using Script-based monitoring.

62224

Monitoring failure was happening occasionally for all the Operating System parameters (Status, CPU/MEM, HDD, Swap / Buffer Memory, etc.) that were configured with Script-based monitoring.  This issue was occurring when the same job was running in parallel for both the Standard Parameters and Script-based Parameters.

Now, all the Operating System parameters are getting monitored without any failure.

63908

The Swap Memory data was not displaying even after the deployment of DLLs with the modified command and the key to ignore the Buffer Memory for AIX.

Bug Reproduction Steps:

1. Log in to the Application.
2. Click Operations.
3. Click Server View under Views.
4. On the SERVER VIEW page, the FILTERS pop-up page is displayed. Select the Tenant and other required filter options to view the Servers.
5. Click SUBMIT.
6. Click the Host Name to view the details.
7. Under the BUFFER&SWAP tab, the SWAP MEMORY UTILIZATION data was not displayed.

Now, under the BUFFER&SWAP tab, the SWAP MEMORY UTILIZATION data is displaying correctly.

63557

The Utilization value graph was not displaying for the Parameters that were configured with Script-based monitoring. The last monitored value of the Parameter was displaying as NA.

Bug Reproduction Steps:

1. Log in to the Application.
2. Click Operations.
3. Click Server View under Views.
4. On the SERVER VIEW page, the FILTERS pop-up page is displayed. Select the Tenant and other required filter options to view the Servers.
5. Click SUBMIT.
6. Click the Host Name to view the details.
7. Under the SCRIPTS tab, the Utilization value graph is not displaying any data.

Now, the Utilization value graph is displaying proper values for the Script-based monitoring Parameters.

62792

On the SEARCH Report page, the Incident Symptoms were  getting displayed under the Description column. This issue was occurring only in the SEARCH Report of the Incident Management module.

Bug Reproduction Steps:

1. Log into the Application and click on the Reports icon.
2. Select the Incident Management module.
3. In the Reports drop-down list, select Search.
4. Click on Filters and fill in the required details.
5. Click SUBMIT.
6. The Incident Symptoms are  displayed under the Description column.

Now, the Incident symptoms are displayed under the Symptom column in the SEARCH report for the Incident Management module.

60863

On the NEW INCIDENT page of the SummitAI Mobile App, the Categories which are disabled for End Users were also getting displayed in the Category field. 

Required Configuration:

1. Log into the Application (SummitAI Web application).
2. Select Incident > Configuration > Category.
3. On the CATEGORY page, select a Tenant and disable the Category for the End User.
4. Select Incident > Configuration > Log Incident Page.
5. On the LOG INCIDENT PAGE, configure the Category field for the same Tenant.
   
   

Bug Reproduction Steps:

1. Log into the SummitAI Mobile App.
2. Click New Incident.
3. Select the Tenant for which the Category field is configured.
4. Click the Category field. The disabled Categories are also displayed.

Now, on the NEW INCIDENT page of the SummitAI Mobile App, the Categories, which are disabled for the End Users do not display in the Category field.

62119

The Manager field was not getting populated under the GENERAL tab of the USER DETAILS page. This issue was occurring when the Import Using Excel option was used to import User details into the Application.

Bug Reproduction Steps:

1. Log into the Application.
2. Select Admin > Basic > Users > Import > Excel Import.
3. On the EXCEL IMPORT page, upload the Excel under the GENERAL tab, specify the other details. Click SUBMIT.
4. Select Admin> Basic > Users > User List.
5. On the FILTERS pop-up page, specify the details. Click SUBMIT.
6. On the USER LIST page, open the same User.
7. On the USER DETAILS page, check the Manager field under the GENERAL tab. The Manger filed is not populated.

Now, the Manager field is getting populated under the GENERAL tab of the USER DETAILS page when User details are imported using an Excel sheet.

62668

While exporting the newly discovered Assets using the Export All option, the Operating System names were missing. This issue was occurring only for the Export All option  but was working fine using the Export to Excel option.

Bug Reproduction Steps:

1. Log into the Application and click on Asset.
2. Select User > Manage Assets > Variance > New Discovery.
3. Click on Filters and fill in required details in filter pop-up page.
4. Click SUBMIT.
5. Select EXPORT ALL option under the ACTIONS panel.
6. Compare the Columns present in the NEW DISCOVERY page and the Columns in the Report.

Now, while exporting the newly-added Assets using the Export All option, all the values including the Operating System names are getting displayed properly.

62445

Locations were not getting displayed under the Location field when searched on the NEW INCIDENT page or NEW INCIDENT FOR USER page. This issue was occurring after the SummitAI application was upgraded to ALPS SP1 HF02.

Prerequisite:

1. Log into the Application.
2. Select Incident > Configuration > Incident Masters > Log Incident Page.
3. On the LOG INCIDENT PAGE, select a Tenant and enable the Location field under the CONFIGURE FIELDS section.

Bug Reproduction Steps:

1. Log into the Application.
2. Select Incident > User > New Incident.
3. On the NEW INCIDENT page, select the same Tenant and type in a Location. No results are displayed.
4. Select Incident > User > Manage Incidents > New Incident for User.
5. On the NEW INCIDENT FOR USER page, select the same Tenant and type in a Location. No results are displayed.

Now, Location values are getting displayed under the Location field on the NEW INCIDENT page or NEW INCIDENT FOR USER page.

60755

The Response and Resolution deadlines were getting incorrectly violated for few Incidents. This issue was occurring when the configured Holidays were considered as working days while calculating the SLA.

Prerequisites:

1. Log into the Application.
2. Select Admin > Advanced > Productivity > Holiday.
3. On the HOLIDAY page, select the current date as Holiday.
4. Select Incident > Configuration > SLA > Configurations > SLA Service Window.
5. On the SERVICE WINDOW page, select a Tenant. Click ADD NEW on the ACTIONS panel.
6. Configure the SLA under the DETAILS section and select the Use Analyst's Work Location check box. Click SUBMIT.

Bug Reproduction Steps:

1. Log into the Application.
2. Select Incident > User > New Incident
   1. or Incident > Manage Incidents > New Incident for User.
3. Select the same Tenant as selected in the above steps, specify the Priority and other details. Click SUBMIT.
4. Select Incident > Manage Incidents > Incident List.
5. On the FILTERS pop-up page, specify the details. Click SUBMIT.
6. On the INCIDENT LIST page, select the same Incident and click the Assigned to Me icon.
7. Under the GENERAL tab, the Response and Resolution SLA is displayed as Yes.

Now, the Incident Response and Resolution SLAs are calculated correctly excluding the Holidays.

62813

The Reconciliation button on the MY ASSETS LIST page was not working. This issue was occurring when the Tile View option was selected to display the Assets on the MY ASSET LIST page.

Prerequisite:

1. Log into the Application.
2. Select Admin > Basic > Infrastructure > Custom Scheduler.
3. On the CUSTOM SCHEDULER page, click ADD NEW on the ACTIONS panel. Fill in the required details. Click SUBMIT.
4. Select Asset > User > Manage Asset > Asset Inventory.
5. On the ASSET INVENTORY page, click FIXED on the SELECT THE ASSET TYPE section.
6. On the FILTERS pop-up page of the FIXED ASSET page, specify the Status as Allocated and specify other filter criteria. Click SUBMIT.
7. Select an Asset to reconcile and click the RECONCILIATION button on the ACTIONS panel. An e-mail alert for  the reconciliation is sent to the user.

Bug Reproduction Steps:

1. Log into the Application.
2. Select Dashboard > User Dashboard.
3. On the USER DASHBOARD page, click My Assets under OTHERS section or click the hyperlink received in the alert e-mail.
4. On the MY ASSETS LIST page, select the Tile View option.
5. Select the same Asset and click Reconciliation on the ACTIONS panel. No action is performed.

Now, the Reconciliation button on the MY ASSETS LIST is working properly even if the Tile View option is selected.

64064

On the NOTIFICATION PARSER page, the duplicate mailbox name was displayed. This issue was occurring when a mailbox was attached with different Notification Parsers.

Bug Reproduction Steps:

1. Log into the Application and click the Admin icon.
2. Select Advanced > Notifications > Notification Parser.
3. Select a Tenant.
4. Click on Notification Parser.
5. Under the CREATE tab under CONFIGURE PARSING CONDITIONS, the Mailbox field is displayed with a duplicate mailbox name.

Now, no duplicate Mailbox name are displayed in the Mailbox field on the NOTIFICATION PARSER page.

63110

The Scripting icon was displayed on the All Alerts page, but, when a user clicked the Scripting icon, the Application was not redirecting to the SCRIPTING page.

It is found that the Scripting icon should not be displayed on the All Alerts page and is now removed.