Customer Fixed Issues and Known Issues Tahoe SP5 HF03

On this page: Customer Fixed Issues | Known Issues 

Hotfix Merges

Following are the merged releases in Tahoe SP5 HF03:

Customer Fixed Issues 

This section provides details about the fixed customer issues in following modules.

Service Management 

Issue IDIssue DescriptionScenarioResolution
121802

In Vendor Information the Resolution Deadline was not getting calculated based on the Priority.

Prerequisites:

  1. Create Underpinning Contract Specification (SLA > Underpinning Contract) and define SLA Service Window name under Actions > Service Timings. 

  2. Publish the specification and create Underpinning Contract Agreement. 

Steps: 

  1. Navigate to Incident > Manage Incidents > Incident List. The Incident list page is displayed.

  2. Click on the Incident ID hyperlink. The Incident details page is displayed. Navigate to Vendor Information tab.

  3. Select the vendor for which Underpinning Contract Agreement. 

  4. Select the Service Name and verify Underpinning Contract dropdown. 

  5. Select the priorities configured in Underpinning Contract Agreement. 

  6. Select Status and Start Date.

In Vendor Information the Resolution Deadline is getting calculated based on the Priority.

124059

The duplicate 5 Why Problem statement was allowed under 5Why Work Area section.

Prerequisites: 

  1. Navigate to Root Cause Analysis. Select Methodology as 5 Why Analysis under RCA Methodology

  2. Under 5 – Why – Work Area, add multiple statements (let’s consider 3) using + symbol.

  3. Modify the second Why statement.

  4. Specify the 5why reasons for the1st and the 3rd statement, and don't specify the reason for the 2nd statement. Click Submit.


The duplicate 5 Why Problem statement is not allowed under 5Why Work Area section. 

126204

The same custom attribute updation was captured twice in the change history only for Auto created CR.

Precondition:

  1. Custom attributes should be configured for the CM module at the desired tenant.

  2. CR template should be saved for configured custom attributes.

  3. Catalog to change mapping should be configured for the desired tenant & the recently saved CR template which includes custom attributes should be mapped.

  4. CR Auto Create from the SR job should be running.


Steps:

  1. Navigate to Request > User > Manage Service Request > New Service Request for User.

  2. Select Department.

  3. Enter the details in the required fields that match with the Catalog to Change Mapping configuration.

  4. Click Submit.

  5. Navigate to Request > User > Manage Service Request > Service Request List.

  6. Click on SR ID.

  7. Click Relationship tab.

  8. Click on auto created CR-ID.

  9. Navigate to the custom group & update the custom field and submit the CR.

  10. Click on Change History & verify the updated custom field.

The same custom attribute updation is captured properly in the change history only for Auto created CR.

Fixed 502 Bad Gateway issue in Azure utilities related to SQL sessions.