Customer Fixed Issues and Known Issues Tahoe HF10

Owned by Enterprise IT
Last updated: Apr 23, 2024 by Mayuresh Balaji Kamble (Unlicensed)Version comment
21 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

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
105802In the Incident Module, a mismatch of Resolution time was observed in the View icon of the Incident dashboard and in the Ticket.  

Prerequisite: Configure Customer SLA Matrix for the desired TENANT, WG and priority P1.  

 Steps:  

  1. Log in to SUMMIT Application. 
  2. Navigate to Incident > New Incident.  
  3. Create an Incident for the configured Tenant, WG and Priority P1.  
  4. Navigate to Incident > Incident List - Open the created Incident.  
  5. In the Incident List - Click on 'Summary' Icon for the respective ticket ID.  
  6. Compare the Resolution Deadline and Resolution Time in the summary popup with the same parameters displayed in Incident detail page. 
The Resolution Deadline and Resolution Time values are same in both Summary pop-up and detail page after resolution. 
106779

An error message ‘Oops an error occurred’ was displayed and the reports page resulted in Timeout while opening an IM and SR report. This specifically occurred, when the From and To date selected in the Filter Report was more than 1 year duration.

The reports for which this issue was are:

IM

Daily Incident Report

Reopened Incident Report

Incident FeedBack Report

SR

Daily Service Request Report

Feedback Report

Prerequisite:

Ensure you have IM / SR Reports data with more than 1 year.

Issue was present in both IM and SR Reports. Below are sample steps taken from one of the IM Report.

Steps:

  1. Navigate to Reports > Incident Management > DailyIncidentReport > Action panel > Filter.
  2. Select any Tenant.
  3. Select From and To Date duration more than 1 year duration.
  4. Verify and click Submit.

Populating Reports data more than 1 year had performance page loading issue. This is resolved by restricting the Reports Filter duration (From and To dates) which must be less than 1 year. If you select more than 1 year duration, following message is displayed:

“Max supported duration must be within 1 year.”

105127While configuring the parsing keys in the Notification Parser as Free-form Mail content, the Subject type was missing under Mail Content Type.

Steps:

  1. Navigate to Admin > Notifications > Notification Parser > Click ADD NEW.
  2. Expand CONFIGURE PARSING KEYS > Select Parsing Type as Free-form.
  3. Verify if the Mail Content Type includes Subject.
Subject type is appearing under Mail Content Type while parsing keys in the Notification Parser. 
104493On Logging a new Incident using Rules, while switching tenants the data of the previous Tenant was retained for the next Tenant selected. 

Steps:

  1. Navigate to Incident > User > New Incident > Select the same Tenant and the configured Rule by keying in the appropriate text.
  2. The Rule values are loaded as per configuration.
  3. Change the Tenant. 
While logging a new Incident using Rules and switching tenants the data from the previous Tenant is not retained for the next Tenant.
103917Under Reports, the Incident Dashboard Report was showing Response SLA as more than 100% whereas the Response SLA cannot be above 100%. 

Step:


Navigate to Reports > Incident Management > On the REPORTS dropdown, select Incident Dashboard		The Incident Dashboard Report is showing the correct Response SLA value. 
104493Under the SEND E-MAIL option on an Incident Record, while selecting Workgroup, and adding an Additional Recipient, the list also included Inactive members of the Workgroup.

Steps:

  1. Navigate to Incident > User > Manage Incidents > Incident List.
  2. Open any Incident > Click SEND E-MAIL.
  3. Select the checkbox for Workgroup.
  4. Type in the name of the Inactive member and verify if it appears.
The names of Inactive members of the Workgroup are no longer appearing in the Additional Recipient field. 
105155The Status drop-down on the Relationship Page while linking a new Incident to a Problem was not displaying Resolved option.  

Steps:  

  1. Navigate to Problem > User > Problem Record List  
    Problem Record details page is displayed.   
  2. Click on the Relationship tab.  
  3. Click on the Link drop-down and select the Incident Module. The Relationship Page appears.  
  4. Select the Status drop-down. 

 

The Status drop-down on the Relationship page while linking a new Incident is displaying Resolved option.   
103116System was displaying “Attachment Error (403 status)” for no profile image while loading the communication tree.

Prerequisites (Incident Module):

  1. Navigate to Incident > Manage Incidents > Incident List > click on any Incident ID hyperlink. The Incident ID details page is displayed.
  2. Click Communication Specify the required field information. Click Submit.


Prerequisites (Service Request Module):

  1. Navigate to Request > Manage Service Requests > Service Requests List > click on any SR ID hyperlink. The SR ID details page is displayed.
  2. Click Communication tab. Specify the required field information. Click Submit.
System is not displaying any error message for no profile image while loading the communication tree.
104442

Analyst was getting an error while viewing Reports, and the customer was not able to export and download the report.

Steps:

  1. Click the Filters icon on the ACTIONS panel to specify the filter criteria to display records on the DAILY INCIDENT REPORT

  2. On the table, click the Incident ID to view the incident details.

  3. Click EXPORT TO EXCEL to export and download the table data to a Microsoft Excel sheet.

Analyst views the Report, and  customer exports and downloads the Report successfully after the resolution.

104589Email parsers were not working, and the tickets were not getting created for E-mail notification configured for specific workgroups. 

Prerequisites:

To configure the server for mail parsing action, refer to the following steps:


  1. Navigate to Admin>Advanced>Notification>Mailbox

  2. Select tent as Information Technology and Server type as O365 API server

  3. Configure a mailbox for 'O365' Server type by selecting the Action for Unparsed Mail as 'Move to Folder'.

  4. Click Get Mailbox Folder. A dropdown against Folder Name lists all the Folders in the configured Mailbox.

  5. Select the desired Folder Name and Submit.

  6. Select the option Allow End User to Update Incident and under User communication select Allow Analyst to Update Incident.


Steps:

 

  1. Send a mail to the mailbox by keeping a user in cc.

  2. Reply to the mail from user's outlook.

  3. Reply to the user's mail from the caller's outlook.

E-mail is getting triggered successfully as per E-mail notification configured for specific workgroups after the resolution.

105025

E-mail was not getting triggered as per the E-mail notification configured for specific workgroups.

(Few examples of workgroups: Cisco SOC and TCS SOC).

Prerequisites:

To configure Incident E-mail Notifications, refer the following steps:

  1. Select Incident > Configuration > Others > E-mail Notification.

  2. On the E-MAIL NOTIFICATION page, click ADD NEW on the ACTIONS panel.

  3. Select the Tenant, Workgroup, Location, Customer, Sub customer and other required details.

  4. Click SUBMIT. A new E-mail Notification is configured.

Steps:

  1. Navigate to Incident > Configuration > Others > E-mail Notification.

  2. On the E-MAIL NOTIFICATION page, Select the Tenant, Workgroup, Customer, and Locations.

  3. Click SUBMIT.

  4. On the ACTIONS panel, Click SHOW LIST to display the LIST table. The table shows all the E-mail Notifications configured in the SummitAI application for the selected Tenant.

E-mail is getting triggered successfully as per the E-mail notification configured for specific workgroups after the resolution and is not facing any issues in all related attributes.


106621

Analyst was getting Oops error while selecting the Category, Sub-category under the Change advisory board page.

For example, following pop-up was displayed in message box: “Oops! an error occurred.”

Prerequisite:

  •  Configure child change category for parent change category with more than 50 characters at desired tenant level.

Steps:

  1. Navigate to Change > Configuration > Change Advisory Board.

  2. Check the Tenant > Click + Icon.

  3. Select the desired Category, Change type, Workgroup.

  4. Select the configured Change Category with more than 50 characters.

  5. Select the desired CAB member.

  6. Click SUBMIT.
     
Analyst is not getting Oops error while selecting the Category, Sub-category and is not facing issue with Change Advisory Board page. 


Asset Management 

Issue NumberIssue DescriptionScenarioResolution
102284While performing AD Import from the Summit Proxy Server there was an error, “The connection string property has not been initialized.” 

Prerequisites:  

Ensure there is already a job created under the CUSTOM SCHEDULER page under the monitoring source Summit Server.  

Steps:  

  1. Navigate to Admin > Basic > Users > Import > AD Import.  
  2. Click ADD NEW > Fill in all the mandatory details.  
  3. In the Run at Source field select Summit Server and select the proxy server name under Run at Proxy.
AD import was working from the Summit Proxy Server.  
105701Upon Asset update, the Maker-Checker Approval entry showed the same attribute value in multiple Fields before approval. This was found only if validations were used for the attributes.

Steps: 

To update Asset Attributes:

  1. Navigate to Asset > User > Manage Assets > Asset Inventory.
  2. Select the FIXED asset type.
  3. Filter the Asset by the following values:

Tenant: Any

Status: Select All (Check Box)

Category: Select All (Check Box)

Search by Asset ID

Search Value: Any

Click Submit

  4. Select the Asset id and click UPDATE > Update the         attributes > Click SUBMIT


Maker Checker Approval:

  1. Navigate to Reports > Asset Management> Maker-Checker Dashboard.
  2. Click Filters > Select the Tenant > Select the Status as Pending for Approval > Click SUBMIT.
The Maker-Checker Approval entry displays the accurate values for the attributes after Asset modification.
105889The Screen Connect option was not available on the Asset Details Page to perform the Screen connect action and the RDP Type drop-down in the Remote Desktop Sharing option displayed blank data in the Asset Management Module. 

Prerequisites:

  1. Enable Remote Desktop Button on Asset Details Pop-up Page checkbox should be selected in the Remote Desktop grid in the Tenant Configuration. 

    To configure the above-mentioned condition, perform the following steps: 

    1. Navigate to Admin > Infrastructure > Tenant.
        
    2. In the FILTERS pop-up, select the desired Tenant, which is a mandatory field. 
      The Tenant List is displayed. 

    3. Click the desired Tenant hyperlink. 
      The Tenant Details page is displayed. 

    4. Select Configure Details from the right ACTIONS panel. 

    5. Select Asset Management from the left MODULES panel. 

    6. Scroll down to find the Remote Desktop grid. 


  2. Enable Basic Remote Desktop Sharing and Enable Advanced Remote Desktop Sharing checkboxes should be selected in the Remote Desktop Sharing grid in the Tenant Configuration and Application Settings. 

    To configure the above-mentioned condition in Tenant Configuration, perform the following steps:

    1. Navigate to Admin > Infrastructure > Tenant. 

    2. In the FILTERS pop-up, select the desired Tenant, which is a mandatory field. 
      The Tenant List is displayed. 

    3. Click the desired Tenant hyperlink. 
      The Tenant Details page is displayed. 

    4. Select Configure Details option from the right ACTIONS panel. 

    5. Select Asset Management from the left MODULES panel. 
      Under the General accordion, the Remote Desktop Sharing grid is displayed. 

       To configure the above-mentioned condition in                     Application Settings, perform the following steps:

        a. Navigate to Admin > Basic > Infrastructure >                      Application Settings.

        b. Select the Remote Desktop Sharing option from                  the left panel.
            The Remote Desktop Sharing grid is displayed. 


Steps:

  1. Navigate to Asset > User > Manage Assets > Asset Inventory.

  2. Select Fixed Asset on the Select the Asset Type page.
     
  3. Select the Tenant, which is a mandatory field.  
    The Fixed Asset List page for the respective Tenant is displayed. 

  4. Click the desired Allocated or Instore Asset count hyperlink. 
    The Allocated or Instore  Asset List page is displayed.

  5. Click the desired Asset ID count hyperlink. 
    The Asset Details pop-up is displayed. 

  6. Navigate to the right end of the pop-up and click the Remote Desktop icon.

  7. Select the desired option from the RDP Type drop-down. 

  8. Enter the Customer Email-ID and click the REQUEST icon. 

  9. The icons INVITE, JOIN, and END is available which can be used as per the requirement.     


The Screen Connect option works successfully and the RDP Type drop-down populates data after the resolution.  

The RDP settings for Tenant Level Configuration is available for Asset Management Module as part of the resolution. 

 

NOTE: The Advanced Remote Desktop Sharing for Tenant level settings are already part of Incident Management and Service Management Module.  

 

Platform

Issue IDIssue DescriptionScenarioResolution
106022While searching for Configuration Items (CI’s) on the Global Search with the CI Id there were no results getting displayed. However, the results were getting displayed while searching for the serial number, hostname, and IP address. 

Steps: 

  1. Login to the SummitAI application. Click on the Global Search icon available on the top panel of the application and select the CMDB check box.
  2. Enter the CI Id and click SEARCH.
The Global Search is displaying the results while searching for CI Id. 
100901In the Authentication Configuration, if two Domains were configured then the user from the Domain that was set as ‘False’ were not able login to the Mobile Application.

Prerequisites:

  1. Navigate to Admin > Authentication Configuration.
  2. Add two new Domains:
    Wellness Corp – Set ‘Is Default’ - True
    HealthCare – Set ‘Is Default’ – False.
  3. Log in to the Mobile App with HealthCare Domain.
Users can now login to the Mobile Application successfully even if the Domain is ‘Is Default’ as False when there is more than one Domain configured.
103345Page limitation keys configured in a config file for online profile status were not restricted users to access all pages.

Prerequisites:

  • Add page limitation key in web.config file.

Steps:

  • Login to the SummitAI application.

  • Navigate to the pages that were not added in web.config.
Users are restricted to access the online status pages for which limitation keys are added in the web.config file.
104114The trigger UTG_Izenda_InsertReportMenus was creating performance issues, if it was not disabled at the time of upgrade or rollback.NADue to performance issue the trigger in Summit DB/Reporting DB :UTG_Izenda_InsertReportMenus is deleted. 

Agentless Discovery

Issue NumberIssue DescriptionScenarioResolution
106784User was facing issue, as OS names were not displaying properly in the LICENSE MAPPING under the SOFTWARE INSTALLATION details page.

Steps:

  1. Navigate to ASSET > LICENSE MAPPING > SOFTWARE MAPPING.

  2. Click FILTERS icon on the ACTION PANEL.

  3. Select the Department and License Name from the list and SUBMIT.

  4. Navigate to SOFTWARE INSTALLATION DETAILS report > LIST.

  5. Click FILTERS icon on the ACTION PANEL. The Filters page is displayed.

  6. Select the Department and click SUBMIT. The page displays the details of the OS type.
User is not facing issues with license mapping and OS names are displaying properly after the resolution.

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