1_Customer Fixed Issues and Known Issues Tahoe SP6

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 SP5

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

In this page: Customer Fixed Issues | Known Issues 

Merged Releases

Following are the merged releases in Tahoe SP6: 


Known Issues 

This section describes the known issues detected by the Summit Dev and QA team in the release, Tahoe SP6 Release.

Issue ID

Issue Description

Scenario

Workaround

117165

In the Mozilla Firefox browser, the appearance of the scroll bar on any configuration pages in the Change Management module is not proportionate to the page size.  

 Steps:

  1. Log in to Summit Application on the Mozilla Firefox browser.  

  2. Navigate to Change > Configuration. Click any page under configuration. 

  3. Verify the scroll bar under Tenant* 

Screenshot for Reference

Log in to the Summit application either on Chrome or Microsoft Edge browsers.  

119073

Under Incident Management Module, on the Log Incident page, the delink option is displayed on the Local configurations in the Local Tenant.  

Prerequisites: 

  1. A Local Log Incident page configuration should be present in Local Tenant 

Steps: 

  1. Log in to Summit Application.
     
  2. Navigate to Incident > Configuration > Incident Masters > Log Incident Page.  

  3. Select any Local tenant and open any Local configuration.  

  4. The Delink option should not be visible.  

NA

111780

On the Auto Escalation page, while adding a new configuration, the values of the previous record are displayed.  

Prerequisites: 

Auto Escalation configuration should pre-exist by selecting “All” for the following fields workgroups, locations, customers, and priorities.  

Steps: 

  1. Navigate to Admin > Advanced > Productivity > Escalations > Auto Escalation. 

  2. Select any Tenant. 

  3. Under the Actions Panel, click Add New. 

NA

118909

Scenario 1: 

Under Incident Management Module, on the Log Incident page, in any Local tenant, the Customer* and Attribute by Rule are disabled.  

Scenario 2: 

On the Log Incident page, in any Local tenant, along with the Customer*, Attribute by Rule, and all the other fields on the page are disabled. 

Steps: 

  1. Log in to Summit Application. 

  2. Navigate to Incident > Configuration > Incident Masters > Log Incident Page.  

  3. Select any Local tenant. 

  4. Click ADD NEW from the ACTIONS panel.  

  5. Verify Customer*,Attribute By Rule and all the other fields on the page. 

NA

118813

  1. Customer field was enabled in Local Tenant for Global Configuration.

  2. Globally configured Attribute by Rule value was not getting retained in Local Tenant.  

 Steps:

  1. Log in to Summit Application.  

  2. Navigate to Incident >Incident Masters > Log Incident Page.

  3. Select any Local Tenant.

  4. Access any Global Value by clicking on Customer Name.

  5. Verify if the Attribute by Rule value is reflecting correctly.

  6. Click on Customer dropdown to verify if it is disabled.  

NA 

119270

For the Incident Module,  Global Value (Labels) are editable in Local Tenants.

Prerequisites:


Global values should be configured by Attribute by Role in the global tenant.

Steps:

  1. Log in to Summit Application.

  2. Navigate to Incident > Configuration > Incident Masters > Log Incident Page.

  3. Select Local Tenant from the Tenant List.

  4. On the Actions Panel, click Show List.

  5. Select Customer Name from Global Tenant.

  6. Verify the Labels.

NA

118786

Upon searching Global Rules names on the Dashboard, they are repeating. Not prefixed / Suffixed with Tenant Name. 

Prerequisites:

Global Rule should be configured.

Steps:

  1. Navigate to Dashboard.

  2. Enter the Global rule in the search bar.

  3. Validate the Global Rule Names.

NA

119368

In Local Tenant, multiple workflows were existing for the same properties when the user created a Global Workflow with different Change Category values. However, the Change Category option was disabled for local tenants.

Note: The issue is happening if the Change Category is disabled for few Tenants at the Tenant Level Configuration.  

Steps:

  1. Navigate to Admin > Workflow > Change Management.

  2. Select the Category as ‘Large’ > Owner Workgroup as ‘IT Infra’ > Change Category as ‘ALL’.

  3. Select the Tenant as GLOBAL TENANT and create a Workflow by selecting Category as ‘Large’ > Change Type as Normal > Owner Workgroup as ‘IT Infra’ > Change Category as ‘TestCat’.

  4. Select any Local Tenant.

  5. Verify if the Change Category is enabled at Local Tenant.


NA 

119611

Unable to open the Workflow, displays as "Processing" and user experiences console error. Hence, the globally configured workflows are not replicating as expected.

Steps:

  1. Navigate to Admin > Workflow > Change Management. 

  2. Select Global Tenant. 
  3. Click + icon, Create a new Workflow. 
  4. Enter the required details and click Save.

  5. Drag and drop the Activities such as Approval, Conditions, and Notification.

  6. Click Submit.

  7. Validate the newly created Workflow. 


NA