Customer Fixed Issues and Known Issues Tahoe HF11

Owned by Enterprise IT
May 08, 2024
19 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 HF01 << Tahoe HF02 << Tahoe HF03 << Tahoe HF04 << Tahoe HF05 << Tahoe HF06 << Tahoe HF07 << Tahoe HF08 << Tahoe HF09 << Tahoe HF10

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

 

On this page: Customer Fixed Issues | Known Issues 

Hotfix Merges

The following Hotfixes are merged with this release. Please refer to the respective Release Notes for details.

Resolved Issues

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

Service Management

Issue IDIssue DescriptionScenarioResolution

107102

The change history Window was responsive for SR module, and they were resizing based on the browser window, but for the IM module change history window was not resizing hence was unable to view the complete columns.


Steps:

1.   Navigate to Incident > Manage Incidents > Incident List.

2.   Access any Incident.

3.   Minimize the browser.

4.    Select the "Change history" icon on the Right side of the Page.

The change history Window is now working fine for IM module. They are getting resized based on the browser window, hence able to view the complete columns.

107263The Work Order names were not available on the checklist when the Incident and Service Work Order checklists were created. 

Steps: 

To configure Service Work Order Checklist:  

  1. Navigate to Request > Configuration > Service Request Masters > Service Request Work Order Checklist.  
     
  2. Select the Tenant from the left pane, which is a mandatory field. 
     
  3. Click Add New from the right ACTIONS panel. 
    The DETAILS page is displayed. 
     
  4. Select the desired Status, Workgroup, Category, Catalog, and Work Order Name from the dropdown.  
    (The Status and Catalog fields are mandatory). 

 

To configure Incident Work Order Checklist: 

  1. Navigate to Incident > Configuration > Incident Masters > Incident Work Order Checklist.  
     
  2. Select the Tenant from the left pane, which is a mandatory field. 
     
  3. Click Add New from the right ACTIONS panel. 
    The DETAILS page is displayed. 
     
  4. Select the desired Status, Workgroup, Category, Catalog, and Work Order Name from the dropdown.  
    (The Status and Catalog fields are mandatory). 
The Work Order names are available on the Incident and Service Work Order checklist pages after the resolution.

104335

Emails using terms like "Auto Generated" and "Auto Submitted" in the mail header were unable to create Incident Tickets.

Steps:

1.   Navigate to Admin > Notifications > Mailbox.

2.   On the FILTERS pop-up, select the department click SUBMIT.

3.   Select a Mailbox Name and fill all the necessary information on the DETAILS page.

4.   Click SUBMIT.

By including the key <add key="App:IgnoreAutoReplayMailID" value="" /> in servermonitor.config the mail header is now allowed to create Incident Tickets using a Notification parser for emails having terms like "Auto Generated" and "Auto Submitted" in the mail. 



Asset Management 

Issue NumberIssue DescriptionScenarioResolution
106571

The user faced an issue while creating Publishers in the Software License Configuration page.  

The issue occurred when more than 10,000 records were added to the common_master table due to which the user was unable to create a publisher on the Software License Configuration page and the publisher was not stored in the database. 

 

Prerequisite: 

  1. The common_master table should contain more than 10,000 records.  

Steps: 

  1. Navigate to Asset > Configuration > Software > Software License Configuration.  
     
  2. Select the Tenant, which is a mandatory field. 
     
  3. Right-click on the desired publisher. 
    Click Create Publisher and enter the name. 
    Click Submit. 
     
  4. Verify the display of the newly created publisher. 
The publishers created on the Software License Configuration page display the accurate data after the resolution.  
107442

The following issues were noticed in the Asset search option on the Service Catalog Request feature: 

  1. The assets which were allocated to the logged-in User were not displayed in the Asset Allocation popup on the New Service Request page. 
     
  2. The User was unable to filter the required assets using the Filters option in the Asset Allocation popup on the New Service Request page.

Prerequisites:  

  1. Log in to the SUMMIT Application as an ADMIN. 
     
  2. Create an SR catalog with Enable Asset Allocation, Enable User Asset, and Enable Asset Search checkboxes selected in the Additional Information tab. 
     
  3. Approve the SR catalog wherein the catalog is in Published mode. 
     
  4. The Asset Inventory should contain Fixed Assets under In-Store, Allocated, and Inactive status. 
     
  5. The Fixed Assets should be allocated to the logged-in user. 

Steps:  

  1. Navigate to Request > User > New Service Request. 
     
  2. Select the desired Tenant from the left panel, which is a mandatory field. 
     
  3. Select the created SR Catalog. 
     
  4. In the Asset Catalog page, verify the assets displayed in the Asset Allocation grid. 
     
  5. Click the Link Asset button. 
    The Asset Allocation popup is displayed. 
     
  6. Verify the Assets displayed in the Asset Allocation popup. 
     
  7. Select the Search By value as Asset ID. 
     
  8. Enter the desired Asset ID value in the Search value text field. 
     
  9. Click the Search icon beside the Search Value text field. 
The Asset Allocation popup displays the allocated assets, and the Filters option works fine after the resolution.

Platform

Issue IDIssue DescriptionScenarioResolution
103108

While trying to create an Incident through an API,  

  • When the Updater was selected as “Executive” and PageName was selected as “TicketDetail”, Description Parameter data was going to Description Field in UI, but the Information parameter data was going to Symptom field in UI.


  • When the Updater was selected as “Caller” and PageName was selected as “LogTicket”, the Description parameter data was going to Description field in UI but the Information Parameter data was going to Description field in UI.

Pre-requisites:  

  1. Updater should be selected as "Executive" or “Caller”.
  2. PageName should be selected as "TicketDetail" or “LogTicket”.

Step:  

Create an Incident through API using IM_LogOrUpdateIncident payload. 

To overcome the Issue a new Parameter SYMPTOM has been created. Irrespective of what value is selected under Updater and PageName, the Symptom value now shows under Symptom field in UI and Description under Description field in UI. 
108230While creating a Report, if the report name was greater than 40 characters system displayed an error. 

Steps:

  1. Navigate to Reports > Change Management > Click the Icon for New Report.
  2. Select the Report Type > CONTINUE TO FIELDS
  3. Enter the fields > Click Save As > Enter the report name > Select the Category > Click OK.
Reports are getting created successfully even when the report name is greater than 40 characters. 
91286In the Izenda report, Work Order (WO) information was not updated correctly due to a logic sync issue in the WO Master. 

Prerequisites: 

  • Configure a Work Order (WO). 
  • Map a Catalog for 4 to 5 auto WO creations to the configured WO. 
  • Configure Izenda report – WO master table. 

Steps: 

  1. Navigate to Service Request (SR) module. 
  2. Create an SR for the configured multiple WOs. 
  3. Manually Cancel the created SR. 
    All the configured WO is cancelled. 
All the Work Orders information is updated as designed. 
107108On the Holiday page, an error was encountered and took more time to load than usual.

Prerequisites:

  1. Log in to the SummitAI application.

  2. Navigate to Admin > Productivity > Holiday. 
The Holiday page is loading as designed. 
108576

In the Mobile App, the text was displayed with HTML tags in the Description and Solution fields of the following pages: 

  • Approve Service Request
  • Incident Details
  • Service Request Details

Prerequisites:  

  • Raise an SR in SummitAI application or Mobile App. 
     
  • Enter the required details to resolve Service Request (SR), such as Solution, User Communication, and Closure Code. 
     
  • Click Submit. 

 

Steps:  

  1. Log in to the Mobile Application. 
     
  2. Click the Requests widget from the Dashboard. 
     
  3. Click the SR ID of the recently raised and resolved SR. 
     
  4. Click SR Details tab. 

 

Notes:  

  •  Issue persists in both Old and New Mobile App. 

  •  Issue fixed for New Mobile App.
In the new Mobile App, the text in the Description, Remarks, and Solution fields appear without HTML tags. 
105799

In the Change Management module, the user encountered the following issue for the cloned CR:  

  • Unable to delink CIs.  
  • Delete attachment added from existing CR.  
  • The Solution field has greyed out in the Implementation tab. 

Prerequisites:  

User with Approver and Change Manager access. 

 Steps:  

  1. Navigate to Change > New Change Record.

  2. Enter the required details, such as Linking the CIs and attaching the attachments. 

  3. Click Submit. 

  4. Authorize and Approve the CR. 

  5. Implement the CR and Submit the details. 

  6. Clone the CR. 
Cloned CR working as designed for all the status, such as Closed, Implemented, and Requested. 
105672In the Email Notification for the approval required notification, the Catalog details were not displayed. 

Prerequisites:  

Enable Include SR Details in SR E-mail in Application Setting. 

 Steps:   

  1. Create a Catalog with custom attributes. 

  2. Add an approver level for the Catalog. 

  3. Create a SR and associate it with the created Catalog. 

  4. Approve the  SR. 
    The Notification Email is triggered to the respective user (caller, workgroup). 

The Service Request’s catalog details are displayed in the Email Notification of the Approval Required Notification.  

Note: The *CustomAttribute* keyword is removed from Approval Required Notification Template. 

108397User was not able to perform Bulk Asset Allocation and encountered ‘Not Allocated’ error message. 

Prerequisites: 

  1. Navigate to Asset > Manage Assets > Imports > Bulk Asset Allocation. 
    The Bulk Asset Allocation screen appears. 

  2. Select a Tenant and a Category. 

  3. Select Allocate Only Store Assets from Allocation Type field. 

  4. Click the DOWNLOAD TEMPLATE icon to load the template. 

  5. Enter the required Asset details from the Inventory in the downloaded spreadsheet template and Save. 

  6. Upload the amended spreadsheet template in the Bulk Asset Allocation screen. 

  7. Click Submit.  

  8. In the Source section, click Select icon corresponding to the Asset Allocation Template. 
     
  9. Enter the following details and click Next: 

    Asset ID 
    Asset Location 
    Asset Floor 
    Select Email ID 
    Cubicle

  10. Click Submit. 
Bulk Asset Allocation is allocating the assets successfully.  

Agentless Discovery

Issue NumberIssue DescriptionScenarioResolution
108161While creating and submitting parser for any parameter, the Parent key value was displaying as zero under CONTENT PARSER pop-up.

Steps:

 

  1. Navigate to Discovery & Monitoring > Discovery Template

  2. On the Discovery Template page, Click the specific Template Name.

  3. Click Actions for the specific Parameter Name.

  4. Under the CONTENT PARSER pop-up select mandatory fields. and add to the list.
The Parent key value is displaying as empty for all parameters under CONTENT PARSER pop-up after the saving the data. 
106631User was facing an issue with Content Parser pop-up in Discovery Template page, as it was not fetching the data from hard disks of multiple sizes (GB and TB). 

Steps:

  1. Navigate to Discovery & Monitoring > Discovery Template > Content parser.

  2. On the Discovery Template page, Click the specific Template Name.

  3. Click Actions for the specific Parameter Name.

  4. Under the CONTENT PARSER pop-up, select Content Type, Output Type, Unit and check the Final output to make it as false for the multiple parsers to work.
User is not facing issue while fetching data from multiple hard disks and is working properly after the resolution.
107218User was facing an issue while fetching IP Address for Windows Management Instrumentation (WMI) discovery. 

Steps:

  1. Navigate to Admin > Discovery & Monitoring > Discovery.

  2. On the Discovery page, Click View Jobs under LIST. The Subnet Details displays the IP ADDRESS of the scanned discovery.
User is not facing issue while fetching IP Address for Windows Management Instrumentation Discovery (WMI) and it is displaying appropriately after the resolution.


Configuration Management Database (CMDB)

Issue NumberIssue DescriptionScenarioResolution
41455The Variance data from Discovery was not getting updated to CMDB automatically.

Prerequisites:

  1. Navigate to CMDB > Configuration > CMDB Discovery Mapping. The CMDB DISCOVERY MAPPING page is displayed. Select the required TENANT and Classification.

  2. Select the Variance Type as Automatic.

The Variance data from Discovery is getting updated to CMDB automatically.

The Custom Scheduler Job should be enabled.

Known Issues 

This section describes the known issues detected by the SummitAI Dev and QA team from previous releases. 

Issue Number

Issue Description

Scenario

Workaround

101982

An approver encountered an error ‘Opps, Error Occurred’ message when opening an SR for approval. 

Prerequisites:

  • Create a Catalog with fields including an Attachment field.
  • Create an SR and attach an email with a symbol in the attached file name.
    For Example:

Steps:

  1. Log in to the SummitAI application as an Approver.

  2. Navigate to Request > Service Request List.

  3. Click the newly created SR ID hyperlink.

N/A

92233

On submitting the cloned CR, the following message is displayed:

“The Standard Template is mandatory.”

Prerequisites:

  1. Navigate to Change > User >New Change Record. The NEW CHANGE RECORD page is displayed. Enable the check box Propose for Standard Change. Enter the value for Standard Template Name and Proposal Justification, and click SUBMIT after mentioning other mandatory fields. A new CR ID is created.

  2. Authorize this newly created CR and click on the CLONE CR tab under Actions panel.

  3. CLONE CR pop-up is displayed. Enable all the check boxes and click Clone. A New CR page will be displayed. Enter the value at Standard Template Name, Proposal Justification and other mandatory fields and click SUBMIT.


NA



Issue

An Administrator has remapped the Resigned approver approvals to a new approver in the Resigned Approver List. Before the original approver has resigned, an asset task for floor or store movement is awaiting approval. It is now assigned to the new approver as per action taken by Admin. The new approver is getting an information message "You are not an approver" on the Movement Approval page (Asset > Manage Assets > Approvals > Movement Approval) while approving an asset for floor or store movement. (#86330)

On Change Record List screen, the selected field value for the Tag filter is getting cleared when you select the field value for the Tenant filter as ALL. (#86329)

A sub-status that is not default, is deactivated even though the sub-status is assigned to an Asset.

Recommendation: To deactivate the sub-status, move the active Assets to another sub-status and then deactivate the sub-status. (#86269)

Full Name is not displayed under FIXED ASSETS upon selecting Dashboard > Asset Dashboard. This issue occurs when you have configured the Sub Status parent with 50 characters or more. (#86159)

Note

The Full Name is displayed, if you rotate the PIE Chart to 90 degrees.

The sub-status value of previously selected Tenant is retained still for the newly selected Tenant. For example, the sub-status value selected for a Tenant ‘IT Solutions’ is ‘server’. Now search for a different Tenant and select another Tenant as ‘Information Technology’. The sub-status value ‘server’ of previous Tenant is displayed incorrectly for the newly selected Tenant ‘Information Technology’. (#86273)

On the Remote Desktop Sharing screen, when you request for a Microsoft Teams meeting link (Advanced > RDP Type > Microsoft Teams) and click on Audit Log hyperlink under Session History tab, the message "Your request is processing please wait…" is displayed, but no further action is being made (#86297).

The formatting of Custom Attributes and Attribute Values using nicEditor on the User Communication tab of the Service Request Details page is missing when you click on the Print icon of the My Service Request Details page (#84048).

The text alignment of Custom Attributes and Attribute Values mentioned on the Service Request Details page is not getting displayed properly on the My Service Request Details page under the Additional Information tab (#83888).

On the notification window, the scheduled CAB meeting time is displaying incorrectly (#85493).

On accepting the meeting invite (calendar invite), the date and time are displaying incorrectly in the When field of the acceptance e-mail in the Sent Items folder (#84971).

On Microsoft Teams, the joined user details are displaying as 'U'(Undefined). But on hovering the mouse on 'U', the user details are displaying on the screen. This issue is happening only with the Admin account (#84966).

While sharing the screen, the selected screen is getting displayed multiple times and the screen gets stuck. Due to this issue, the data on the screen is not completely displayed. This issue is occurring only when the user logs in to the MS Teams desktop app as well as a browser app at the same time and tries to share the screen (#84978).

Admin is not getting any notification that users are waiting in the lobby when the Admin has opened the MS teams in two different browsers or two different devices (#84982).

On the COMMUNICATION HISTORY pop-up, the data (Custom attributes and its values) of the User Communication is not displayed in proper format and all the data is displayed in a single line without any delimiter. This issue occurred when Custom Attributes and their values were updated from the User Communication section on the SR Details page (#84018).

On the Communication tab and Change History tab of the Service Request Summary pop-up, the Custom attributes, and its values are not aligned properly. This issue occurred when Custom Attributes and their values were updated from the User Communication section on the SR Details page (#83893).

In the User Communication tab of the Service Request Detail page, formatting applied to Custom Attributes and Attribute Values using nicEditor is not retained in the End-User e-mail body when the ticket is updated.

(Bug# 84047)

In the Text Editor, when text alignment (Middle, Centre, Left) option is used, the UI alignment is not working as expected throughout the SummitAI application.

(Bug# 85770)

Following known issues are observed in the Problem Record Detail page for Mobile application:

  • When the RCA Approver refers back the PR, the RCA Approver Name and RCA Approve Date are not captured.
  • When the Reviewer refers back the PR, the Reviewer/Approver Name, Reviewer/Approver Date and Reviewer/Approver Status are not captured.
  • When the Reviewer rejects the PR, the Reviewer/Approver Name and Reviewer/Approver Date are not captured.

(Bug# 85946)

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.

(Bug# 73532)

For the Custom Attribute (Drop-down), if any value is set as default on the Form Builder page (Admin > Basic > Infrastructure > 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 > Drag and drop the Drop-down Custom Attribute > Type in the Label for the Custom Attribute > Select Options (data source) as Manual > Type in the Drop-down Values and Make one value as default), then the default value is not automatically set for that Custom Attribute (Drop-down) across the Incident Management module

(Bug# 71703).

If the SLA is paused during the PR resolution and the Paused Time is before RCA Deadline, the paused duration is not getting added to the Resolution Deadline. This issue is occurring when the Resolution Deadline Type is selected as RCA Deadline Time in the Deadline Configuration. (Bug#74495)

Note: 

If the SLA Paused Time is between RCA Actual Time and RCA Deadline, the paused duration does not consider for the Resolution Deadline.

Example:

Consider the PR Log Time as 9:00 AM, RCA Deadline as one hour, and Resolution Deadline two hours.

The paused duration does not add if the Analyst performs the below actions:

  • If the RCA completed at 9:30 AM (RCA Actual Time), where RCA Deadline is 10:00 AM.
  • If the Analyst pauses the PR at 9:40 AM to 9:50 AM before RCA Deadline Time (10:00 AM), the paused duration 10 mins is not getting added to the Resolution Deadline.

The Expected Resolution Deadline should be:

RCA Deadline Time + Resolution Deadline + Paused Time = 10:00 AM + 2 hours + 10 mins = 12:10 PM.

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.
(Bug# 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.

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.

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.

(Bug#67236)

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.

(Bug#67240)

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