Versions Compared

Old Version 2

changes.mady.by.user Mayuresh Balaji Kamble

Saved on

compared with

New Version 3

changes.mady.by.user Shilpa K

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Scroll Exporter macro migration

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 HF03 << Denali HF04 << Denali HF05

Background Color
colorblue

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 

Scroll export button
scopecurrent
template-idc9a14909-8f27-452d-bca0-164bee1a9265
captionDownload this Page
add-onScroll PDF Exporter

Anchor
Customer Fixed Issues
Customer Fixed Issues
Customer Fixed Issues 

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

78536



When a Caller receives an SMS notification, the Logged Time in SMS Notification used to display the time is in Indian Standard Time (IST) Zone though the Caller’s Time Zone was a different one.

For example, if the Caller is in Malaysian Time Zone, the Logged time displayed in SMS is Indian time instead of displaying the Malaysian time.

Now, the Logged time is displayed based on the Caller’s time zone in the SMS notification.

77568


On the Global Search, the "Show All Incidents" and "Show All Service Requests" were not hyperlinked. Due to this, the user was not able to view all the Incidents or Service Requests for Incident and Service Request modules. 

Now, the "Show All Incidents" and "Show All Service Requests" are hyperlinked. Also, by clicking the "Show All Incidents" or "Show All Service Requests" hyperlink, the user can view all the Incidents or Service Requests.

77998


Prerequisites: Configure a Recurring Incident Job on the CUSTOM SCHEDULER page for a Tenant (Example: Information Technology).

Issue:

An error “Job option already exists!” was displayed when the Administrator tries configuring a Recurring Incident job for a different Tenant (Example: Facility). Due to this, the Administrator was not able to configure Recurring Incident Job for multiple Tenants.

Now, the Administrator can configure the Recurring Incident Job option for multiple Tenants without any error.

78818


The number of columns selected are 2 on the PROPERTIES panel when configuring the custom attribute fields on the FORM BUILDER page. But it is displayed in a single column under the Custom Attributes section on the Service Request List page.

Now, the custom attributes fields are displayed in 2 columns as per the configuration.

77686

The Special Character (?) was displayed instead of the Greek language characters in:
  • Request Description field on End User Service Request Details page (Request > My Service Requests > Click on the SR ID)
  • Description field on the Analyst Service Request Details page (Request > Manage Service Requests > Service Request List > Click on the SR ID)

Now, both fields are displaying Greek language characters entered by the End User.

78694


Prerequisites:

  1. Configure two User Types (Example: VVIP and VIP)
  2. Configure a user (James) under VVIP user type. Provide access to VIP user type to the user (James), using Configure additional User Type option.
  3. Create a catalog and provide access only to user type VIP.

Issue:

On the New Service Request page, an error "You do not have access to the catalog" was displayed when a user selects the catalog belonging to the additional user type.

Now, the user can raise Service Request by selecting the catalog belonging to the additional user type without any error.

79674

The following issues were observed after exporting an Asset to CMDB from the CMDB EXPORT page:

  • The Asset ID was not populated under the RELATIONSHIP tab of the respective CI Details page.
  • Similarly, the CI ID was not populated under the RELATIONSHIP tab of the respective Asset Details page.

The CMDB EXPORT page can be accessed using (Asset > User > Manage Asset > Asset Inventory > Select FIXED under the SELECT THE ASSET TYPE section > on the FILTERS pop-up, select the value for Status as CMDB Export and select the other required filter criteria > Click SUBMIT.

Now, the following issues are fixed related to the CMDB Export:

  • The Asset ID is linked and populated under the RELATIONSHIP tab of the respective CI Details page.
  • Similarly, the CI ID is linked and successfully populated under the RELATIONSHIP tab of the respective Asset Details page.

79677

The user was not able to complete the CMDB export process as a validation message, “Owner Name is mandatory” was displayed. This issue occurred when the Owner was configured as an AD import user (Frm_Uid value was blank in the User Master table).


Now, no validation message is not displayed, and the Asset is getting export to CMDB even though the Owner was configured as an AD import user.

Note: On CMDB EXPORT list page, only one asset at a time can be exported to CMDB.

74968


In the CM_RPT_DN_ChangeRequest_Master table, the "Assigned WorkGroup Name" column name was misspelled as "Aissigned WorkGroup Name".

Now, in the CM_RPT_DN_ChangeRequest_Master table, you can find two columns named 'Aissigned WorkGroup Name' (misspelled column) and 'Assigned WorkGroup Name' (newly added column), where both hold the same value.

Note:

The reports created using the old column (Aissigned WorkGroup Name) should be replaced with a new column (Assigned WorkGroup Name). Post Tahoe release, the old column named (Aissigned WorkGroup Name) in the 'CM_RPT_DN_ChangeRequest_Master' table will be removed.


Anchor
Known Issues
Known Issues
Known Issues 

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

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.

On the IMPORT ASSET and ADD ASSET pages, the users can add multiple Assets with same Serial No., although, Serial No. is a unique field for Assets. This issue is found if Maker/Checker configuration is enabled. For example, a user added an Asset with Serial No. 123 and is pending for Checker’s approval. The user is able to add another Asset with same Serial No. 123. And send for Checker’s approval. The Checker is also able to approve two Assets with same Serial Number on the MAKER-CHECKER ASSET-APPROVAL page. (#67236)

Bug Reproduction Steps:

  1. Select Asset > User > Manage Asset > Import > Import Asset.
  2. On the IMPORT ASSET page, under GENERAL tab, select the required options and upload the updated Asset Import Template. Click SUBMIT.
  3. Select the sheet to import the Assets. Click the Mapping tab and select the required options if not already selected.  Click Next.
  4. Click the Preview tab and select the store where you want to import the Assets from the Store list.
  5. Click IMPORT ASSETS TO QUEUE on the ACTIONS panel.
  6. Alternatively (Steps 1-5), select Asset > User > Manage Assets > Asset Inventory.  On the ASSET INVENTORY page, click FIXED.  On the ACTIONS panel, click ADD. On the ADD ASSET page, specify the required information and click SUBMIT.
  7. Add two Assets with same Serial Number.
  8. The Application allows to import or add two Asset with same Serial Number.
  9. Select Asset > User > Manage Assets > Approvals > Maker Checker Approval . On the MAKER-CHECKER ASSET-APPROVAL page, click Filters  on the ACTIONS panel. Select the Tenant. Select the Transaction Type as Add to view the list of requests from the Maker.
  10. The Assets with duplicate Serial Number are displayed. Click APPROVE on the ACTIONS panel. On the APPROVE pop-up page, select the  Approval Status as Approved.

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

Scroll ignore
scroll-pdftrue
scroll-officetrue
scroll-chmtrue
scroll-docbooktrue
scroll-eclipsehelptrue
scroll-epubtrue
scroll-htmltrue
1

| |