Customer Fixed Issues and Known Issues Tahoe SP5 HF06

Owned by Enterprise IT
May 08, 2024
3 min read

 | 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

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 HF06:

Customer Fixed Issues 

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

Service Management

Issue ID

Issue Description

Scenario

Resolution

131710

The Resolution OLA was not getting calculated properly as per the holiday configured in Workorder Details page.

Prerequisites:

  1. Create a catalog without any approval level and publish it.

  2. Configure Work Order catalog mapping for the above created catalog.

  3. While configuring SLA service window, select the logged in user's location in Location field and set it as default. Click Save to save it.

  4. Configure a Priority with 240 minutes in Response SLA In Minutes field and 1500 minutes in Resolution SLA In Minutes field and set it as default. Click Submit.

Steps:

  1. Raise an SR for configured catalog (Log Service Request page).

  2. Configure the holiday for the location configured in SLA Service Window Details

  3. Reopen the raised SR ID in Service Request List page and navigate into work order page and click submit. In Work order page, verify if the Resolution SLA Deadline is calculating properly as per the configured holiday.

  4. Verify the Resolution OLA.

The Resolution OLA is getting calculated properly as per the holiday configured in Workorder Details page.

130353

Though the Email notification template was enabled for Finance connect Tenant in Service Request module, the notification template was not seen.

Steps: 

1.  Create a User with Super Admin role.

2.  Create a Tenant with only Service Request and SC Module configured.

3. Log in to the application with the User created in Step1.

4. Navigate to Admin > Notification Template

5. Verify if the Tenant created in Step 2 is visible in Notification template page.  

This issue is fixed, and the Tenant created is displayed in Notification Template list.

128208

The Requestor and Logged by parameters not working for Create new SR API Payload.

Steps:

  1. Log an SR using API ‘SR_LogServiceRequestCatalog’.

  2. Navigate to Manage Service Requests > Service Request List.

  3. Select the SR logged via API and check SR details.

The Requestor and Logged by parameters are successfully getting displayed.

Platform

Issue IDIssue DescriptionScenarioResolution
129384Even though the requests created from API and specific to Service Request module (Work Orders) were not assigned to any user, still a random user name was reflecting in the Assigned To field.

Steps:
1.     Create a Work Order from API.
The API request is added below:

 Request

{

    "ServiceName": "WO_CreateORUpdateWorkOrder",

    "objCommonParameters": {

        "_ProxyDetails": {

            "AuthType": "APIKey",

            "OrgID": "1",

            "APIKey": "6CE2tl6ochPHQbVVVHlM1XJlcqjOm+NB/M5KNLFpopo=",

            "ProxyID": 0,

            "UserName": "",

            "Password": "",

            "ReturnType": "JSON"

        },

        "oWorkorderParam": {

            "IsWebServiceRequest": true,

            "LoggedAnalystEmailID": manasa.mahesh@symphonysummit.com,

            "_Sup_Function": "Info",

            "_Status": "New",

            "Module": "SR",

            "ModuleTicketNumber": "4229",

            "_Classification_Name": "SR 1 Classification",

            "Priority_Name": "P1",

            "_Assigned_WorkGroup_Name": "IT Addintional Owner",

            "Symptom": "Testing workorder via API",

            "_Description": "Testing workorder via API desc.",

            "CustomFields": []

        }

    }

}


 Response

Response:

{

    "Errors": "",

    "Input": null,

    "Message": "Successfully WorkOrder Added : WO1026",

    "OrgID": 0,

    "Output": null,

    "OutputID": 0,

    "OutputObject": null,

    "TokenID": "48A253CA63AD9FDECFA1C8E52D17A0C404B45749E3FC581D92D881AFD5FA4354D8812A8AB6373599077FFD5AE95AA4C0E302B58AC447DC6924DCED5AC26D265658FD8559F18689C2AA5DEE99F83D614ADB51EFE799C7D483DA9E802898F03EC52027CE686629F1652264FD3A733344B0B072CD19456E75B3FF2913C2291AC59F072B8A382DB4C3C7EF83C03FC783F36E53E7F02552489ED5142025194D9A397FADA29A91C46A8DDB7BF699934180C1AD",

    "TicketID_Encrypted": null,

    "TicketID_Internal": 3033,

    "TicketNo": 1026

}

This issue is now fixed, and New Requests / Work Orders don’t get a random user assigned.

Agentless Discovery

Issue ID

Issue Description

Scenario

Resolution

131710

Discovery was not working as email ID was not present for the user. 

  1. Configure a Discovery job for user.   
     
  2. Run the Discovery job and verify if it is functioning correctly. 
     
  3. Navigate to Discovery > List. The List page displays the Status of the Discovery Job appropriately. 

Note: The user initiating the Discovery job must provide an active Email ID to receive notifications.

Discovery works appropriately after the resolution.