Customer Fixed Issues and Known Issues Tahoe SP5 HF09

Owned by Enterprise IT
May 08, 2024

 | Previous Versions: << Sierra << Sierra HF01 << Sierra SP1 << Sierra SP1 HF01 << Sierra SP1 HF02 << Sierra SP1 HF03 << Denali << Denali HF01 << Denali HF02 << Denali HF03 << Denali SP1 << Denali SP1 HF01 << Tahoe << Tahoe SP1 << Tahoe SP3 HF01 << Tahoe SP3 HF01 (v1) << Tahoe SP3 HF02<< Tahoe SP3 HF03 << Tahoe SP4 << Tahoe SP5 << Tahoe SP5 HF01 << Tahoe SP5 HF02 << Tahoe SP5 HF03  << Tahoe SP5 HF04 << Tahoe SP5 HF05 << Tahoe SP5 HF06  << Tahoe SP5 HF07 << Tahoe SP5 HF08


What's New? | Customer Fixed Issues and Known Issues | Prerequisites | Installation, Configuration, and Upgrade

On this page: Customer Fixed Issues | Known Issues 

Hotfix Merges

Following are the merged releases in Tahoe SP5 HF09:

Customer Fixed Issues 

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

Service Management

Issue ID

Issue Description

Scenario

Resolution

137173

Resolution Deadline SLA was getting changed for the cancelled tickets whose status were changed from ‘Pending’ to ‘Cancelled’.

Steps:

  1. Enable Convert to Service Request auto cancel Incident in the tenant.

  2. Keep the Incident in pending.

  3. Convert the Incident to Service Request. Incident will get auto cancelled.

  4. Check the Resolution Deadline SLA.

The Resolution Deadline SLA was not changing in the Incident detail page.

135863

SR was going to EA approval (Level 2) even though it did not meet any of the EA conditions after re-estimation.

Prerequisites:

Set the following Approval condition:

  • Level 1 - RFC Coordinators

  • Level 2 - EA Approval (If cost is more than 150 K AED OR Is New Technology is 'Yes' OR IS Application Change 'Yes')

  • Level 3 - BU FM

Steps:

  1. Log a SR for App Skip Catalog. Approval request sent to RFC Coordinators user group.

  2. User from RFC Coordinators user group forward this SR to another user.

  3. User enters Total One- Time Cost value as 150000 and selects is Application Change and is new technology as YES. Now, as per configured Workflow condition, the next approval is EU Approval.

  4. If the User from EU Approval is not fine with Total One- Time Cost value, so refers back the SR to the RFC Coordinators user group. RFC Coordinators group will again forward the SR to User.

  5. Users change the Total One- Time Cost value to 130000 and approve the SR.

Approval list shows properly after the condition change.

131803

When an auto Workorder was created from Service Request approval through Mail approval, Workorder assigned notification was not getting triggered to the assigned Workgroup.

Steps:

  1. Login to the application.

  2. Log a Service Request with at least one approval. The approval should have an auto Workorder configured with creation set to Immediate.

  3. Deactivate the email template to the caller.

  4. Approve the SR from mail.

While approving SR from mail, the Workorder email is successfully getting triggered to the assigned Workgroup.

Agentless Discovery

Issue ID

Issue Description

Scenario

Resolution

137978

 Flag based Extended SNMP Discovery was not working properly.

Prerequisites:
To enable the Flag based Discovery for SNMP machine, perform the following steps:

  1.   Configure SNMP machine and add key="IsSNMPExtendedInfoReq" value="True" /> for Device CDP Info, Interface Info, Net2Media Info, Dot1 Bridge Info and WLCA Access point to view the interface details after the Discovery.

  2.  To stop this Discovery partially, set Ping Retry as 99.

Steps:

  1. Select Admin > Advanced > Discovery & Monitoring > Discovery. 

  2. On the DISCOVERY page, click ADD NEW on the ACTIONS panel. 

  3. Select the Tenant and fill in the required details.  

  4. Select the SNMP check box and the SNMP version from drop-down list. 

  5. Specify the protocol details, as required in the fields. 

  6. Click SUBMIT. The Discovery details are configured. 

Flag based Extended SNMP Discovery works appropriately after the resolution.