Customer Fixed Issues and Known Issues Denali HF21

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 HF04 << Denali HF05 << Denali HF06 << Denali HF07 << Denali HF08 << Denali HF09 << Denali HF10 << Denali HF11 << Denali HF12 << DENALI HF13 << DENALI HF14 << Denali HF15 < Denali HF16 << Denali HF17 << Denali HF18 << Denali HF19 << Denali HF20

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


n this page: Merged Releases | Customer Fixed Issues | Known Issues 

Merged Releases

The bug fixes for the bugs found in the following version are also merged with this release. Please refer to the respective Release Notes for details.

Customer Fixed Issues 

This section describes the issues reported by the customers and their fixes in Denali HF21.

Platform

Issue IDIssue DescriptionScenarioResolution
108268 When a user click Scripting icon from the User ID page, even if the Tenant field was not present, a validation message, "Please select a Tenant," displayed.

Prerequisite:

  • Enable Scripting icon from the Tenant Configuration and Edit Profile pages.

Steps:

  1. Navigate to the Admin > Users > User ID.

  2. Select the Domain and Customer from the list.

  3. Click SUBMIT.

  4. Click User ID hyperlink and click Scripting Icon.
You can access the Scripting page without any errors. 

Asset Management 

Issue IDIssue DescriptionScenarioResolution
108124The Asset Reconciliation email alert notifications were not triggered for the end user to accept/reject the asset.

Prerequisites: 

  1. Log in to the SUMMIT application as an Admin. 
     
  2. The Fixed Asset Categories should be configured, and the Assets must be allocated to the End User. 
     
  3. Asset Reconciliation Alert should be enabled and running. 
     
  4. Asset Reconciliation Manager Alert should be enabled and Running. 
     
  5. The values in the 'Summit_SAASUrlConfig' should be as mentioned below 
  • Uid --> 1 
  • IsCustom --> 1 
  • CustomUrl --> *Custom Url may differs from customer to customer* 
  • Org_Id --> 1 
  • Active --> 1 
  • CustID--> 0 
  • IsProxy --> 0 
  • BaseUrl --> * (Custom URL may differ)

    Reconciliation Type should be configured for the required Tenant on Asset Reconciliation Configuration page. 

Steps: 

To configure the Asset Reconciliation action, perform the following steps: 

  1. Navigate to Asset > User > Manage Assets > Asset Inventory. 
     
  2. Select the Fixed Asset type on the Asset Inventory page. 
     
  3. Select the desired Tenant from the drop-down, which is a mandatory field. 
     
  4. Click the Filters icon from the right panel. 
     
  5. Select the desired Status and Category from the drop-down, which are mandatory fields. 
     
  6. Select the desired Asset Condition from the drop-down. 
    Click SUBMIT. 
     
  7. Select the desired asset checkbox and click the Reconciliation icon from the right ACTIONS panel. 
     
  8. Select the type of reconciliation from the Reconciliation Name drop-down, which is a mandatory field. 
    Click SUBMIT. 
     
  9. Verify the Summit_Email_Queue once the Asset Reconciliation job is completed. 
     

Log in to the Summit Application as an IT (Asset) Manager. 
 

  1. Navigate to Asset > User > Manage Assets > Approvals > Asset Reconciliation Approvals. 
     
  2. Click the Filters icon from the right panel. 
     
  3. Select the desired Tenant and Reportee values from the drop-down, which are mandatory fields. 
    Click SUBMIT. 
     
  4. Select the desired asset and approve. 
     
  5. Verify the Summit_Email_Queue once the Asset Reconciliation job is completed.

The Asset Reconciliation email alert notifications are triggered for the end user to accept/reject the asset after the resolution. 

 

Known Issues 

This section describes the known issues detected by the SummitAI Dev and QA team in the release, Denali HF21.

Issue

The GetBulletinBoard Mobile API request is used to retrieve Bulletin Board information. The User ID and Tenant Code are passed as the Request Parameters. In the API Response, instead of displaying the Bulletin Board information for the specific User ID and Tenant, the Bulletin Board information for all the Tenants is displayed. (#73031)

Prerequisites:

Configure Bulletin Boards for multiple Tenants.

Bug Reproduction Steps:

  1. Log into the Application as an Administrator.
  2. Configure a Bulletin Board. For more information, see Configuring Bulletins.
  3. Send a POST request for the GetBulletinBoard API. Pass Tenant Code, in the Instance parameter and User ID in the UserID parameter.
  4. Check API Response, instead of displaying the Bulletin Board information for the specific User ID and Tenant, the Bulletin Board information for all the Tenants is getting displayed.

On the ACTION DETAILS pop-up page, the Target ID is not showing in the Target column when Status of the Orchestration Workflow Script (other than the first Script) is In-Progress, and it is having Target Host Type mapped to From Previous Output value. However, the Target ID is displayed after the Script is executed successfully. (#73079)

Note: This issue is found in Incident Management, Work Order, and Service Request Management (SR) modules. Following bug reproduction steps are for the SR module:

Bug Reproduction Steps:

  1. Log into the Application as an Administrator.
  2. Select Admin > Advanced > Automation > Orchestration.
  3. On the WORKFLOW LIST page, click the NEW
  4. On the WORKFLOW CONFIGURATION pop-up page, select Module as Service Request, and specify other details to configure the Orchestration Workflow.
  5. Map the Target Host Type to From Previous Output value for the scripts of the Orchestration Workflow.
  6. Log out and log into the Application as an Administrator or as an Analyst.
  7. Select Request > Manage Service Requests > Service Request List.
  8. On the SERVICE REQUEST LIST page, specify the Filters and open an SR.
  9. On the SERVICE REQUEST DETAILS page, click the ORCHESTRATION tab.
  10. On the ORCHESTRATION tab, click the Script When the Script (other than the first Script) is in In Progress status, check the Target column details on the ACTION DETAILS pop-up page. The Target ID is not displaying in the Target column.
  11. After successful execution of the Script (other than the first Script), click the Script hyperlink. Check the Target column details on the ACTION DETAILS pop-up page. Now, the Target ID is displaying in the Target column.

The previous Asset transaction details are not displayed under the Previous Transaction drop-down list on the PREVIOUS IMPORT DETAILS page (Asset > User > Manage Assets > Import > Import Asset > Specify all the details > Click SUBMIT), even though the Assets are approved by the Checker on the MAKER-CHECKER ASSET-APPROVAL page (Asset > User > Manage Assets > Approvals > Maker Checker Approval > Click Filters  on the ACTIONS panel > Specify the filter criteria to view the list of requests from the Maker > Select the Assets that you want to approve under the LIST section > Click APPROVE on the ACTIONS panel > Select the  Approval Status as Approved.) This issue is found when the Asset Maker Checker Configurations is enabled.

(#67240)

When a user opens any page in a new tab in the SaaS Environment, the Switch Tenant pop-up is displayed in all the pages. This issue occurs only when the user is using the Firefox private window/tab. (#72276)

On the ADMIN DETAILS page (Admin > Advanced > Password Management > Administrator > Click ADD NEW on the ACTIONS panel > Specify all the details > Click SUBMIT > Select the Domain Name on the LIST page), the Password field is not displaying the GUID or Encrypted ID of the password and the field is empty. This issue is found when the user is logging into the SummitAI application using Microsoft Internet Explorer browser.

On the Incident Management FORM BUILDER page (Admin > FORM BUILDER > Select a Tenant > Select Module as Incident Management > Click Add on Actions panel> Select Display At as Additional Information or General Area or TFS Area > Click Next), when a user configures single Parent and multiple Child using Common Master, the collective values of both Child 1 and Child 2 are displayed in Child 1 and Child 2 drop-down lists.

On the Service Request Management FORM BUILDER page (Admin > FORM BUILDER > Select a Tenant > Select Module as Service Request > Click Add on Actions panel> Select Display At as Additional Information or General Area or TFS Area > Click Next), when a user configures single Parent and Multiple Child using Common Master, the collective values of both Child 1 and Child 2 are displayed in Child 1 and Child 2 drop-down lists.

The configured Bulletin Board (Admin > Advanced > Notifications > Bulletin Board > Select the Tenant > Click ADD NEW to configure the Bulletin details > Click SUBMIT) is displayed on the END USER DASHBOARD page even if the user does not have access to the selected Tenant and Domain.

Overlapping of content is observed on the Pagination bar of all the pages having high amount of data (typically in the range of 5 digits).

Broken image of the logo is displayed in the application when the logo image is deleted from the APPLICATION SETTINGS page (Admin > Basic > Infrastructure > Application Settings).

Workaround: The users need to re-login to the SummitAI application after deleting the logo.

On the AUTO-RESOLUTION SERVICE REQUEST CONFIGURATION and AUTO-RESOLUTION INCIDENT CONFIGURATION page (Admin > Basic > Infrastructure > Tenant > Select Domain > Select Tenant which is configured with Service Request/ Incident Management module > Click CONFIGURE DETAILS on the ACTIONS panel > Under the For End Users tab, select a reason form the Enable Reminder to Callers for Pending Reasons drop-down list > Enable Auto-Resolve Service Requests/ Auto-Resolve Incidents check box > Click Set Fields for Auto-Resolving Service Requests/ Set Fields for Auto-Resolving Incidents link), the users can set the auto-resolution criteria by specifying only white space (not numbers and alphabets) in the Response SLA Reason, Resolution SLA Reason, and Solution fields.

The following issues are observed in BI Custom Reports:

  • When a user downloads the report (in any format), the data is displayed with hyperlinks.

  • When a user places the mouse cursor on the count link, the tooltip is displayed as [Object Object].

  • In the exported report, report name is displayed with '+' instead of space.

The Change Record is not created when the CR Requester and Customer Approver are same. This issue occurs even though Do Not allow Customer Approval of CR check box is selected on the Change Management TENANT configuration page. This issue occurs only for the first time when the Tenant is configured.

Workaround: The Administrator needs to unselect and again select the Do Not allow Customer Approval of CR on the Change Management TENANT configuration page (Admin > Basic > Infrastructure > Tenant > Select the respective Tenant for which this issue is occurring > Click CONFIGURE DETAILS on the ACTIONS panel > Enable Do Not allow Customer Approval of CR check box and click SUBMIT > Clear Do Not allow Customer Approval of CR check box and then click SUBMIT, again).

The new SLA Value of an Incident is not displayed on the CHANGE HISTORY pop-up page (Incident > User > Manage Incidents > Incident List > Select the required Incident ID from the list > Click CHANGE HISTORY on the ACTIONS to view the change history of the selected Incident) when an incident is moved from New status to In-Progress using Notification Services.

The Pending Reason of an incident is still displayed on the CHANGE HISTORY pop-up page (Incident > User > Manage Incidents > Incident List > Select the required Incident ID from the list > Click CHANGE HISTORY on the ACTIONS to view the change history of the selected Incident), when an Orchestration Script fails and the respective Incident is moved back from Pending to In-Progress.

The notification e-mails related to escalation and jobs are triggered only in English language irrespective of the configured language on the NOTIFICATION TEMPLATE page for all the modules (Admin> Advanced> Notification> Notification Template> Select a Tenant > Click ADD NEW > Specify all the required fields > Click SUBMIT).