#

Issue

Resolution

63772

Details of the inactive Software Licenses were also getting included in the Software License Utilization alert notification.

Prerequisites:

1. Log into the Application.
2. Select Asset > Asset Inventory > Software.
3. On the SOFTWARE DETAILS page, specify the FILTERS criteria. Click SUBMIT.
4. On the LICENSE DETAILS page, select the Software Assets to deactivate and click DEACTIVATE on the ACTIONS panel.
5. Select Asset > Configuration > Others > Asset Alert Configuration.
6. On the ASSET ALERT CONFIGURATION page, select the same Tenant that was selected during software deactivation and click ADD NEW on the ACTIONS panel.

7. On the ASSET ALERT CONFIGURATION DETAILS page, select Software License Utilization under the Alert Type field and configure the other fields. Click SUBMIT. 

   Note:

   Make sure that the alert is set in advance (in days) = 0

8. Select Admin > Basic > Infrastructure > Custom Scheduler.

9. On the CUSTOM SCHEDULER page, click ADD NEW on the ACTIONS panel.
10. On the CUSTOM SCHEDULER DETAILS page, configure the Asset Software Compliance Alert” job.

Bug Reproduction Steps:

1. Upon execution of Software License Utilization alert notification, verify the details of Software Licenses.
2. Inactive Software Licenses are also found in the alert notification.

Now, only details of active Software Licenses are captured in the Software License Utilization alert notification.

67180

The Last Updated field data format was not consistent when the OPERATING SYSTEM SUMMARY or SOFTWARE LICENSE USAGE details from the Asset Dashboard report were exported to a Microsoft Excel sheet.

 Bug Reproduction Steps:

1. Log into the Application.
2. Select Report > Asset Management.
3. Select DASHBOARD under REPORTS drop-down and specify the FILTERS criteria. Click SUBMIT.
4. On the OPERATING SYSTEM SUMMARY tab or SOFTWARE LICENSE USAGE tab, click the View Data icon.
5. Under the OPERATING SYSTEM SUMMARY tab or SOFTWARE LICENSE USAGE tab, click the count hyperlink.
6. On the OPERATING SYSTEM SUMMARY or SOFTWARE LICENSE USAGE pop-up page, click EXPORT TO EXCEL icon. 
7. Open the downloaded Excel and verify the data of the Last Updated column.
8. The data format of the Last Updated column is not consistent.

Now, when data is exported from the Asset Dashboard report to an Excel sheet, the Last Updated field data of the OPERATING SYSTEM SUMMARY or SOFTWARE LICENSE USAGE tabs, the data is displaying in correct format.

67088

While trying to filter records on the PATCH REPORT page, the, “Oops! An error occurred”, message was getting displayed.

Bug Reproduction Steps:

1. Log into the Application.
2. Select Asset > User > Patch Management > Patch Report.
3. On the PATCH REPORT page, specify the FILTERS criteria and click SUBMIT.
4. “Oops! An error occurred”, message is getting displayed on the screen. 

Now, the users can filter records on the PATCH REPORT page without any error

67293 &

67309

The SCCM Software Data Sync job that was scheduled to run at specific intervals was not running correctly. This issue was occurring when the SCCM Software Data Sync job schedule was falling on the following day.

Example: Let’s say SCCM Software Data Sync job was scheduled at 3:00 PM to run every 8 hours as follows:

• 3.00 PM - First schedule (Day one)
• 11:00 AM - Second schedule (Day one)
• 7:00 AM - Third schedule (Day two)

From the third schedule onwards, job was not running as per the schedule.

Prerequisites:

1. Log into the Application.
2. Select Admin > Basic > Infrastructure > Custom Scheduler.
3. On the CUSTOM SCHEDULER page, click ADD NEW under the ACTION panel.

4. On the CUSTOM SCHEDULER DETAILS page, configure a new job for the SCCM Software Data Sync and click SUBMIT.
   

   Note:

   Make sure that the job frequency is set correctly.

Bug Reproduction Steps:

1. Upon execution of the SCCM Software Data Sync job, verify the job running intervals.
2. The SCCM Software Data Sync job is not running as per the schedule.

Now, the SCCM Software Data Sync job is running properly as per the schedule.

67076

Attachments for the Custom Attributes were not getting saved while raising Service Requests using the SummitAI Mobile App.

Now, all the attachments for the Custom Attributes are getting saved while raising Service Requests using SummitAI the Mobile App.

64530

The Response deadline was getting incorrectly violated for few Incidents, which were assigned to the Analysts using the SummitAI Mobile App. This issue was occurring as 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. 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 Mobile App.
2. Select Incident > Workgroup Incidents.
3. On the INCIDENT details page, select an Analyst under Assign Executive field and check the SLA Violated field. It is showing Yes.

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

67888 & 67887

Rules are templates that you can configure to log Incidents with pre-selected data without the need to key-in each information. While configuring a Rule on the RULE page, all the CIs were not getting populated when only a few characters of the CI name were typed in the Configuration Item drop-down field, however, on the CONFIGURATION ITEM LIST page, all the CIs were getting displayed.

Bug Reproduction Step:

1. Log into the Application.
2. Select Incident > Configuration > Others > Rule.
3. On the RULE page, select a Tenant and click ADD NEW on the ACTIONS panel.
4. On the RULE details page, provide data in all the fields and type in the initial few characters of a CI name under the Configuration Item drop-down field.
5. Only a few CIs are displayed for the specified text instead of all the CIs.

Now, while configuring a Rule on the RULE page, the first 15 records of the related CIs are populated in the Configuration Item search field when a few characters of the CI name is typed in the field.

67900 & 67807

While viewing the Knowledge Record, the Answer details with bulleted points was not getting displayed.

Example:

Content written while creating KB

The Incident is assigned based on the following factors:

• Category and Classification
• Impact, Urgency, and Priority
• Service Window

Contents displayed while viewing KB

The Incident is assigned based on the following factors:

(Bulleted points information is not displayed)

Bug Reproduction Step:

1. Log into the Application.
2. Select Knowledge > User > New Knowledge Record.
3. Write an Answer content using bullet points, provide data in all the fields. Click SUBMIT.
4. Move the KB article to Published status.
5. Search the same KB article on the KNOWLEDGE DASHBOARD or New Incident page or Looking For An Answer field.
6. Check the Answer text box. The Answer description written using bullet points is not displaying.

Now, all information in the Answer field of the Knowledge Record is displayed correctly including the bulleted points.

64807

On the SERVICE REQUEST ID page, the SR Requester was able to change the To Date in the Service Validity of the SR more than the allowed maximum no. of days. The Service Validity for Service Catalogs is configured by the Administrator on the Service Catalog FORM BUILDER page. This issue was observed when an SR was referred back to the Requester.

Prerequisites:

• The Service Validity should be enabled at the Catalog level.
• There should be at least one Custom Attribute configured on the FORM BUILDER page.
• There should be at least one level of Approver configured in the Workflow.

Bug Reproduction Steps:

1. Log into the Application as an End User..
2. Select Request > User > New Service Request.
3. Select a Service Catalog for which the Service Validity is configured.
4. Provide data in all the remaining fields and click SUBMIT.
5. Now, log out and log into the Application again as the Approver of the SR.
6. Select Request > User > Approve Service Requests.
7. Select the SR that is created in the above steps 1-4.
8. Change the SR status to REFER BACK.
9. Now, log out and log into the Application as the SR Requester.
10. Select Request > User > My Service Requests.
11. On the My Service Requests page, specify the Filters and select the SR that was Referred Back.
12. Change the To Date under the Service Validity section more than the maximum no. of days.
13. No validation or error is displayed upon submitting the change.

Now, the SR Requester cannot change the Service Validity To Date of the referred back SRs beyond the maximum configured limit.

66903

Users were receiving false alerts related to Incidents and unable to close the Incidents. This issue was occurring when few Services of the Servers were displaying incorrect output in the result.

Now, the users are receiving correct alerts related to Incidents created for Servers.

67206

After upgrading from V5.6 SP2 version to ALPS HF05 version of the SummitAI application, the configured Archival for the IT Operations Management module was not displaying on the ARCHIVAL page in the SummitAI ALPS HF05 version.

Bug Reproduction Steps:

1. Log into the Application.
2. Select Admin > Basic > Infrastructure > Archival.
3. On the FILTERS pop-up page, select the Module field. The IT Operations Management field value is not displayed in the Module drop-down list field.

Now, after upgrading the SummitAI application for Alps SP1HF08, the configured Archival for IT Operations Management module is displaying on the ARCHIVAL page.

66912

Even if there was no Hardware Variance for the Assets, the Hardware Variance data was wrongly captured in the e-mail notifications to the users.

Prerequisites:

1. Log into the Application.
2. Select Asset > Variance > Hardware Variance.
3. On the HARDWARE VARIANCE page, specify the FILTERS criteria. Click SUBMIT.

   Note:

   Make sure that there are Assets on the HARDWARE VARIANCE page.
4. Select Asset > Configuration > Asset masters > Key Field Mapping.
5. On the KEY FIELD MAPPING page, select the same Tenant and Category that were selected while specifying the filters criteria in step 3.
6. On the KEY FIELD MAPPING DETAILS page, select Automatic under the Variance Type field.
7. Select Admin > Basic > Infrastructure > Custom Scheduler.
8. On the CUSTOM SCHEDULER page, click ADD NEW on the ACTIONS panel.
9. On the CUSTOM SCHEDULER DETAILS page, configure the Asset HW and SW Variance Summarization and Asset Variance Alert jobs.

Bug Reproduction Steps:

1. Upon execution of the Asset HW and SW Variance Summarization and Asset Variance Alert jobs, verify the Hardware Variance data sent to the user.
2. Incorrect Hardware Variance data is getting captured in the e-mail notification triggered to the user.

Now, only the correct Hardware Variance data is getting captured in the email notifications sent to the users.

68218

On the KNOWLEDGE DASHBOARD page, the special character ‘&’ in the Knowledge Record name was not displaying correctly.

Example: When a special character ‘&’ was used in the Knowledge Record name, after publishing, it was getting replaced with the ‘&’ character.

Bug Reproduction Step:

1. Log into the Application.
2. Select Knowledge > User > New Knowledge Record.
3. Create a Knowledge Record with special character ‘&’ in the name.
4. Move the KB article to Published status.
5. Select the KNOWLEDGE DASHBOARD tab and search for the same KB article.
6. The Knowledge Record name is displaying incorrect character ‘&’ instead of ‘&’ character.

Now, the Knowledge Record name is displaying the special character ‘&’ correctly on the KNOWLEDGE DASHBOARD page.

66321

While raising multiple Service Requests using the Service Catalog Package option, an error message, “Oops! An error occurred”, was displayed. This issue occurred when the apostrophe character (‘) was used in the Remarks or in any Custom Field value of the Service Request.

Prerequisites:

1. Create two Service Catalogs with at least one text box Custom Field, see Creating Service Catalogs.
2. Create a Package Catalog and add the above two Service Catalogs to the Package, see Configuring Service Catalog Packages.

Bug Reproduction Steps:

1. Log into the Application.
2. Select Request > User > New Service Request.
3. Select a Tenant and Category.
4. Select the configured Package under the selected Category.
5. Specify an apostrophe in the Remarks or the Custom text field.
6. Provide data in all the other mandatory fields and click SUBMIT.
7. Oops! An error occurred”, message is displayed.

Now, no error is displayed while raising multiple Service Requests using the Service Catalog Package option even though there is an apostrophe character (‘)in the Remarks or Custom text field.

65989

Duplicate Incidents were getting generated for the same Server Threshold breach in Script-based Monitoring. This issue was occurring when the Incident Closing Mode was specified as Manual on the INCIDENT TEMPLATE page and Ignore Re-logging Incident check box was selected under the INCIDENT CONFIGURATION tab of the ACTION TEMPLATE page.

Example: An Event (E1) and Incident (I1) were created when the Utilization in the Script-based Monitoring was High. Only the Event (E1) was closed when the Utilization was Normal. If again, the Utilization went High, another Event (E2) and Incident (I2) were getting created even though the first Incident (I1) was still open.

Now, no more duplicate Incidents are created for same Server Threshold breach in Script-based Monitoring.

67503

In Orchestration, the Script of the second trigger was taking input from the first Script of the first trigger instead of the first Script of the second trigger when Orchestration was getting executed multiple times. This issue was occurring when multiple Scripts were configured for an Orchestration trigger.

Prerequisites:

1. Orchestration Scripts consisting of parameters should be configured.
2. Make sure that the Create /Update Populate always is selected in the Execute When field on the ORCHESTRATION page.
3. Make sure that two or more Scripts are configured, and the second Script is taking the output of the first Script as one of the inputs. Also, the third Script is taking the output of the second Script as one of the inputs.
4. Make sure that the Orchestration job is running.

 Bug Reproduction Steps:

1. Log into the Application as an Administrator who is also having Analyst access.
2. Select Request > User > New Service Request.
3. On the New Service Request page, select the same Tenant for which Orchestration is configured. Provide all the data and click SUBMIT.
4. Select Request > Manage Service Requests > Service Request List.
5. On the SERVICE REQUEST LIST page, specify the Filters and select the same SR that is raised through steps 1-3.
6. On the SERVICE REQUEST DETAILS page, click the ORCHESTRATION tab to see the Orchestration scripts of the first Trigger that are linked to the SR.
7. Make sure that the Scripts are executed successfully.
8. Select Admin > Advanced > Orchestration > Orchestration Scripts.

9. Open the Script configured for the 1st action in the trigger and modify the code. Click SUBMIT.

   Note:

   Make sure that the output of the first Script is different than the output of the previously executed first Script, configured for the first trigger.

10. Select Request > Manage Service Requests > Service Request List.
11. On the SERVICE REQUEST LIST page, specify the Filters and select the same SR that is raised through steps 1-3.
12. On the SERVICE REQUEST DETAILS page, modify any details, for example, Priority change, etc., and click SUBMIT.
13. Click the ORCHESTRATION tab to see the Orchestration scripts of the same Trigger that are linked to the SR for the second time.
14. Make sure that the Scripts are executed successfully.
15. The output of the first Script in the first trigger is being passed as an input to the second Script of the second trigger instead of the first Script of the second trigger.

Now, the Orchestration Scripts are taking input from the configured Script of the same trigger when Orchestration is triggered multiple times.