#

Issue

Resolution

65302

The user with access to a certain .exe file was able to access the version of the same Application that was restricted while configuring the Application control.

This issue was occurring when the Application was executed from the shared/network folder. The Application controller was not able to extract the file properties. Hence, the user was able to access the version of the Application that was restricted using Application Controller.

Now, the Application Controller can extract the file properties of the Application that is executed from the shared or network folder.

So, the user with access to a .exe file cannot access the version of the same Application which is restricted in the Application Controller.

65291 

Model Number for the MAC agent was not getting captured on the Hardware Discovery tab of ASSET DETAILS page.

Bug Reproduction Steps:

1. Log into the Application.
2. Select Reports > Asset Management.
3. On the REPORTS drop-down select Agent Online Status Report.
4. On the AGENT ONLINE STATUS REPORT page, specify Filters and click SUBMIT.
5. Make sure the System Type is MAC agent on the AGENT ONLINE STATUS section.
6. On the AGENT ONLINE STATUS tab, select and open to get the Asset details.
7. On the ASSET DETAILS pop-up page, select Hardware Discovery tab.
8. Check the Model Number field, no value is displayed.

Now, the Model Number for the MAC agent is getting captured on the Hardware Discovery tab of ASSET DETAILS page.

 65294 

Improper asset details are displayed in the “Reminder to Accept Allocated Asset” email. It is observed in the Reminder to Accept Allocated Asset email triggered to the end-user, that the host name, make and model fields are inhibiting the values from the previous fields if the fields are blank.

Prerequisites:

1. Configure one asset category (laptop) with serial no, host name, make, and model. 
2. Configure one more asset category (desktop) with only with serial no.

Bug Reproduction Steps:

1. Log into the Application.
2. Allocate an asset to user for Asset Category Laptop.
3. Allocate an asset to user for Asset Category Desktop.
4. Initiate a job "Reminder to Accept Asset" and verify the mail triggered to allocated user.

Now, no improper asset details are displayed in the "Reminder to Accept Allocated Asset" email.

66090

ADD TO CART option was getting displayed on the New Service Request page when an SR was being raised from the User dashboard page even though ENABLE CART checkbox was unchecked on the Tenant page.

Prerequisite:

1. Log into the Application.
2. Select Admin > Basic > Infrastructure > Tenant.
3. On the TENANT page, specify the Filters and click SUBMIT.
4. On the TENANT page, select a Tenant and click CONFIGURE DETAILS under ACTIONS panel.
5. Under the MODULES, select SERVICE REQUEST.
6. Uncheck the ENABLE CART checkbox under For End Users section.

 Bug Reproduction Steps:

1. Log into the Application.
2. Select User dashboard. Type in a Catalog name in the Log Issue/Request field and select catalog from the result.
3. Check the details on the New Service Request page, ADD TO CART option is getting displayed.

Now, ADD TO CART option is not getting displayed on the New Service Request page when ENABLE CART checkbox is unchecked on the Tenant page.

65749 

After submitting the Validity period value under the ACHIEVEMENTS tab of the GAMIFICATION page, the selected validity period value was not displayed in the Period field.

Bug Reproduction Steps:

1. Log into the Application and select Admin.
2. Select Advanced > Productivity > Gamification.
3. Under ACHIEVEMENTS tab, select Validity as Period.
4. Select a Period value and click SUBMIT.
5. The Period value is displayed as blank.

Now, the Period value under the ACHIEVEMENTS tab of the GAMIFICATION page is displaying the correct value.

66532

A pop-up message, “The Service name already exists!”, was displayed, whenever a user tried to add a new Service in the CMDB. This issue was occurring, because, for example, if the user created a Service as “ABC”, and then tried to create one more Service as “AB.” The Application was interpreting the name “AB” same as  “ABC” since the word “AB” is present in “ABC.”

Bug Reproduction Steps:

1. Log into the Application and click CMDB.
2. Select User > Services.
3. Click ADD NEW and add a new Service, let’s say ABC. Click SUBMIT.
4. Click ADD NEW to add a new Service let’s say AB.
5. A validation message is displayed, “The Service name already exists!”

Now, Services can be added in the CMDB without any error

66336

The Daily Incident Report was not showing all Incidents when it was exported to excel using EXPORT TO EXCEL or EXPORT ALL option. This issue was occurring when the report included an Incident which contained <% symbols together in the Solution field. Hence, excel sheet was considering <% characters as skip tag. And all the subsequent Incident records were skipped and not exported into the excel.

Bug Reproduction Step:

1. Log into the Application as an End User.
2. Select Incident > User > New Incident.
3. Select a Tenant, provide data in all the mandatory fields, and click SUBMIT.
4. Log into the Application as an Analyst.
5. Select Incident > User > Manage Incidents > Incident List.
6. Click on the same Incident ID that you have created.
7. Move the Incident to Resolved status and provide solution comment with <% characters in the Solution field. Click SUBMIT.
8. Select Report > Incident Management.
9. On the REPORTS drop-down, search and open the Daily Incident Report.
10. Click Filters icon on the ACTIONS panel, select the same Tenant for which the above Incident is resolved. Click SUBMIT.
11. Click the EXPORT TO EXCEL or EXPORT ALL icon on the ACTIONS panel, the Daily Incident Report gets downloaded.
12. Open the downloaded excel report and check the Incident details, incidents that are falling after the specific incident to which <% in mentioned is the Solution, are not exported to excel.

Now, the Daily Incident Report shows the record of all Incidents when it is exported to excel using EXPORT TO EXCEL or EXPORT ALL option.

59498 

While raising Change Requests using Change Request templates, the Business and Operational Risk field values were displaying random values.

Prerequisites:

Make sure there is a Change Record template for the Tenant.

Bug Reproduction Steps:

1. Log into the Application and click Change.
2. Select User > New Change Record.
3. On the ACTIONS panel, click IMPORT TEMPLATE.
4. Select a Template.
5. After selecting the template, the Business and Operational Risk field display random values.

Now, no random values are displayed in the Business and Operational Risk fields of the Change Request while creating a Change Request using a Change Request template. The user can define the values as per the requirements.

66589

The HARDWARE VARIANCE DETAILS was showing the HDD data different from the actual Inventory data. This issue was occurring as the decimal value of the HDD was not rounding up to the next integer value on the HARDWARE VARIANCE DETAILS tab.

Example: If the HDD capacity was discovered as 200.51 GB, then the HARDWARE VARIANCE DETAILS was showing the HDD capacity as 200 GB only.

Bug Reproduction Steps:

1. Log into the Application.
2. Select Asset > User > Manage Assets > Variance > New discovery.
3. On the FILTERS pop-up page, select a Tenant and specify the details. Click SUBMIT.
4. On the NEW DISCOVERY page, select check box corresponding to the Asset category (Server or Desktop, etc.). Click IMPORT.
5. Specify the Category, Mapping, and Allocation details. Click SUBMIT.
6. Select Asset > Configuration Mapping > CMDB Mapping.
7. On the CMDB MAPPING page, select a Tenant, Category, and Classification. Click SUBMIT.
8. Select Asset > User > Manage Assets > Asset Inventory.
9. On the ASSET INVENTORY page, select FIXED option and select the same category on the FIXED ASSET page. Click SUBMIT.
10. On the FILTERS pop-up page, select CMDB Export in the Status field and specify the other details. Click SUBMIT.
11. On the FIXED ASSET page, select the Asset ID and click EXPORT TO CMDB.
12. On the CMDB EXPORT page, specify the required details and click SUBMIT.
13. Select Admin > Basic > Infrastructure > Custom Scheduler.

14. On the CUSTOM SCHEDULER page, configure the CI Variance AutoUpdate job.
    

    Note:

    Make sure that the CI Variance AutoUpdate job is executed successfully before you open CI details.

15. Select CMDB > User > Configuration Item List.
16. On the CONFIGURATION ITEM LIST select a CI.
17. On the CI Details page, click HARDWARE VARIANCE on the ACTIONS panel.
18. Verify the HDD details on the HARDWARE VARIANCE DETAILS pop-up page. HDD value is less than the Inventory.

Now, the decimal value is rounded up to the next integer value and displayed accordingly.

Example: If the HDD capacity is discovered as 200.51 GB, it is rounded up to 201 and displayed on the HARDWARE VARIANCE DETAILS tab.

65056

After executing the CI Variance AutoUpdate job, the RAM and HDD sizes that were getting captured on the DESKTOP or SERVER tab of the CI record was not matching with actual Asset details.

Bug Reproduction Steps:

1. Log into the Application.
2. Select Asset > User > Manage Assets > Variance > New discovery.
3. On the FILTERS pop-up page, select a Tenant and specify the details. Click SUBMIT.
4. On the NEW DISCOVERY page, select checkbox corresponding to the Asset category (Server or Desktop, etc.). Click IMPORT.
5. Specify the Category, Mapping, and Allocation details. Click SUBMIT.
6. Select Asset > Configuration Mapping > CMDB Mapping.
7. On the CMDB MAPPING page, select a Tenant, Category, and Classification. Click SUBMIT.
8. Select Asset > User > Manage Assets > Asset Inventory.
9. On the ASSET INVENTORY page, select FIXED option and select the same Category on the FIXED ASSET page. Click SUBMIT.
10. On the FILTERS pop-up page, select CMDB Export in the Status field and specify the other details. Click SUBMIT.
11. On the FIXED ASSET page, select the Asset ID and click EXPORT TO CMDB.
12. On the CMDB EXPORT page, specify the required details and click SUBMIT.
13. Select Admin > Basic > Infrastructure > Custom Scheduler.

14. On the CUSTOM SCHEDULER page, configure the CI Variance AutoUpdate job.
    

    Note:

    Make sure that CI Variance AutoUpdate job is executed successfully before you open CI details.

15. Select CMDB > User > Configuration Item List.
16. On the CONFIGURATION ITEM LIST, select a CI.
17. On the CI Details page, click DESKTOP or SERVER tab and verify the RAM and HDD size. RAM and HDD sizes are less than the Inventory details.

Now, after executing the CI Variance AutoUpdate job, the RAM and HDD sizes that were getting captured on the DESKTOP or SERVER tab of the CI record are matching with actual Asset details.

66334

While consuming the GetAllMyWkgWorkorders API method to fetch the Work Orders for a specific date range, the incorrect syntax error message was displayed.

This issue occurred if the user’s time zone value was in negative as after converting the minus time zone value, the minus symbol was preceded by another minus symbol of the precedented dynamic query, e.g. <dynamic query - - time zone value>. So, the system was considering the double minus symbols as a comment within the SQL statement.

Now, while consuming the GetAllMyWkgWorkorders API method, the Work Orders for the specific date range are displayed without any error message even though the user’s time zone value is in negative.

63933

On the ANALYST DASHBOARD page, the Response SLA Performance and Resolution SLA Performance widgets were overlapping on the Incident SLA Summary and Service Request SLA Summary graph. This issue occurred due to the incorrect width of the widget and the screen resolution.

Bug Reproduction Step:

1. Log into the Application.
2. Click ANALYST DASHBOARD.
3. Scroll down and check the Service Request SLA Summary and Incident SLA Summary graphs.

The respective CSS is modified. Now, the widgets are not overlapping on each other.

65813

The attachments uploaded while creating or updating a Service Request from the Web Application was not getting downloaded using Summit_GetAttachmentForControl API.

This issue occurred as UID was getting saved from table SR_ServiceTicket_Details in the SR_Dynamic_Attachment table instead of SR number while raising new SR with an Attachment.

Now, the Summit_GetAttachmentForControl API method is modified to fetch and pass the UID of the SR number to download the attachment.

To get the UID based on the TicketNo, the AttributeID, and AttachmentName are passed in the Summit_GetAttachmentForControl API method, and the same is passed in TicketID to get the attachment.

The Log Time value on the TASK ID page displayed the script created date and time as default instead of the task creation date and time.

Prerequisites:

Make sure that scripting has done on the TASK ID page.

Bug Reproduction Steps:

1. Log into the Application
2. Select Change > User > Change Record List.
3. On the CHANGE RECORD LIST page, select and open a Change Record.
4. On the CHANGE RECORD DETAILS page, click the Relationship tab.
5. Click Create and Select Task from the drop-down list.
6. The Log Time field displayed the script created date and time as default instead of the task creation date and time.

Now, the Log Time field displays the actual task creation date and time even if scripting performed.