Customer Fixed Issues and Known Issues Denali SP1 HF11

Parent Incident having 250+ child incidents linked was not updating and displayed the following error message.

Oops! An error occurred while saving the incidents details is displayed.

Prerequisites:

1. Navigate to Incident > Manage Incidents > Incident List.
   The Incident List page is displayed.
2. Click on the Incident ID which is in Pending
3. Click on Relationship
4. Link child incidents (250+) incidents.
5. Click SUBMIT.
6. Click on In Progress
7. Click SUBMIT to submit the Incident.

Now, Parent Incident is updated without any errors.

88985

In Server Group View, if the Group name is longer than a specified limit, it would extend beyond the group tile space.

Click Operations> Views> Server Group View.

Now the group name is truncated after a certain length with ellipsis and full name is displayed in tooltip on hover.

89361

MOM server was not acknowledging the monitoring alerts after restart.

MOM server manages the alerts and notifications of other monitoring tools. It is hosted in the customer environment and is integrated with the 3^rd party monitoring tools.

When the application host server is restarted, LastEventDate value in MOM_alert.xml file (Bin folder) is wiped out. Due to this, MOM server is obstructed from capturing alerts.   

A default time of 30 minutes prior to current time has been incorporated as  LastEventDate value in MOM_alert.xml file (Bin folder). Now the MOM server functions as expected even after restart.

88727

CPU Utilization parameters were not monitored for the newly added servers using the SAR command.

The following VMSTAT command is used in Summit_ProxyServer Config to capture CPU utilization of LINUX machines:

<add key="LINUX:IsLinuxCPUFromVmstat" value="True" /> 

Customer wants output using the following SAR command:

cpu=`sar 1 5 | tail -1 | awk '{print $8}'`; echo 100 - $cpu | bc. 

An additional block and key are implemented to output CPU Utilization parameters using SAR command. SAR command modified to:

cpu=`vmstat 1 5 | tail -1 | awk '{printf "%.0f\n", $15}'`; echo 100 - $cpu|bc

88864

New linux agents must be detected and monitored automatically after installation.

 N/A

Now, on installing a new Linux agent, if the corresponding IP address is not being monitored, then it is added to the monitoring list with default configurations and monitored then on.

If the Planned Start Time was less than the Current Time it displayed the following validation message:

“Planned start Time should be greater than current time”.

Also, after reloading of NEW CHANGE RECORD page, the configured custom fields were getting disappeared.

Prerequisites:

1. Navigate to Change > User > New Change Record.
2. Specify all the mandatory fields.
3. Under the Timelines tab, specify the Planned Start Time which is lesser than the current time.
4. Click SUBMIT.

Now, the configured custom fields are not getting disappeared.

Prerequisites:

1. Navigate to Request > Manage Service Requests > Service Request List. The Service Request List page is displayed.
2. Click on any SR. The SR details page is displayed.
3. Navigate to Change > My CRs > My Change Requests.
   The MY CHANGE REQUESTS page is displayed.
4. Click on any CR. The CR details page is displayed.

Now, SR Page is not loading for a longer period.

Also, CR page displays all fields without any missing fields.

Prerequisites:

1. Configure "SR Reminder - To All Current Approvers" job in Custom Scheduler.
2. Navigate to Request > SLA Configurations > Approver Reminder Configurations to configure the Approver Reminder.
3. Create a catalog and configure one approver in the workflow.
4. Delegate approver role to more than one person.
5. Raise an SR and check if approver e-mails are triggering or not.

When Analyst attempted to update the ticket, the following validation message was displayed even though the ticket was in the New status.

“Please configure technician selectable approver to proceed further'.”

Also, status was displayed as Pending in APPROVAL DETAILS tab in SERVICE CATALOG DETAIL pop-up under CATALOG DETAIL.

Prerequisites:

1. While creating a catalog for the workflow select Technician Selectable from Approver drop-down list.
2. Click SUBMIT.
3. Publish the catalog.
4. Navigate to Requests > New Service Requests and raise the new SR ticket.
5. Login to application as an Analyst.
6. Navigate to Request > Manage Service Requests > Service Request List.
   The Service Request List page is displayed.
7. Click on newly created SR ID.
   The SR ID details page is displayed.
8. Click on Set Approver under Actions. Now select the Caller as Approver. Click Submit.
9. Navigate to Requests > Approve Service Requests.
   The Approve Service Requests page is displayed.
10. Click on the same SR ID and refer back that ticket to Requestor (Requests > APPROVE SERVICE REQUEST > Approval Status > Refer Back, Requestor).
11. Click Submit.
12. Navigate to Request > My Service Request. The My Service Requests list page is displayed. Open the same SR ID. Specify the comments in Additional Information and click Submit.
13. Navigate to Request > Manage Service Requests > Service Request List.
    The Service Request List page is displayed. Open the same SR ID.
    The Service Request List details page is displayed in the New status.
14. Specify the mandatory fields and click SUBMIT. 

Now, the Analyst can update the ticket without any validation message.

89566

The users were getting redirected to the Summit Form Login page instead of the SSO SAML Authentication page.

This issue occurred when the admin clicked on the ‘ID’ hyperlink from the excel file of the report generated.

NA

Now, the users are getting redirected to the SSO SAML Authentication page.

87925

On adding an inactive link again, it is saved without validation but on submission, the inactive link disappears.

Earlier, the existing deleted or deactivated link would get updated automatically interface without any prompts. This caused confusion as to whether the link was activated or not.   

On adding an inactive link again, validation pop-up is displayed - “The selected link is deactivated, please activate it before usage or would you like to create a new one?” before save and the link does not disappear.

87926

When changing device type for the switch device from switch to access switch in the network view, the device icon disappears after save but post submission, the view is reflected.

Prerequisite:

1. Add a device and submit
2. Reopen the device and change the device type
3. Save
4. Device will disappear but once you submit, it will display again.

Now the device icon stays after the save and submission.

89237

For a logged incident, when the Analyst initiated the send-to email option, the scheduled time was displayed in the UTC time zone in the triggered Email instead of displaying in the caller time zone.

Precondition: The Schedule Date keyword must be added in the Send E-mail with details notification template.

Now, in the triggered Email, the scheduled time is displayed in the caller time zone.

88784

Notification e-mail was not triggered to the Requestor when a new Change Request was raised.

The issue occurred only when Task was configured in the first level of the workflow.

Now, notification e-mail is triggered to the Requestor and the initiator upon creating a new Change Request.

86949

In the Service Catalog approval workflow, the  arrow signs between the Activity attributes were missing. Due to which user was not able to collate the flow.

N/A

Now, the arrow links between the Activity attributes are displayed as expected.

89311

On the Network Device Configuration Report, the following issues were observed:

• The Network device were not displayed in the report that contain null values
• Incorrect date and time was shown under the Fr0m Date and To Date columns on the report List page.

This issue occurred because the GMT time was added twice in the actual From and To Date values.

Now, the Network device are displayed in the report that contain null values. Also, the From and To Dates are shown correctly.

88440

In the Agent Online Status report for a few machines, IP Address was not captured though the IP Address was displayed in the Hardware Discovery tab.

This issue was observed when user used dongle for internet connectivity.

Now, the IP address is captured in the Agent Online Status report even though the user uses the dongle for internet connectivity.

88599

On Print Allocation form, the Non-Fixed assets details are not captured though the Non-fixed assets were assigned to the user. The form was displaying only the Fixed assets details.

This issue occurred when the print form is generated from Asset by User report.

Now, on the Print Allocation form both i.e., Non-Fixed and Fixed asset details are captured.

87641

It was taking too long to access the application while login. Due to which the performance was becoming slow.

This issue occurred when the user with End User or Analyst role in the Incident Management was trying to login to the application.

Now, the slow performance issue is fixed.

Pre-requisites:

 This issue occurred when a user added a comma (,) into the group header name due to which two different titles or group header names were created

Pre-requisites:

1. Configure a user as an approver and a workgroup owner.
2. A user should not associate with analyst access.
3. In Tenant configuration page, select the Allow problem Manager to Authorize PR check box.

Pre-requisites:

1. Navigate to Change > New Change Record.
2. Enter the required details and click Submit.
3. Click Relationship tab and create the tasks.
4. Change the CR status to Cancelled and click Submit.

Earlier, the existing deleted or deactivated link would get updated automatically interface without any prompts. This caused confusion as to whether the link was activated or not.

On adding an inactive link again, validation pop-up is displayed - “The selected link is deactivated, please activate it before usage or would you like to create a new one?” before saving and the inactive link persists now.

Email notifications are triggered for a CR in Draft status.

Pre-requisites:

CR Notification mails should be enabled at Custom Scheduler.

1. Navigate to Change > New Change Record
2. Enter the required fields as described in the New Change Record page.
3. Select the date range from TIMELINES section.
4. Draft a CR

Now, email notifications are triggered for the submitted CRs.

The mandatory validation of Configuration Name field was not triggered.

For example, user could submit the tenant details without entering the mandatory Configuration Name field.

Pre-requisites:

1. Navigate to Problem > Configuration > Auto Creation Settings
2. Select a Tenant
3. Click Add New from Action section.
4. Enter the required details except Configuration Name field.
5. Click Submit

This issue occurred when user logged out of SummitAI application.

Pre-requisites:

1. Login to Izenda6 BI Report page.
2. Click Save or perform any action.

Pre-requisites:

Overridable checkbox must be checked from Customer/Vendor SLA Matrix page.

88436

Bug Reproduction Steps:

1. Log a PR outside the SLA window matching the configured deadline.
2. Authorize the PR.
3. Submit the RCA.
4. Approve the RCA.

Issue:

Post RCA Approval, the Problem Record Resolution deadline was getting updated incorrectly.

Prerequisites:

1. On the DEADLINE CONFIGURATION page, select the Resolution Deadline Type as RCA Deadline Time.
2. Set RCA Deadline (In Hours)> Resolution Deadline (In Hours)
3. Set SLA Service Window and fill the other mandatory details. Click SUBMIT to save the configuration.
4.  On the DEADLINE CRITERIA pop-up, Set Calculate RCA Deadline as When RCA Approved and Exclude SLA for Status as Pending.

Now, the Problem Record Resolution deadline is getting captured correctly.