Customer Fixed Issues and Known Issues Tahoe SP3 HF14

Customer Fixed Issues and Known Issues Tahoe SP3 HF14

 

On this page: Customer Fixed Issues | Known Issues 

Merged Releases

Following are the merged releases in Tahoe SP3 HF14:

Customer Fixed Issues 

This section describes the issues reported by the customers and their fixes in Tahoe SP3 HF14 version.

Service Management

Issue ID

Issue Description

Scenario

Resolution

129941

In Service Request Module, while filtering, user was unable to see the cases in the Service Request List page for the previous month.

Steps:



  1. Navigate to Request > User > Manage Service Requests > Service Request


  2. Click FILTERS and filter the requests from the Last month.


  3. Verify if the previous month Service Requests are displayed. 

In Service Request Module, users can filter out the cases for the previous months.

130169

For a newly created Category in a new problem record, the Category field mapped to a specific customer was not getting displayed

Pre-requisite:



  1. Login to the Summit Application > Navigate to Incident > Configuration > Incident Masters > Category > Configure a Category.


  2. Right click the newly created Category > click Configure > In the Popup, map the Category with the specific Customer > click SUBMIT.


  3. Add a new user to the same Customer for which the Category is mapped > Provide Analyst access to the new user.  



Steps:



  1. Login to the Summit Application with the newly created credentials.


  2. Navigate to Problem > User > New Problem Record > click the Category Search Icon > Category tree opens.


  3. Verify whether the Category created and mapped with specific customer is displayed in the category tree. 




For a newly created Category in a new problem record, the Category field mapped to a specific customer is getting displayed.

130209

When a Change Record (CR) was updated from Initial Authorization to Approved status the update was not getting displayed in the CHANGE HISTORY.

Pre-requisite:

 

  1. Dynamic Approval Workflow should be configured.

 

Steps:



  1. Select Change > User > Approve Change Records. The APPROVE CHANGE RECORDS page is displayed.


  2. Click the CR NOof the CR that you want to Approve. The CHANGE RECORD ID page is displayed.


  3. On the CHANGE RECORD IDpage, click APPROVAL icon on the ACTIONS


  4. On the APPROVALpop-up page, select the approval status from the list as Yes.  Specify your remarks and click SUBMIT to approve the CR.


  5. Click on CHANGE HISTORY under



Verify the CR approved update status. 

The Change Record approval status is getting displayed as desired in CHANGE HISTORY

128386

Post upgrading to Tahoe SP3 on the Reachability of SD team report and the Incident Customer CSAT Report, the graphical representation was not working as expected. 

Steps:



  1. Navigate to Reports > Select Incident Management.


  2. In the REPORTS dropdown select Reachability of SD team. Verify if the report and the graphical data is displayed.


  3. In the REPORTS dropdown select Incident Customer CSAT Verify if the graphical data is displayed and click on the graphs to display the records.



In the Reachability of SD team report and the Incident Customer CSAT Report, the graphical representation is working as desired.

127068

The ' SR ID - Reminder! Expiry Period Alert ' e-mails were not getting triggered.

Prerequisites:

 

  1. Insert the record into Summit_SAASUrlConfig table.


  2. While creating a catalog select the Enable Service Validity checkbox and enter the number of days in default To date , Maximum duration. Click Save and publish the catalog.


  3. Raise an SR.


  4. Configure SR Extend for Service Validity job in custom scheduler.

Steps:

  1. Navigate to Request > Service Request List. The Service Request Page is displayed.


  2. Click on SR ID and the Service Request Details page is displayed.


  3. Resolve the ticket.


  4. Once SR Extend for Service Validity job completes, verify for ' SR ID - Reminder! Expiry Period Alert ' e-mails.



The ' SR ID - Reminder! Expiry Period Alert ' e-mails are getting triggered.

129241

In the Service Request notification emails under User, the Customer Name and designation values were not reflecting.

Pre-requisite:

  1. A Notification Template named ‘Service Request Assigned’ should be present in Notification Template

Steps:

  1. Navigate to Request > User > New Service Request. NEW SERVICE REQUEST page is displayed.


  2. Enter the mandatory details and click SUBMIT.


  3. In the notification email, verify whether the Customer and Designation field values are reflecting. 

In the Service Request notification emails under User, the Customer Name and designation values are reflecting as desired.

130545

In the email notification triggered for the creation of the Workorder, the keywords were displayed in the email template instead of the actual information.

 Steps:



  1. Log in to the Summit Application.


  2. Navigate to Incident > User > New Incident.


  3. Enter the required details and click Submit.


  4. In the RELATIONALSHIP tab, create a Work Order. 

The email notification triggered for the creation of the WorkOrder displays the appropriate information as design.



126849

The system was displayed Opps Error on opening the Incident SLA by Workgroup Report

Steps:

  1. Navigate to Reports > Tenant > Select the module as Incident Management.


  2. Select Incident SLA by Workgroup Report under Reports drop-down. 

The system is not displaying Opps Error on opening the Incident SLA by Workgroup Report.

130766

The Workgroup and Owner fields were getting displayed as mandatory fields but not editable in Test Completion stage.



Steps

  1. Navigate to Release > User > Release Record List. The Release Record List page is displayed.


  2. Click RR ID hyperlink. The Release Record ID details page is displayed. Navigate to Test tab. Select Test Stage as Test Completion.

The Workgroup and Owner fields are editable in Test Completion stage.

128955 / 123590

When the  IM_MasterReport was exported using Advance CSV with date filter option, incident details were not getting displayed.

Steps:

  1. Navigate to Application > Report >Incident Management > IM_MasterReport.


  2. Filter the date.


  3. Click Export to Advanced CSV.



Advance CSV option works appropriately after the resolution.

128955

The status of SR was not getting changed from Pending to In Progress.

Steps:

  1. Log in to Application.


  2. Raise a Service Request as an End User.


  3. Log in as an Analyst and keep the SR in Pending status.


  4. Log in as an End User and reply to SR under Pending status through the mail.


  5. Check the status of the SR.



SR status changes from Pending to In Progress and is working appropriately in all related attributes.

121021

Chinese special characters were causing line break issues.

Prerequisite:

The report should contain Chinese characters in the report.


Steps:

  1. Navigate to the Reports page with Japanese as the user language.


  2. From the drop-down list, select Izenda 6 report


  3. Click the Export icon. 


  4. Click New Option Advanced CSV


  5. Check browser download.


  6. Validate if Chinese characters are not causing line break issues.



Reports Detail page displays appropriately after the resolution.

130474

There was an issue with the filter dropdown search option on the list page.

 Steps:

  1. Navigate to the List page of the required module.


  2. Validate that the list pages should have the dropdown working with auto-complete features on. 

The filter drop-down search option is working with auto-complete features after the resolution.

124673

When the status was changed it was not displayed properly in the RM Deployment tab.

Steps:

  1. Navigate to Release > User > Release Record List.


  2. Open Release Record which is in build/test status.

  3. Change status to deploy, fill in other mandatory details, and Submit.

  4. Go to the Deployment tab and verify the Deployment status.