#

Issue

Resolution

64209

Validation and allocation of Software Licenses was not happening through Orchestration when a Service Request was raised. This issue was occurring when SCCM was selected in the Package Source field on the SOFTWARE REQUEST MAPPING FORM page.

Prerequisites:

1. Log into the Application.
2. Select Asset > Configuration > Software > Software Request Mapping Form.
3. On the FILTERS pop-up page, specify the details. Click SUBMIT.
4. Click ADD NEW on the ACTIONS panel of the SOFTWARE REQUEST MAPPING FORM page.
5. On the SOFTWARE REQUEST MAPPING FORM page, specify the Asset Fields, Service Catalog Fields, and other fields. Select SCCM under the Package Source drop-down.

Bug Reproduction Steps:

1. Log into the Application.
2. Raise a SR for the same Software that is mapped in the Prerequisites section. See: Logging Service Requests.
3. Check for validation and allocation of the Software License. It is not happening through Orchestration.

Now, validation and allocation of Software Licenses is happening through Orchestration when a Service Request is raised even though SCCM is selected in the Package Source field on the SOFTWARE REQUEST MAPPING FORM page.

64666

Servers were not displaying in the Servers field on the GROUP DETAILS page. This issue was occurring for the Group Name that was added newly and opened again for modification. Also, the Servers were not getting removed from the Servers field when few of the Servers were unselected and submitted on the GROUP DETAILS page of existing Groups.

Bug Reproduction Steps:

1. Log into the Application.
2. Select Operation > User > Servers > Group List.
3. On the Group List page, select a Tenant and click ADD NEW on the ACTIONS panel.
4. Under the DETAILS section, specify the Group Name, Description, and Servers. Enable the Active check box and click SUBMIT.
5. On the GROUP LIST page, open the same Group and check the Servers from the Servers field. None of the Servers are available.
6. On the GROUP LIST page, open any existing Group and unselect few of the Servers from the Servers field on the GROUP DETAILS page. Click SUBMIT.
7. Click SHOW LIST on the ACTIONS panel and open the same Group Name again.
8. On the GROUP DETAILS page verify the selected Servers in the Servers field. Servers that were unselected in the step 6 are also present in the Servers field.

Now, Servers are getting displayed on the GROUP DETAILS page when a Group is opened for modification. Also, the Servers are getting removed from the Servers field when Servers are unselected and submitted on the GROUP DETAILS page.

64016

The PowerShell scripts are being executed on a 32-bit PowerShell if the scripts are set to run on “Proxy” as CI, and the scripts are being executed on a 64-bit PowerShell if the scripts are set run on “CI” other than proxy. It should use 64-bit PowerShell on proxy.

Now ,the PowerShell scripts are executed on 64-bit PowerShell ,if target is Proxy.

64657

The drop-down list of the child multi-valued attribute was not displaying the values that were configured on the Service Catalog FORM BUILDER page. This issue was occurring while raising the Service Request using a Catalog that was configured with multi-valued parent and child relation.

Example: If the India was configured as the Parent Location and Karnataka, Maharashtra, Kerala were configured as Child Location, while raising an SR using this Catalog, the child multi-valued drop-down attribute was not displaying values as Karnataka, Maharashtra, Kerala.

Bug Reproduction Steps:

1. Log into the Application.
2. Select Catalog > User > Create Service Catalog
3. Under the FORM DETAILS tab, select Module as Service Catalog Management, enter details under the FORM DETAILS tab, and click NEXT button.
4. Select the MV Drop-down control.
5. Configure the Parent - Child relationship from Normal drop-down to Multi-valued combination.
6. Click NEXT to view the Preview.
7. Click NEXT and then click SUBMIT.
8. Refresh the page.
9. Select Request > User > New Service Request.
10. Select the Catalog for which MV Drop-down is configured. The drop-down list of the Child multi-valued attribute is not displaying.

Now, while raising the Service Request using a Catalog that is configured with multi-valued Parent and Child relation, the drop-down list of the Child multi-valued attribute is displaying the values that are configured on the Service Catalog FORM BUILDER page.

63407

The newly created Change Requests were not getting displayed on the CHANGE RECORD LIST page.

Bug Reproduction Steps:

1. Log into the Application and click on Change.
2. Select User > My CRs > New Change Request.
3. Fill in the required details.
4. Click SUBMIT.
5. Click Change.
6. Select User > Change Record List.
7. The newly created Change Request is not displayed in the Change Record List.

Now, the newly created Change Requests are displayed on the CHANGE RECORD LIST page.

64015

The Dependent Work Order was not getting created when the Parent Work Order was resolved using Orchestration.

Now, using Orchestration, if the Parent Work Order is resolved, the Dependent Work Order is created.

64868

Parameter field Data which is entered in “Software Request Mapping Form” is not getting updated in the Orchestration Scripts and SCCM.

Now, Parameter field Data which is entered in “Software Request Mapping Form” is getting updated in the Orchestration Scripts and SCCM.

64014

In Orchestration, the Dependent Script was executed and getting canceled even though the Main Script configured as Recurring in the Schedule Type field had failed and was still getting executed.

Now, the Dependent Script is executed only after the execution of the Main Script or completion of the time limit given for the execution of the Main Script configured as Recurring, (when it is getting failed).

65212

For the EST (Eastern Standard Time) time zone users, the time was getting displayed in IST (Indian Standard Time) format instead of EST format under the Mail History section of the CHANGE HISTORY pop-up page of a Change Record.

Bug Reproduction Steps:

1. Log into the Application and click on Change.
2. Select User > Change Record List.
3. Select a Change Record.
4. On the ACTIONS panel, click the CHANGE HISTORY icon.
5. Check the Mail History section on the CHANGE HISTORY pop-up page. For the EST users, time is displayed in IST.

Now, for the EST (Eastern Standard Time) time zone users, the time is displayed in EST (Eastern Standard Time) format under the Mail History section of the Change History of a Change Record.

64656

There were discrepancies for Linux Monitoring on the SummitAI Staging instance.

Now, no discrepancies are found for Linux Monitoring on SummitAI Staging instance when LinuX CPUNMEM job is picking following utilization data:

• CPU Utilization: The LinuX CPUNMEM job can pick the CPU utilization data only when IsCmdFromTable key is True in proxy and CPU Utilization command is present in the table.
• RAM Utilization: The LinuX CPUNMEM job can pick the RAM utilization data only when IsCmdFromTable key is True in proxy, RAM Utilization is Free, and RAM Utilization Total command is present in the table
  
  

64425

The attachments from the originating Incident were getting deleted after copying an Incident. This issue was occurring when a user copied an Incident with attachments (let’s say five). In the copied Incident few attachments are removed (let’s say two) before submitting the copied Incident. After submitting the copied Incident, the attachments, which were removed in the copied Incident are also getting deleted  automatically from the originating  Incident.

Bug Reproduction Steps:

1. Log into the Application and click on Incident.
2. Select User > Manage Incidents > Incident List.
3. Select an Incident (with multiple attachments) from the list of Incidents.
4. Select the COPY INCIDENT icon on the ACTIONS panel.
5. Delete one or more attachments from the copied Incident before submitting the Incident.
6. Check the attachments in the originating Incident. The attachments deleted from the copied Incident are deleted.

Now, while copying an Incident from another Incident if attachments are deleted from the copied Incident, the originating Incident continues to have all the attachments.

64740

Incidents were not generated, whenever the E-mail parser job is run through the proxy server. This issue was occurring only when the E-mail parser job is run through Proxy server.

Now, Incidents are generated whenever the E-mail parser job is run through the proxy server.

65261

KB recommendation pop up is not appearing while logging the Incident as End user by typing the Question/Answer/keywords in the symptom. This issue was occurring even if the End user is from the same location and Customer to which the KB recommendation is published and even if the End user selects the same Question/Answer/keywords for the symptom.

Bug Reproduction Steps:

1. Log into the Application and click on Incident.
2. Select User > New Incident.
3. Select Tenant and specify the Symptom with either Question/Answer/keywords.
4. KB recommendation pop-up is not appearing.

Now, the KB recommendation pop-up is appearing while logging the Incident by typing Question/Answer/keywords in the symptom.

66233

Updated field value was not displaying on the CI ID page when Owner Workgroup field was updated on the CI ID page using a related Change Record.

Bug Reproduction Step:

1. Log into the Application.
2. Select CMDB > User > Configuration Item List
3. On the CONFIGURATION ITEM LIST page open the CI ID for which you want to update the Owner Workgroup.
4. Select RELATIONSHIP tab.
5. Click Create drop-down and select Change.
6. On the NEW CHANGE RECORD page, provide data in all the fields and click SUBMIT.
7. Update the newly created related CR’s status to Implemented.
8. Select CMDB > User > Configuration Item List
9. Click the same CI ID for which CR is created to update the Owner Workgroup.
10. On the CI ID page, update the Owner Workgroup field and click SUBMIT.

Now, the updated field value is displaying on the CI ID page when any field is updated on the CI ID page using a related Change Record.

64927

Upon configuring the SLA Matrix by Configuration Item (CI) for Incidents under a Tenant and linking the same CI to the Incidents under the RELATIONSHIP tab, the respective SLA Matrix of the CI (including Priority) is applied to the Incidents.

Due to the refresh issue, the Priority for the Incidents were not getting auto-updated based on the SLA Matrix by Configuration Item configuration.

Bug Reproduction Step:

1. Log into the Application.
2. Select Incident > Configuration > SLA Configurations > SLA Matrix By CI.
3. On the SLA MATRIX BY CI page, click ADD NEW on the ACTIONS panel.
4. Select a Tenant, click ADD to search and add CIs.
5. Select a Priority and provide data in all the other fields. Click SUBMIT.
6. Select Incident > User > Manage Incidents > Incident List.
7. Click an Incident ID under the same tenant for which you have configured above SLA Matrix for CI.
8. Click RELATIONSHIP tab.
9. Click Link drop-down and link the same CI that you have selected while configuring the SLA Matrix for the CI on the SLA MATRIX BY CI page.
10. Click GENERAL tab and validate the Priority. The Priority field is not auto-populated based on the configuration.
    

Now, upon linking a CI to an Incident under the RELATIONSHIP tab, the Priority as configured for the respective CI on the SLA MATRIX BY CI page is auto-populated on the INCIDENT ID page.

63304

While logging an SR from the NEW SERVICE REQUEST page, upon providing all the information for the selected Service Catalog, the End User was not able to navigate to the next tab.

Bug Reproduction Step:

1. Log into the Application.
2. Select Request > User > New Service Request.
3. Select a Tenant, Category/ Sub-Category and Service Catalog.
4. Provide data in all the fields for the selected Service Catalog. Click NEXT button.
5. The user cannot navigate to the next page.

Now, upon providing all the mandatory information for the selected Service Catalog, the End User can to navigate to the next tab and complete raising a Service Request.

 65215

In the Incident that was logged using Mail to Incident functionality, the content written under the Description field was not getting displayed in the original format.

Now, in the Incident that is logged using Mail to Incident functionality the content written under Description field is displayed in the original format.

66526

The Administrators can configure the SMS Notification settings for a Subscriber using the SummitAI SMS services to perform various actions in the SummitAI application.

The SMS was not being sent from the SummitAI application to the configured Subscribers (do not confuse with SMS Gateway). An error message, “Delivery failed”, was displayed.

Now, SMS is sent from the SummitAI application to the configured SMS Subscribers without any error message.

25223

In the Mail to Incident functionality, if a client of the Customer replied to the e-mail, the subject line of the replied e-mail was populated with an additional word, "EXTERNAL". Due to this additional word, the subject was changed from the original subject and the Application was creating a new Incident. However, the expected action was to update the respective Incident for which the reply e-mail was sent.

Now, the following configuration key can be modified in the summit_config table:

Mail_To_Ticket_Subject_Remove_RE_FW_Prefix

The word(s) or symbols that need to be excluded from being parsed (e.g. RE:, FW:, [External], (External), and so on) from the subject line of the replied e-mail should be specified using comma.

If appropriate configurations are made, on replying to Incidents, even if "EXTERNAL" word gets added to the reply e-mail, an update about the Incident is received and no new Incident is created.