Customer Fixed Issues and Known Issues Tahoe SP3 HF12

Owned by Enterprise IT
May 08, 2024

 | Previous Versions: << Sierra << Sierra HF01 << Sierra SP1 << Sierra SP1 HF01 << Sierra SP1 HF02 << Sierra SP1 HF03 << Denali << Denali HF01 << Denali HF02 << Denali HF03 << Denali SP1 << Denali SP1 HF01 << Tahoe << Tahoe SP1 << Tahoe SP3 HF01 << Tahoe SP3 HF01 (v1) << Tahoe SP3 HF02 << Tahoe SP3 HF03 << Tahoe SP3 HF04 << Tahoe SP3 HF05 << Tahoe SP3 HF06 << Tahoe SP3 HF07 << Tahoe SP3 HF08 << Tahoe SP3 HF09 << Tahoe SP3 HF10 << Tahoe SP3 HF11

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

On this page: Customer Fixed Issues | Known Issues 

Merged Releases

Following are the merged releases in Tahoe SP3 HF12:

Customer Fixed Issues 

This section describes the issues reported by the customers and their fixes in Tahoe SP3 HF11 version.

Service Management

Issue ID

Issue Description

Scenario

Resolution

124512

The system was displaying the data older than 36 months in the archive. 

Prerequisites (Scenario I)

  1. Navigate to Incident > Manage Incidents > Incident List. The Incident List page is displayed.
  2. Hover on Incident ID hyperlink and select the option Assign to me.
  3. Click Submit.

Prerequisite (Scenario II)

Update the SR via email.

The system is not displaying the data older than 36 months in the archive.

126190

Holiday was not showing different locations and date as compared to what was configured.  

Steps:  

  1. Navigate to Admin > Advanced > Productivity > Holiday.

  2. Click ADD NEW > Select the Domain > Select Holiday Date > Select the Location.

  3. Add a description under Holiday Description.

  4. Click SUBMIT.

  5. Click SHOW LIST from the ACTIONS Panel.

  6. Verify if the configured Holiday is displayed accurately. 


Holiday is getting displayed as configured.   

123288

In the Service Request Module, user attributes such as Department, email id and contact were not getting displayed when hovering over User field in the CATALOG DETAIL page.

Prerequisites:

  1. Navigate to Admin > Infrastructure > Application Settings.

  2. Click User Search Tile > Check Enable User Search Tile > Select the Display Mode as On

  3. Create and publish a Catalog having User control

  4. Create a Service Request and assign it to any user.

Steps:

  1. Navigate to Request > User > Manage Service Request > Service Request

  2. Click the SR which was created.

  3. Click CATALOG DETAILS on the ACTIONS

  4. Mouse hover on the profile icon in User


User attributes such as Department, email id and contact are getting displayed when hovering over User field in the CATALOG DETAIL page. 

122659

Users were getting the message, “Oops! An error occurred.” while raising a Service Request using a Catalog having a Multivalued dropdown. 

Prerequisite:

  1. Create a Catalog with multivalued group (under this group file, Multivalued dropdown attributes should be present).

  2. Publish the Catalog.

Steps:

  1. Login to the Summit application. 

  2. Navigate to Request > User Manage Service Requests > New Service Request for User.

  3. Select the Catalog created which has a multivalued group (under this group file, Multivalued dropdown attributes should be present).

Users can raise a Service Request using Catalog having Multivalued dropdown without any error. 

122277 

The substatus was not getting displayed on Approve Service Requests list page for status Pending for Approval. 

Prerequisites:  

  1. Navigate to Request > User > Approve Service Request. The Approve Service Request list page is displayed. 

  2. Observe the Status (Pending for Approval) and Substatus fields (such as Refer Back, On Hold, Forward).  


The substatus is getting displayed on Approve Service Request list page for status Pending for Approval. 

125662

Auto Escalation mails were not triggering for email ids configured which were not present in the user list.

Steps:

  1. Navigate to Admin > Productivity > Escalation.

  2. Select the respective tenant.

  3. Select Incident Module.

  4. Configure the auto escalation by entering the required data.

  5. Click Submit.

  6. Run the respective job.

  7. Raise an Incident.

  8. Check for the auto escalation mail.

Note: Email id should not be present in the user list.

Auto Escalation mails are successfully triggering for email ids configured and are not present in the user list.

126798

On the Discovery Template, the newly added Parser was not working as expected. Spaces were not considered as part of the value for preceding and succeeding text fields due to which it was not able to fetch the data.

Steps:

  1. Navigate to Admin > Advanced > Discovery and Monitoring > Discovery Templates.

  2. Click Filters.

  3. Select Tenant and click Submit.

  4. Click Template Name.

  5. Click and edit Actions.

  6. Verify the Preceding and Succeeding text fields.

The newly added parser is working appropriately along with space values on preceding and succeeding text fields.

125584

No errors were produced when Initial authorizer remarks exceeded 200 characters.

 Steps:

  1. Navigate to Change > User > New Change Record.

  2. Fill in all the mandatory fields and Submit.

  3. Authorize the created CR by entering more than 200 characters in the remarks field and then Submit.

  4. Verify the CR status.

 

Error not produced when remarks exceed 200 characters is fixed after the resolution.     

124436 

When the user was opening a Problem Record and clicking Submit without performing actions, the page was getting refreshed and triggering mail to Requestor, Assigned Analyst and Workgroup members.  Steps: 
  1. Select Problem > New Problem Record. 

  2. On the NEW PROBLEM RECORD page, type in the mandatory details and click SUBMIT. A new Problem Record is created. 
     
  3. Click SHOW LIST, open the PR created in previous step. 
     
  4. Without editing any data, just click on submit button. Mail is getting triggered to Requestor, Assigned Analyst and Workgroup members. 

No mail triggers when the user clicks Submit without modifying any data in PR and whenever status of PR changes, mail triggers to respective users.

125085

Recurring Change records are not generated for Standard Changes.

Prerequisites:

  1. Create a Standard Template for a Standard Change request.

  2. Create a Standard CR with the created template. The status of the CR should be in the requested status.

  3. Recurring CR job should be running.

Steps:

  1. Log in to the Summit application.

  2. Navigate to Change > Change Record List.

  3. Select the created Standard CR with Requested Status.

  4. Authorize the Change request.

  5. Approve the Change.

The recurring CRs are generated for Standard changes.

The functionality is working as intended. 

123807

In a Release record, when an analyst uploads the attachment under the test tab, it is not available after submitting the release record.

Steps:

  1. Log in to the Summit application.

  2. Navigate to Release > Release Record List.

  3. Open a created release record. Click the Test Tab.

  4. Select the Test Stage as New Test Plan. Upload an attachment and click Submit.

The attachments uploaded in the Test Tab are available after submitting the release record. 


Asset Management

Issue ID

Issue Description

Scenario

Resolution

120878

Allocated Asset User details were not displayed in the Asset Inventory List and Details page but were shown in the Allocation History tab. 

 

The issue occurred when the checker clicked the Approve button more than one time. 

 

NOTE: 

Maker-Checker was enabled for the asset allocation process. 

 


Steps: 

  1. Navigate to Asset > User > Manage Assets > Approvals > Maker-Checker Approval. 
    Maker-Checker Asset Approval page is displayed. 
     
  2. In the FILTERS pop-up, select the following values: 

       Tenant- Desired Tenant 

       Transaction Type- Allocate

       Category- Desired Asset category

       Location- Desired location
       Click SUBMIT.

  3. Select the desired asset checkbox.

  4. Click APPROVE from the right ACTIONS panel.

  5. Select Approval Status as Approved.
      Click SUBMIT(more than once.

  6. Check the user details on the Asset Inventory page.
     ( Asset > User > Manage Assets > Asset Inventory) 


Allocate Asset User details are displayed in the Asset Inventory List and Details page successfully after the resolution.  

124037

The system was unable to update the accessories information on Update Accessories page using Update under Action Panel.

Prerequisite:

Define a rule under Form Builder section.

Steps:

  1. Navigate to User > Manage Assets > Asset Inventory. The Asset Inventory page is displayed. Select the Asset Type as Accessories. The Accessories page is displayed.

  2. Click on In-Store count hyperlink. The Accessories details page is displayed.

  3. Select the checkbox Asset Click Update under Actions panel. The Update Accessories page is displayed. Make the necessary updates and click Submit.


The system is able to update the accessories information on Update Accessories page using Update under Action Panel.
124546

ISBN barcode was not showing in print preview screen for the first time. After clicking on Cancel and then again clicking on Print, the barcode was appearing.

Steps:

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

  2. Select Fixed Asset.

  3. The List page appears. Select a Tenant.

  4. Click the In-Store Asset from a Category.

  5. Click Print Barcode from right side Actions panel.

The ISBN barcode was successfully showing on the print preview screen.
123344

Under the Asset Code configuration page, the Bulk import & Single option was facing file attachment issue.

Pre-requisites:

  • Maker checker approval should be configured for adding transactions.

  • File upload control should be present for the Fixed asset category.

Steps:

  1. Navigate to Asset > Asset Inventory > Fixed Asset > Tenant > Add Action.

  2. Fill in the required details and upload attachments in the File upload control and click Submit.

  3. Navigate to the Maker Checker Approval page with Checker credential and approve the add transaction. Add transaction gets approved successfully.

  4. Navigate to Asset Inventory > Fixed Asset > Instore.

  5. Click the asset id details popup and validate the File upload control present in Asset Information.
Asset moves to Maker Checker Approval and file upload attachment displays under File upload control.
125054

Mac Agent was deployed but was not showing in the new Discovery.

Steps:

  1. Navigate to Reports > Asset Management.

  2. Scroll down page to Reports.

  3. Select Agent Online Status Report.

  4. Click Filters. Select the required attributes.

  5. Click Submit on the Filters popup. List of Assets will be displayed.

  6. Click Serial Number hyperlink of the required Asset.

  7. Navigate to Hardware Discovery and Software Discovery tab and verify the details on these pages.

  8. Click Filters from the right panel.

  9. Fill in all the mandatory details.

  10. Click Submit.

The MAC Agent is successfully getting contacted with the device/machine/asset and the hardware and software details are captured without any error.
125863

UTC time zone was displayed instead of IST in the movement date field on the Store Movement approval page. 

 


Steps:  

  1. Navigate to Asset > User > Manage Assets > Approvals > Movement Approvals. 
     
  2. Select the desired Tenant, Asset Type as Non-Fixed, and other fields in FILTERS pop-up. 
    Select SUBMIT. 
    Movement Approval of Non-Fixed Asset is displayed. 
     
  3. Click the desired Movement ID hyperlink. 
    Movement Approval pop-up is displayed. 
     
  4. Verify the Movement Date field. 
     
User time zone is displayed on the Store Movement approval page after the resolution. 
127260

No data- Oops error was displayed on the asset New Discovery page. 

 


Steps: 

  1. Navigate to Asset > User > Manage Assets > Variance > New Discovery. 
     
  2. Verify the details displayed. 


New Discovery page displays the right data without any error after the resolution. 

Platform

Issue ID

Issue Description

Scenario

Resolution

121732

The report for network device configuration push is not being triggering.

Prerequisite:

 Enable backup to Network device.

 Steps:

  1. Log in to the Summit App.

  2. Navigate to Reports > IT Operational module > Network Device Configuration report.

  3. Configure Push Report using two format that is with attachment and XML format.

The report for network device configuration push is functioning as expected and being successfully triggering.

123436

The asset accessories on the Update Accessories page were not successfully updated.

Prerequisite:

Add a Rule validation in Validate Controls pop-up in the Form Builder page for Accessories Asset.

Steps:

  1. Log in to the Summit App.

  2. Navigate to Asset > User > Manage Asset > Asset Inventory.

  3. Select ACCESSORIES as Asset Type.

  4. In the FILTERS section, enter the details and click SUBMIT.

  5. Click the Asset ID and click Update icon from the ACTIONS panel.
    The Update Accessories page is displayed.

  6. Make the required changes and click SUBMIT.

The asset accessories are updating successfully.

124051

Duplicate alert for Asset Movement was being triggered.  

Prerequisite:

 Complete Asset Movement Configuration

 Steps:

  1. Log in to the Summit App.

  2. Navigate to Asset > User > Manage Asset > Asset Inventory > Fixed Asset.

  3. Select a Tenant from the list.

  4. In the FILTERS section, enter the details and click SUBMIT.

  5. Click the Asset ID to view the Asset Details.

  6. On the ACTIONS panel, click Store Movement.

Asset Movement alerts are being sent without any duplication.

124869

The ‘<’ special character was not displayed in the resolved Service Request - Email Notification.

Prerequisites: 

  • Configure and Publish Catalog without any Approval Levels.

  • Raise an SR.

  • Update SR to In-progress status.

  • In the Postman application, resolve SR with ‘<’ symbol in the solution parameter. 

Steps:

  1. Log in to the Summit App.

  2. Navigate to Request > Service Request List.
  3. Click SRID hyperlink.

The special character is displayed without any issue.

124328

The user list is not being completely imported from the CSV file to the proxy server, causing a sync issue in HMSI.  

Prerequisites: 

  1. Add the 2 keys in Web config or App config in proxy server and DC in web files.  

    Keys to be added 
    <add key="App:CSVUserDomain" value="APU" /> 

<add key="App:CSVImportField" value="NAME|UserName,ADEMPCODE|EmpID,NTUID|NT_UID,EMAILID|EmailID,EMPLOCATION|Location,EMPLOYEESTATUS|isactive,DESIGNATION|Designation,PHONENUMBER|MobileNo,PHONENUMBER|ContactNo,COUNTRY|Country,REPORTINGMANAGER1|Manager,REPORTINGMANAGER2|CA_ReportingManager2,SECTIONNAME|CA_Section Name,SECTIONMANAGER|CA_Section Manager,DEPARTMENTNAME|CA_Department Name,DEPARTMENTMANAGER|CA_Department Manager,DIVISIONNAME|CA_Division Name,DIVISIONHEAD|CA_Division Head,OPERATIONNAME|Customer,OPERATIONHEAD|CA_Operation Head,FUNCTIONALDESIGNATION|CA_Functional Designation,COORDINATOR|CA_Coordinator,EXECOORDINATOR|CA_EXE Coordinator,DIRECTOR|CA_Director" />
  2. In the proxy service, navigate to Data > User import. In this folder, complete, failed, and pending folders should be present. 

Steps: 

  1. Log in to the Summit application.  

  2. Navigate to Admin > Custom Scheduler.  

  3. Run the job “User import from CSV file”. 

  4. Add the CSV file in the Pending folder created.  

  5. After adding the folder rerun the job “User import from CSV file”.  

  6. Once the job is successfully completed, the CSV file is moved from the pending folder to the completed folder. 

The correct data of the user from the CSV user list is completely imported into the proxy server. 
If there are any errors while importing, SUMMIT_Error_Log table captures the correct logs for invalid user data in the CSV excel sheet. For any missing data in the excel sheet, the logs are captured in the logs folder of the DC. 

Agentless Discovery

Issue ID

Issue Description

Scenario

Resolution

126510

Fields values were not getting displayed in Additional Discovery.

Steps:


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

  2. Create an SSH job by checking the check box of Additional Discovery.

  3. Navigate to Admin > Discovery &Monitoring > Discovery Report.  
      
  4. Select the tenant from the FILTERS on the ACTION panel and click SUBMIT. The Discovery LIST page gets displayed. 
     
  5. Navigate to the reports page by clicking Tabular View icon to view the details of Discovered IPs.  
     
  6. Click any IP address to view the hardware, software, and additional details. 

  7. Click the ADDITIONAL DISCOVERY tab in the action panel and check the field values. 

Field values displays in Additional Discovery appropriately after the resolution.

Operations Management

Issue ID

Issue Description

Scenario

Resolution

126170

The system displays the following error message after editing End Time, while submitting:

“Start Time should be greater than Current User Time.”


Prerequisite:

The job is schedule for one time.

Steps:

  1. Navigate to Operations > General > Maintenance. The Maintenance List page is displayed.

  2. Select required filters for scheduled maintenance and submit.

  3. Select existing maintenance which is currently under progress.  The Maintenance details page is displayed. 

  4. Update End Time (either decrease or increase the future date and time).

  5. Click Submit.

While editing now the system is not displaying the following error message after editing End Time, while submitting: 
“ Start Time should be greater than Current User Time.”

122773

User was not having the access to choose the tenants for specific modules in Discovery pages such as Scripts, Script Based Monitoring, SNMP MIB, SNMP Based Monitoring.

Prerequisite:

  1. The application is without ITOM module license access.

Steps:

  1. Navigate to Admin > Discovery & Monitoring. 
     
  2. Select the pages like Script, Script Based Monitoring, SNMP MIB or SNMP Based Monitoring. 
     
  3. Click Filters. 
     
  4. The list of tenants will be displayed under Department. 
     
  5. Verify the Tenant that can be accessed by the user.

Tenants are successfully displaying in the Discovery pages when ITOM module licenses are not available.

122217  

Unable to create SOP and Evaluator in the ILT instance as departments were not reflected in the Tenant list. 

Precondition 

  1. User should be created in a non-global domain with Analyst access (The application is without ITOM module license access).  

Steps: 

  1.  Navigate to Admin > Advanced > Documents > Standard Operating Procedure (SOP).  

  2. Verify the Tenant that can be accessed by the user.  

SOP and Evaluator can be created in the ILT instance after the resolution.  

Fixed 502 Bad Gateway issue in Azure utilities related to SQL sessions.


Known Issues 

This section describes the known issues detected by the SummitAI Dev and QA team in this Release.

Issue ID

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

100922

An error ‘Opps! An error occurred’  or a Saved Successful message was displayed for all the modules, if the mandatory configuration fields were saved with a space (empty) value.

Scenario – I


1.       Navigate to Incident > SLA Configurations > Urgency.

2.       Select a Tenant.

3.       Click Add New from left panel.

4.       Press Space Key in Urgency Name field and click SUBMIT


Scenario – II


1.       Navigate to Problem Management > SLA Violation Reason.

2.       Select a Tenant.

3.       Click Add New from left panel.

4.       Select the Violation Type from the list.

5.       Press Space Key in SLA Violation Reason field and click SUBMIT.

N/A

105119

After submission, the text is getting converted to code for Question and Answer fields.

Prerequisites:


1.       Navigate to Knowledge > User > New Knowledge Record. The New Knowledge Record details page is displayed. Specify the mandatory fields. Make sure for Question field use keyboard Enter key. Click Submit.


2.       Navigate to Knowledge > User > Knowledge Record List. The Knowledge Record List page is displayed. Open any KB article with Status as Published. The Knowledge Record details page is displayed. Click COPY KNOWLEDGE RECORD link under Action panel. Check for the Answer field.

N/A

100352

When a Change Record (CR) is created with ‘special characters’ in status, it does not display any data in Change Record list page.

Prerequisites:


1.       Create a 'status' having special characters such as (*satus_test*).


2.       Create the CR.


Steps:


1.       Log in as approver.


2.       Navigate to Change > Change record list.


3.       Click on the Filters icon.


4.       Select the 'Tenant' field as ALL.


5.       Select the previously created 'status'.


6.       Click Apply.


7.       Verify the results, after applying the status filter with special characters.

N/A

100760

The ‘Category’ filters on the Change Record (CR) list page do not display any data results when you select ALL Tenant and Category.

Steps:

1.    Navigate to Change > User > Change Record list.

2.    Select the 'Tenant' field as ALL.

3.    Select the field as Category.

4.    Click Apply.

5.    Check the results displayed on the Change Record list page.

The Category filter works fine, when you select individual Tenant and Category.

100781When a ‘User Contact Number’ is used to filter records on the list page of IM/SR/PM, it does not fetch any data records.

Below is just an example from Incident Management list page. It also applies to SR and PM list pages too where User Contact Number is used. as filter:

Steps: Incident Management (IM)

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

The Incident List page is displayed with list of incidents.

2.    From Filter options, select User Attributes
> User Contact Number. Select the operator as = and enter the Contact Number in the Value field of the respective User.

3.    Click Apply.

4.    Verify the results, after applying the User Contact Number filter.

N/A
100796The ‘Time Selection’ option is not displayed to an Analyst on the SR list page, when Equals (=) operator is selected for Time Filter.

Steps:

1.    Log in as an Analyst.

2.    Navigate to Request > Service Request List.

3.    Select the Time related Filter and choose Equals (=) operator.

4.    Click Calendar icon.

5. Check if you are getting the Time Selection option or not in Calendar popup.

N/A
100798The filter option ‘<=’ operator for Log Time Filter used by an Analyst on the SR list page, does not yield proper filter results.

Steps:

1.    Log in as an Analyst.

2.    Navigate to Request > Service Request List.

3.    Select the Log Time filter and choose operator (<=).

4.    Click Calendar icon.

5.    Select date and time for an already existing SR.

6.    Click Apply.

7.    Check if you are getting the filter results.

N/A
100808

The View names created by an Analyst for IM/SR/PM/CM

modules with long Japanese names are getting out of the container, unlike the English long names.

Steps:

1.    Log in to the Application as an Analyst.

2.    Navigate to Request > Service Request List and create a view with long Japanese name and apply view.

3.    Navigate to Incident > Incident List and create a view with long Japanese name and apply view.

4.    Navigate to Problem >
Problem Record List and create a view with long Japanese name and apply view.

5.    Navigate to Change > Change Record List and create a view with long Japanese name and apply view.

6.    Verify the view name in Japanese language text which goes out of the container.

N/A
100813The Assigned To drop-down does not display the User list.

Prerequisite:

The key

<add key="App:MultiLanguageEncodingEnabled" value="true" /> is set to True in webconfig file.


Steps:

1.  Navigate to Incident > User > Manage Incidents > Incident List. In the Incident List Click Incident ID hyperlink. The Incident ID details page is displayed.
        
2. Click RELATIONSHIP tab Click on the displayed Work Order ID. The Work Order ID page is displayed. Check Assigned To drop-down field under ASSIGNMENTS tab.


N/A

 



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 SP1 << Denali SP1 HF01 << Tahoe

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 Hotfix versions are merged with this release. Please refer to the respective Release Notes for details.

  • <Release Name> (Patch Release)

Known Issues 

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

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 Web 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# 86000/ 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).