Customer Fixed Issues and Known Issues Denali SP1 HF10

Change Record Details page is not aligned as expected.

An error “Job option already exists!” was displayed when the Administrator was configuring a Recurring Incident job for other Tenants. Due to this, the Administrator was not able to configure multiple Recurring Incident Jobs.

However, the expected functionality allows the Administrator to configure multiple Recurring Incident jobs for the same or different Tenants.

Prerequisites:

Navigate to Admin > Basics > Infrastructure > Custom Scheduler.

Configure the Recurring Incident Job at Custom Scheduler page for a particular Tenant (For example: Information Technology), Caller, and Workgroup.

On the New Incident page, while specifying the symptoms under Symptom in Details section, it also displays the rule suggestions belonging to other tenants.

Prerequisites:

1. To configure the rules, navigate to Incident > Configuration > Others > Rule.
2. Configure the rules for two tenants.
3. Navigate to Incident > User > New Incident.
4. Specify the configured symptom of rule from another tenant.

Under the ENVIRONMENTAL PARAMETER tab, WLC parameters are reflecting.

Prerequisites:

1. Navigate to Operations > User > Views > Network Device View.
2. On the NETWORK DEVICE VIEW page, select the Tenant under Filters. Click Submit.
3. A list of configured devices is displayed.
4. On Network Device view click on any Network Device, the NETWORK DEVICE DETAILS pop-up is displayed.
5. Click on the ENVIRONMENTAL PARAMETER tab.

Now, under the ENVIRONMENTAL PARAMETER tab, WLC parameters are not reflecting.

Prerequisites:

1. Navigate to Admin > Advanced > Discovery and Monitoring > Discovery.
   The Discovery page is displayed.
2. Configure a job by selecting Repeat Job checkbox and specify 168 as hours next to Every text box.
3. Click Save.

The Information mentioned for Solution under Vendor Information tab is getting displayed in Solution column of Daily Incident Report instead of the information mentioned for Solution under General Tab.

Prerequisites:
Navigate to Reports > Incident > Daily Incident Report.

The Daily Incident Report is displayed.

Now, a new column Vendor Solution is provided in Daily Incident Report.

Hence, the Information mentioned for Solution under Vendor Information tab will be displayed in Vendor Solution column of Daily Incident Report.

And, the information mentioned for Solution under General tab will be displayed under Solution column of Daily Incident Report.

Prerequisites:

1. Create a new Discovery job
2. Click on submit
3. Open the same job and click on the Repeat Job checkbox
4. Provide time details and select the hours from the dropdown.
5. Click on submit.

Prerequisites:

MPLS (Multiprotocol Label Switching) links are basically ISP (Internet service provider) like Airtel, Reliance Tata etc.

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.  

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.

When a Service Request is linked in a Change Record, success message is not displayed, and the SR is not visible under Relationship tab. However, on accessing the SR, the CR is listed in relationship tab.

Prerequisite:

88794

Network link capacity must be in KBPS in Edit Network Topology & Network Device View.

Prerequisites:

Edit Network Topology:

1. Navigate to Operations -> Networks -> View -> Edit View
2. Select Tenant
3. Select Network from the list for the Draw View
4. Click on a link/Connector
5. Click on Modify & Edit Connector

Network Device View:

1. Navigate to Operations -> Views -> Network Device View.
2. Select the same Network from the tile view
3. Links and interfaces on the network will be displayed in a modal window.
4. Select the link used in the previous step
5. This will display the link details

87706

On the RELATIONSHIP pop-up, the Administrator was not able to view and link a change record to the cab meeting.

This issue occurred when the change Record Id and Cab Meeting ID were the same.

Note: You can view the cab meeting ids in the CM_Meeting_ID column of the CM_CAB_Meeting table.

The RELATIONSHIP pop-up can be accessed using Change > User > CAB Meeting > Select the required Tenant > Click the required Subject hyperlink > Click Link drop-down and select Change.

Now, the Administrator can view and link the change record to a cab meeting even though the Meeting Id and Change Record Id are the same.

87257

On the CR NO - CI Impact Summary notification e-mail, under the CI IMPACT SUMMARY section, the CIs that need to be updated were displayed as HTML tags.

Pre-requisites:

Click Change > User > New Change Record.

Enter all mandatory fields.

Link CIs.

Move the CR till closure.

Post closure, the CI Impact Summary notification e-mail Triggered.

Now, the CIs that need to be updated are displayed in table format with Host Name, Parent CI, and Impact Type.

86339

The values selected on the BULK UPDATE pop-up were not getting updated to Service Requests when the analyst update Service Requests through Bulk Update. But, the success message "SRs are updated" pop-up is displayed.

Bug Reproduction Steps:

Log into the Application as an Analyst.

Click Request > User > Manage Service Requests > Service Request List. The Service Request list page is displayed.

Select the SR IDs in In-Progress status and click BULK UPDATE on the ACTIONS panel. The BULK UPDATE pop-up is displayed.

Select the Status as Resolved and fill in the other mandatory fields.

Click Submit. The success message "SRs are updated" pop-up is displayed.

Pre-requisites:

Enable ' Enable Bulk Update Icon on List Page ' check box at Tenant Level configuration.

Scenario

This issue occurred only when the analyst updates the service requests from In-Progress to Resolved status through the Bulk Update.

Now, the values are getting updated and the status also updated to resolved.

88091

The e-mails sent to the o365 API mailbox were not converted to tickets.

Pre-requisites:

Configure o365 API mailbox.

Scenario

This issue occurred only when the e-mail body contains the keyword “src or SRC" and hyperlinks.

Navigation

The MAILBOX configuration page can be accessed using Admin > Advanced > Notifications > Mailbox.

Now, the e-mails are getting converted into tickets.

87067

Under the Non-Fixed Assets tab of the Asset History section, as error message “Oops! An error occurred.”  was displayed. Due to which user was not able to view the allocation history of the software.

NA

Now, the software allocation history is displayed without any error message.

86506

On the Change Record List report, “Oops! An error occurred.”  was displayed.

This issue occurred when the records were filtered for more than 90 days.

Now, the records are displayed without any error message.

87070

After creating an Incident using e-mail to ticket functionality, the respective e-mail was not attached to the newly created Incident.

This issue occurred when the subject length of the e-mail exceeded 200 characters.

Now, the respective e-mail is attached to the newly created Incident.

86950

On the Select User pop-up of the ANALYST page and the APPROVE SERVICE REQUEST page, while searching the Analyst/ Approver, the application was not searching the respective approver based on the specified e-mail id.

 NA

Now, the application loads the specified Analyst /Approver details as expected.

The background image that was added for network topology in the edit view was not displayed in the Network view of the cloud environment.

NA

Now, the background image that is added for network topology in the edit view is displayed in the Network view of the cloud environment.

88797

While updating a detail on the CHANGE RECORD ID page, the SUBMIT button was disabled and the Analyst was not able to update the detail.

NA

Now, the analyst can update the change record details.

88548

Under the New Value column of the CHANGE HISTORY page of the CONFIGURATION ID page, the Installation Date was showing the wrong value.

This issue occurred when the Analyst had cleared the Installation Date while editing the CI ID.

Now, under the New Value column of the CHANGE HISTORY page, correct value is shown based on the Installation Date.

86485

The Category ID was not available in the WO_RPT_DN_WorkOrderMaster table but available in the transaction table.

NA

New column [Category_ID] has been added in the WO_RPT_DN_WorkOrderMaster table.

88185

On the Problem Details page, when the user selects the value in the Parent custom attribute drop-down field, the mapped child values were not loading in the Child drop-down field.

NA

Now, the mapped child values are loaded in the Child drop-down field when the user selects the value in the Parent drop-down field.

88086

On the Problem Details page, the Custom Attribute section fields were displayed in a single column even if the No. of Columns value was selected as 2 in the Form Builder under Properties panel for a Group control.

NA

Now, the Custom Attribute section fields are displayed based on the No. of columns selected in the Form Builder.

87934

When the user selects the problem records from Global Search results, the ticket leads to the New Problem Record page instead of the Problem Record Details page.

NA

Now, the ticket leads to the Problem Record Details page successfully when user selects the ticket from the Global search record results.

87480

When the user provides the data and submits it under the Custom Attribute tab fields on the Customer Details page, the alignment issue occurred.

This issue occurs if the Custom Attribute tab had more than 15 fields on the Customer Details page.

Now, the alignment issue doesn’t occur, even if the Custom Attribute tab has more than 15 fields on the Customer Details page.

90218

The IM_GetUpdatedIncidentDetails API was not working as expected.

When the user passes the interval, the API response was rendering only the latest first incident instead of rendering all incidents logged and updated within the specified time interval.

Now, the API is working as expected and rendering all the incidents logged and updated within the specified time interval.

88548

Under the New Value column of the CHANGE HISTORY page of the CONFIGURATION ID page, the Installation Date was showing the wrong value.

This issue occurred when the Analyst had cleared the Installation Date while editing the CI ID.

Now, under the New Value column of the CHANGE HISTORY page, correct value is shown based on the Installation Date.

On the Incident > New Incident page:

•  If a user entered an incident id into the Incident ID field on the COPY INCIDENT window and click the SUBMIT button.

OR

• If a user select an incident from the Select from Recent 50 Incident drop-down field on the COPY INCIDENT window.

In both these scenarios the user encountered an error message.

This issue occurs if a user enters or select an Incident ID of an incident which is logged for a workgroup for which Show on Log New Incident Page checkbox is not enabled.

Customer unable to view the links when devices added from discovery.

Access: Operations > Networks > Create View/Edit View > Add New.

In the Edit View page, if a user manually links two new devices that were added separately from discovery, the links are not getting saved on the submission of the request.

86927

The status column of Change Record List appeared as:

Now, the following changes applied to the status column:

1. The pre-configured status text is center aligned.
2. The custom status background box changed to general oval shape.

On the User ID page, when updating the user details the Manager field was displayed blank.

Note: When the Employee ID, E-mail ID, and Manager NT ID have null value then Manager field appearing blank.

Now, when updating the user details if the Manager field is blank, it is displaying previous manager details.

The notification e-mail is not triggering for the configured users after the User Selectable approver approves the CR.

This issue occurs only the User Selectable approver approves the CR.

Prerequisite