Customer Fixed Issues and Known Issues Tahoe SP3 HF15

Owned by Enterprise IT
May 08, 2024
24 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 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 << Tahoe SP3 HF12 << Tahoe SP3 HF13 << Tahoe SP3 HF14

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 HF15:


Customer Fixed Issues 

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

Service Management

130775

The Test table details were getting displayed in English language. 

Steps:

  1. Navigate to Release > User > Release Record List. The Release Record list page is displayed. page is displayed.

  2. Click RR ID hyperlink. The Release Record ID details page is displayed.

  3. Navigate to Test tab. Add a Test Details with Test Stage as Test Completion. The Test details are captured in the table.

  4. Change the language to Japanese.

  5. Click Detailsicon. The Test Plan details pop-up is displayed. 

The Test table details are getting displayed in Japanese language.

131273

The Closure Date for the child incident was not getting captured in the “IM_ticketmaster” table.


Prerequisites:

Create a Parent and Child incident.

Steps:

  1. Navigate to Incident > Manage Incidents > Tenant > Incident List. The Incident list page is displayed.

  2. Select the Incident ID hyperlink of the above created Parent Incident.

  3. Close the Parent Incident.

  4. Verify the Closure Date of Child incident.

The Closure Date for the child incident is getting captured in the “IM_ticketmaster” table.


131332

In the Work Order template, the Source field keyword was not getting replaced with the SR ID link.

Steps:

  1. Navigate to Request > Manage Service Requests > Service Request List. The Service Request List page is displayed.

  2. Click SR ID hyperlink. The SR ID details page is displayed.

  3. Navigate to Relationship tab and create a Work Order.

In the Work Order template, the Source field keyword is getting replaced with the SR ID link.

132081

When the Change History of an Incident was exported to PDF having the Old Value column as "Backend update as confirmed by customer" users were experiencing "Oops! An error occurred” message.

Precondition:

Insert the below query with respect to Incident ID present in your database (first column value)

INSERT INTO IM_Ticket_History WITH(ROWLOCK) (Ticket_ID,Column_Name,Change_Date,Old_Value,New_Value)

VALUES (10,'Status',GETUTCDATE(),N'Backend update as confirmed by customer','Resolved').

Steps:

  1. Log in to the application.

  2. Navigate to Incident > User > Manage Incidents > Incident List.

  3. Select Incident ID.

  4. Select EXPORT TO PDF from the Action panel.

  5. Check Change History.

  6. Click Export.

The action item EXPORT TO PDF of the Change History is working as expected without any errors.

128891

The status of SR was not getting changed from Pending to In Progress.

Steps:

  1. Log in to the Summit App.

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

  3. Select the desired Tenant from the list.

  4. Enter the required details.

  5. Select the ‘Is DownTime Required’ as Yes.

  6. Enter Down Start Date/Time & End Date/Time.

  7. Click Submit.

SR status gets changed from Pending to In Progress.

Note: This issue is also addressed in the Incident management module.

131205

In the Summit app, CRs were created without a validation message when the DownTime Start and DownTime End were the same. 

Steps: 

  1. Log in to the Summit App. 

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

  3. Select the desired Tenant from the list.
  4. Enter the required details.  

  5. Select the ‘Is DownTime Required’ as Yes.

  6. Enter same Down Start Date/Time & End Date/Time.
  7. Click Submit. 

The Summit app triggers a validation message on entering the same Down Start Date/Time and End Date/Time. 

130035

The user was encountered error message when clicking on the Service Request ID in the notification email.

Steps:

  1. Log in to the Summit application.

  2. Navigate to Request > User > Manage Service Requests > Service Request List.

  3. Click SR ID hyperlink.

  4. Assign to another user for approval and click Submit.

  5. A notification sent to the assigned user.

  6. Click Service Request ID from the notification email.

The user can access the Service Request from the notification email without any errors.

131173

When trying to access an Incident from the notification email, it had redirected to an incorrect URL.

Prerequisite:

Raise an incident in Summit Mobile App.

Steps:

  1. In the notification email received for newly created Incident.

  2. Click Incident ID hyperlink.

When trying to access an Incident from a notification email, it redirects to the correct URL.

131202 

System Impact values were not loading as per the sort order. 

Steps: 

  1.  Configure the System Impact with Sort order. 
     
  2. Navigate to Change > New Change Record. 
     
  3. Select the same tenant. 
     
  4. Navigate to the Risk tab and verify the System Impact values. 


System Impact value loads properly as per the sort order configuration. 

132688When the analyst updated the data for Serial No field in Configuration Item (CI) ID page, Server tab data were not getting displayed in the Change History and BI report. 

Steps:

  1.  Navigate to CMDB > Configuration Item List.

  2. Click existing CI with Server classification.

  3. Update the fields in the Server tab and click Submit.

  4. Navigate to Change History and verify the details shown in NEW VALUE column.

  5. Update the Serial No field and click Submit.

  6. Navigate to Change History and verify the details shown in NEW VALUE column.



Server tab data in Change History value updates in the NEW VALUE column and is displaying appropriately in related attributes.

131659

The Auto resolved ticket resolution comments were not reflected in the report.

 Prerequisites:

  1. Auto resolved should be enabled for pending incidents at the Tenant level and respective jobs should be running.

  2. Create incidents and move to pending.

Steps:

  1.  Check the solution field in the BI Report, Daily Incident Report, and IM_ticket_information table

Note: The solution is displayed for manually resolved incidents.

Auto-resolved ticket resolution comments are reflected after the resolution.

131319

The Standard CR was getting logged without selecting the standard template

 Steps:

  1. Navigate to Change > New Change Record.

  2. Fill all the mandatory fields.

  3. Select the Change Type as ‘Standard’ and close the ‘Standard Import Template’ pop up.

  4. Click ‘Save as Draft’ and the CR gets saved as draft.

  5. Select the ‘Change Type’ as ‘Standard’ and close the ‘Standard Import Template’ popup.

  6. Click Submit.

Standard CR is not getting logged without selecting the standard template in Draft / Submit mode after the resolution.     

132524

While importing the service catalog, an error is displayed, “An error occurred while importing the data”  

Steps:  

  1. Navigate to Admin > Infrastructure > Export/Import > Import Configurations by File.  

  2. On this page, upload the catalog export file.  

  3. After the page is refreshed, click Import. 

  4. After the page is refreshed, click Import All.  

The Service catalog is imported without any errors.  

132054

In the Incident Feedback report, the data is not populated after clicking on Export All.  

Steps:  

  1. Navigate to Reports > Incident Management. 

  2. Select the Incident Feedback Report.  

  3. Apply the filter details if required. 

  4. Click Export All.  

The data is populated in the Incident Feedback Report after clicking on export all.  

128208

The Requestor and Logged by parameters not working for Create new SR API Payload.

Steps:

  1. Log an SR using API ‘SR_LogServiceRequestCatalog’.

  2. Navigate to Manage Service Requests > Service Request List.

  3. Select the SR logged via API and check SR details.

The Requestor and Logged by parameters are successfully getting displayed.

131315

User was unable to view the configured data and the Caller Details pop-up page did not have a bottom scroll bar. 

Prerequisites:  

  1. Custom attributes should be configured for the Multi-value group from the User module/Table on the FORM BUILDER page.

  2. Navigate to Admin > User List.

  3. User list page is displayed and filter the User Name(User should have the incident)

  4. Navigate the Tab for configured custom attributes for the Multi-value group from the User module on the FORM BUILDER page.

  5. Custom attribute fields are displayed.

  6. Enter more than 45 characters' values into the field and Click SUBMIT.
    The data is displayed.
     
  7. Click SUBMIT and User details will be saved successfully. 

Steps: 

  1. Navigate to Incident > Manage Incident > Incident List. 
     
  2. Filter the incidents for Username/Caller (configured User from the User List page) 
    Incident List is displayed. 
     
  3. Click the Incident ID.
    Incident Details page is displayed.
  4. Click the hyperlink of Caller and verify.
    Caller Details pop-up is displayed.
  5. Navigate to configured custom attributes for the Multi-value group Tab under the General section.
    Verify the configured data. 

The configured data is displayed without any issue after the resolution. 

131557

When relating CIs with Services as part of Service Mapping, the IP Address attribute did not appear in the relationship mapping. 

 


Steps:  

  1. Navigate to CMDB > User > Manage Configuration Items > Services. 
    The Services List page is displayed. 
     
  2. Click the desired Service ID hyperlink. 
     
  3. Click CI Service Relationship option from the right panel. 
    CI Service Relationship DETAILS pop-up is displayed. 
     
  4. Verify the IP Address displayed in the diagram. 


IP Address is visible in the CI Service Relationship DETAILS pop-up without an issue after the resolution. 


Asset Management

Issue ID

Issue Description

Scenario

Resolution

130992

There was an error message displayed if the user enters the email id while raising an SR.

Prerequisite:

Create a field in Catalog form ‘Email’ control.

Steps:

  1. Create a Catalog with an Email field.
  2. In the new SR page, while raising a request, provide an Email value.

There is no error message displayed when the user enters the email id while raising an SR after the resolution.    

130669

The following issues were observed in Asset allocation and deallocation: 

 

Asset allocation: 

With Maker checker enabled, when an asset was allocated or deallocated for allocation to multiple users, the number of approvals displayed for the checker equaled the count of users it was allocated to.  
For instance, if an asset was allocated to 2 users in a multiple-user allocation, the checker displayed the approval process twice with identical data. Similarly, if the asset was allocated to 4 users using a multiple-user allocation, the checker showed the same data four times, including all four approvers. 

 

Asset deallocation: 

An Oops error was displayed during deallocation of asset when the wrong entry was selected. 

 

Steps: 

To enable the Maker checker for Allocation and Deallocation on Tenant configuration page, perform the following steps: 

  1. Navigate to Asset > User > Manage Assets > Approvals > Maker Checker approval. 
     

To allocate asset to multiple users, perform the following steps: 

  1. Navigate to Asset > User > Manage Assets > Asset Inventory. 
     
  2. Select Fixed Asset on Asset Inventory page. 
     
  3. Click the desired In-Store asset count hyperlink. 
    LIST page is displayed. 
     
  4. Select the desired asset checkbox(s) and click ALLOCATE option and perform the allocation action. 
     
  5. Verify the Asset ID displayed on Maker checker Approval page. 

To deallocate previously allocated assets, perform the following steps: 

  1. Navigate to Asset > User > Manage Assets > Asset Inventory. 
     
  2. Select Fixed Asset on Asset Inventory page. 
     
  3. Click the desired Allocated asset count hyperlink. 
    LIST page is displayed. 
     
  4. Select the desired asset checkbox(s) and click DEALLOCATE option and perform the allocation action. 
     
  5. Verify the Asset ID displayed on Maker checker Approval page. 


Maker checker approvals displays correct data without any duplicate values for asset allocation and deallocation after the resolution. 

130116

The Asset Deallocation date was not displayed in the deallocation email notification when the asset was reallocated. 

 

 


Prerequisite:  

  1. Enable Asset Allocation Alert End User Job on Custom Scheduler page. 

 

Steps: 

To perform asset deallocation, perform the following steps: 

  1. Navigate to Asset > User > Manage Assets > Asset Inventory. 
     
  2. Select Fixed Asset on the Asset Inventory page. 
     
  3. Select the desired Tenant from the drop-down, which is a mandatory field. 
     
  4. Click the Allocated count hyperlink. 
    The Fixed Asset LIST page is displayed. 
     
  5. Select the desired asset checkbox and click DEALLOCATE from the ACTIONS panel on the right. 
     
  6. In the record list, select the asset that was previously chosen and click SUBMIT. 
     
  7. The user will receive an Asset Deallocation email notification. 
    Verify the Deallocation date field in the email. 

 

To perform asset reallocation, perform the following steps:  

  1. Navigate to Asset > User > Manage Assets > Asset Inventory. 
     
  2. Select Fixed Asset on the Asset Inventory page. 
     
  3. Select the desired Tenant from the drop-down, which is a mandatory field. 
     
  4. Click the Allocated count hyperlink. 
    The Fixed Asset LIST page is displayed. 
     
  5. Select the desired asset checkbox and click REALLOCATE from the ACTIONS panel on the right. 
    The Reallocate Fixed Assets Details page is displayed. 
     
  6. Fill in the form with the required details and click SUBMIT. 
     
  7. The user will receive an Asset Deallocation email notification. 
    Verify the Deallocation date field in the email. 


The asset deallocation email notification displays the Deallocation date successfully without any issue after the resolution. 

132479

Users were able to view Asset Reconciliation Configuration and Location information on My Asset List (Reconciliation) page even though these options were removed from the Application Settings. 

 

 

 

 

 


Steps:  

To select the options on the Application Settings page, perform the following steps: 

  1. Navigate to Asset > Configuration > Others > Application Settings. 
     
  2. Select Configure by Tenant option in the ACTIONS panel. 
     
  3. Scroll down to find RECONCILIATION SETTINGS grid and select the desired options. 
     

To view Reconciliation details on My Asset List page, perform the following steps: 

  1. Navigate to Asset > User > Manage Assets > My Asset List. 
     
  2. Select Reconciliation option from the ACTIONS panel. 
    Asset Reconciliation List page is displayed. 
     
  3. Check and verify the grids displayed on this page. 


My Asset List page displays the options as per the configurations done on the Application Settings page without any errors after the resolution. 

Platform

Issue ID

Issue Description

Scenario

Resolution

131041

The configured Priority in Service Catalog was not displayed in the Service Request. 

Prerequisites:

  • Configure a Service Catalog with location drop-down attribute.

  • Select the Enable Conditional Service Request Value check box.

  • Configure Condition Section for the Location Attributes.

  • Configure Approver Catalog and Publish the Catalog.

Steps:

  1. Log in to the Summit Application.

  2. Raise a SR with the configured Catalog.

  3. SR moves to the Pending for approver.

  4. Select the configured Location in the approval step.

  5. View the Priority displayed for the selected location.

The Priority configured in the Service Catalog successfully appeared in the Service Request.

131924

In the API response of service "IM_GetIncidentDetailsAndChangeHistory" it was observed that tags were received too. 

When the content from the User Communication tab was saved from UI or from APIs, the HTML tags were displayed along with content. 

A fix is applied, and the HTML tags won’t appear now.  


Agentless Discovery

Issue IDIssue DescriptionScenarioResolution
132626

Discovery was not working as email ID was not present for the user. 

Steps: 

  1. Configure a Discovery job for user.  
     
  2. Run the Discovery job and verify if it is functioning correctly.
     
  3. Navigate to Discovery > List. The List page displays the Status of the Discovery Job appropriately.

Note: The user initiating the Discovery job must provide an active Email ID to receive notifications.

Discovery works appropriately after the resolution. 


Known Issues 

This section describes the known issues detected by the Summit 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).