Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Download Release Notes | Previous Versions: << Sierra << Sierra HF01 << Sierra SP1 << Sierra SP1 HF01 << Sierra SP1 HF02 << Sierra SP1 HF03 << Denali << Denali HF01 << Denali HF02 << Denali SP1 << Denali SP1 HF01 << Denali SP1 HF02 << Denali SP1 HF03 << Denali SP1 HF04

What's New? | Customer Fixed Issues and Known Issues | Prerequisites | Installation, Configuration, and Upgrade | Security Best Practices for SummitAI Application Deployment

On this page: Customer Fixed Issues | Known Issues 

Customer Fixed Issues 

This section describes the issues reported by the customers and their fixes in Denali SP1 HF05. 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.

#IssueResolution

79473 

 

An error message ‘’Oops! An error occurred“ was displayed while configuring the auto creation settings of Problem Record from the AUTO CREATION SETTINGS page. This Issues was occurring when there was no active Risk configured.

Now, the Administrator can configure the auto creation settings of Problem Record without any error message even when there is no active Risk configured. 

80391

On the Incident Details page, the Workgroup entry records were not captured at the Change History pop-up and Audit Log pop-up when the analyst changes the workgroup.

Now, the Workgroup name is captured on the Change History pop-up and Audit Log pop-up.

79047

While logging an Incident using SummitAI Web App, the image(s) that was copied and pasted in the Description field was not displayed on the Incident Details page for the end user. However, all such images were displayed on the Incident Details page for the Analyst.

Now, the image(s) that is copied and pasted in the Description field while logging an Incident is displayed successfully on the Incident Details page for the end user.

79548

While configuring reasons on the REASON page for the Knowledge Record, the application was not allowing space character. Due to this, words were not separated, and user had to use special character such (-) minus symbol to separate two values.

Now, the application is allowing space character while configuring the reason.

80525

An error “Oops! An error occurred.” was displayed on the KR STATUS REPORT page.

Now, the issue is fixed, and no error is displayed on the KR STATUS REPORT page.

79575

After raising a new Service Request with the description specified in the Thai language, the Description field on the SR DETAILS page of the respective SR was displaying junk characters instead of Thai language.

Now, the Description fields displays the specified language on the SR DETAILS page.

80916

 

Prerequisite:

  1. Login as analyst having access to few workgroups.
  2. Problem record status should be In Progress status.

The In Progress status was not displayed on the PROBLEM RECORD details page. This issue was occurring when Logged in reviewer or approver was not having Analyst access.

Now, the In Progress status is displayed on the PROBLEM RECORD details page even when the logged in reviewer or approver is not having Analyst access.

 

80526

On the New Incident for User page, the Expand option was not working for the Diagnostic Details and OLA Details section on the Additional Information tab once it is collapsed.

Now the Expand option works for the Diagnostic Details and OLA Details section on the Additional Information tab of the New Incident for User page.

80487

Gamifications points for the various incident parameters such as Response Time, Resolution Time, and so on were not getting added. As a result, under the My Action Item History tab of the Analyst Dashboard, the grand total of Gamification points was displayed incorrectly. This issue was occurred even though the Gamification point configuration was done for all the parameters and the Gamification -Schedule Action Items job was running successfully.

Now, Gamification points for all the incident parameters are displayed based on the configuration. Accordingly, the total Gamification Points are shown on the My Action Item History tab of the Analyst Dashboard.

80045

On the NEW KNOWLEDGE RECORD page, while adding the screenshot in the Answer field, the ACTIONS panel of the page was compressed. Due to this, the page orientation was changed, and the action items were not completely visible.

Now, the ACTIONS panel is not getting compressed upon adding a screenshot in the Answer field.

79899

While extending the Service Validity of an SR and submitting, the pre-uploaded attachment was disappeared, and the Application displayed the validation message to upload the attachment.

Now, the User can successfully extend and submit the Service Validity of an SR along with the pre-uploaded attachment.

80350

Unable to approve the Service Request. This issue was occurred while approving the Service Request on the APPROVE SERVICE REQUEST page, the page was not auto scrolled to display the unspecified mandatory fields.

Now, the page is auto scrolled to display the unspecified mandatory fields, and the Approver can approve the Service Request.

80971

On the Incident SLA BY WORKGROUP Report, the data displayed on the Incident List pop-up was based on the Resolution Time, but the table section was named as TOTAL INCIDENT LOGGED BETWEEN < DATE> AND <DATE>

Now, the table is renamed as TOTAL INCIDENT RESOLVED BETWEEN < DATE> AND <DATE>.

81197

The user was not able to submit the CR after specifying the required details on the NEW CHANGE RECORD page. This issue was occurring when the user had entered the data within the double curly braces {{ }}

in any of the text fields (including custom attributes).

Now, the user can submit the CR after specifying the required details within the double curly braces {{ }} on the NEW CHANGE RECORD page.

81180

Network Interface Utilization displayed incorrect data under the UTILIZATION tab of the Network Interface Details pop-up page.

Now, the correct data is displaying for the Network Interface Utilization under the UTILIZATION tab of the Network Interface Details pop-up page.

81360

E-mail Notifications were not triggered for the IT Operations Management module.

Now, the E-mail notifications are triggering for the IT Operations Management module.

81361

All the available devices in an Infrastructure were not displayed on the NETWORK UTILIZATION (%) REPORT page. This issue was occurring when the utilization value of the Network Device was null.

Now, the NETWORK UTILIZATION (%) REPORT page is displaying all the available Network Devices in an Infrastructure.

80509

On the INCIDENT LIST page, the Incidents that belong to other Workgroups (i.e., the workgroup in which the logged Analyst was not having access) were not displayed. This issue occurred even though on the FILTERS pop-up, the respective Workgroup was selected, and the View All Incidents check box was enabled.

Now, on the INCIDENT LIST page, the Incidents that belong to other Workgroups (i.e., the workgroup in which the logged Analyst was not having access) are successfully displayed.

76898

The scheduled Izenda Report was not triggered when the TLS 1.2 was enabled.

Now the scheduled Izenda Report is triggering since the Izenda version 6.11.0.0 is supported for TLS 1.2, TLS 1.1, and TLS 1.0.

Known Issues 

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

Issue

On the SEARCH ASSET page (ASSET > USER > MANAGE ASSETS > ASSET INVENTORY page > Click Non-Fixed Asset icon (Consumable, Accessories, or Software) > Click Search Asset icon), an error message "Oops! An error occurred" was displayed when the length of the specified search text is more than 30 characters. This issue exists for the following scenarios:

  • When in the search text field, a relational operator i.e., <, >, <=, or >= is specified to search Assets.
  • When the user tries to search Non-Fixed Asset.

(#73532)

When the Maker-Checker configuration is enabled for the Allocate action and Maker-Checker approval matrix is configured with two levels of approval, on sending the Allocated Assets for Checker’s approval, the following issues are observed:

  • On the FIXED ASSET page (Asset > User > Manage Asset > Asset Inventory > Click the FIXED icon under the SELECT THE ASSET TYPE section > Click FILTERS on the ACTIONS panel > Select Status as Allocated and provide data in all the other fields > click SUBMIT), duplicate Assets are displayed after the Checker approves the Assets sent for approval.
  • The Assets do not move to the second level of approval after the Assets are approved by the first level of Approver.

Prerequisites

  1. Enable Maker-checker approval for Asset Allocate transaction. (Admin> Basic > Infrastructure > Tenant > Click Filters on the ACTION panel and select the Domain and click SUMBIT > On the TENANT page under the LIST section, select the Tenant for which you want to enable Maker Checker > Click CONFIGURE DETAILS on the ACTIONS panel > Click Asset Management under the MODULES section > select the check box of Enable Maker-Checker > Select Actions for Maker-Checker to Approve as  Allocate > Select the End Time value and click SUBMIT).
  2. Configure No. of Approval level as 2 on the APPROVAL MATRIX page (Asset> Configuration > Others > Approval Matrix > On the ACTIONS panel, click ADD NEW > Specify the details > click SUBMIT).
  3. Send Assets for approval for Allocate action (Asset > User > Manage Asset > Asset Inventory > On the ASSET INVENTORY page, under the SELECT THE ASSET TYPE section, click FIXED > Select the same Tenant for which the Maker-checker is enabled >  Click the In-Store hyperlink of the required Asset Category > Select the check box corresponding to the Asset you want to allocate > On the ACTIONS panel, click ALLOCATE > Specify the mandatory details to allocate the Asset and click SUBMIT).

Bug Reproduction Steps:

  1. Login to the Application as Checker.
  2. Click Asset > User > Manage Asset > Approvals Maker-checker Approval > Click Filters on the ACTIONS panel.
  3. On the Filter pop-up page, select the Tenant and specify the required details.
  4. Select the Assets that you want to approve and click APPROVE icon on the ACTIONS The APPROVE pop-up page is displayed.
  5. On the APPROVE pop-up page, select the Approval Status as Approved to approve the Asset and click
  6. Click Asset > User > Manage Asset > Asset Inventory > Click FIXED under the SELECT THE ASSET TYPE section > Click Filters on the ACTIONS
  7. On the Filters pop-up page, select the Tenant, Select the Status as Allocated and specify required details.
  8. Click SUBMIT.
  9. Validate the data.
(#72171)

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).

  • No labels