Customer Fixed Issues and Known Issues Tahoe SP3 HF08

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

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

Customer Fixed Issues 

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

Service Management

Issue ID

Issue Description

Scenario

Resolution

115501The Change Category field for the cloned CR was disabled and the Analyst was unable to select any change category during CR creation.

Prerequisites:

  1. Enable the checkbox Change Category Field Visible For CR.

  2. CR should be in Initial Authorization status.

Steps:

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

  2. Select the required CR in Initial Authorization status. The Change Record details page is displayed.

  3. Click Clone CR under ACTIONS > Clone CR. The Clone CR pop-up page is displayed. Select required checkbox and click Clone.

  4. Observe the Change Category field for the cloned CR.
The Change Category field for the cloned CR is enabled and the Analyst is able to select any change category during CR creation.
116110The system was unable to download the file with .msg extension.

Prerequisites:

  1. Navigate to Change > Change Record List. The Change Record List page is displayed.

  2. Click the required CR ID. The CR details page is displayed.

  3. Attach a file with.msg extension. Click Submit.

  4. Navigate to the Action panel > Attachment. The Attachment pop-up is displayed. Download the .msg file.
The system can download the file with .msg extension.
112842In the CMDB BI report few CIs are not listed. Workgroup updated for the CIs is visible on the UI however it is not visible in the DN tables.  

Prerequisites:  

  1. Summit Admin should configure the table “summit_config” and assign the specific Workgroup ID and Workgroup Owner ID. 

Steps: 

  1. Log in to Summit Application. 

  2. Navigate to Operations > Servers > Server List > Add New. Add new server and verify respective CI in CMDB. CI should have Owner Workgroup and Owner fields updated. 

  3. Navigate to Operations > Network > Edit View > Add Network Device/ Network Link/Server and verify respective CI in CMDB. CI should have Owner Workgroup and Owner fields updated. 

  4. Navigate to Operations > Views > Common Device View. While adding A New Device or A New Link, the Owner and Owner Workgroup details should reflect respective CMDB CI. 

After configuring the Owner Workgroup  and Owner in the “Summit_config” table as default values for CI’s, created from ITOM module, the Owner Workgroup and Owner details are visible in CI’s when new CIs are created from ITOM module.  

To view the SQL Server Script, click on Expand Source. 

SQL Server Script 
SELECT wg_Id,* FROM IM_WorkGroup_Master with(nolock) 

SELECT UserID, * FROM User_Master with(nolock) 

 
IF NOT EXISTS(SELECT 1 FROM Summit_Config with(nolock) WHERE Module_Code = 'AVM' AND Config = 'CI:ServerDefaultWorkGroupID') 
BEGIN 
    INSERT INTO Summit_Config (Org_ID,Config,Config_Val,Module_Code,Discription,UpdatedDate,UpdatedBy,Active) 
    VALUES(1,'CI:ServerDefaultWorkGroupID',1,'AVM','Server Default workGroupID while creating CI from AVM',GETUTCDATE(),1,1) 
END 
GO 

IF NOT EXISTS(SELECT 1 FROM Summit_Config with(nolock) WHERE Module_Code = 'AVM' AND Config = 'CI:NWDDefaultWorkGroupID') 
BEGIN 
    INSERT INTO Summit_Config (Org_ID,Config,Config_Val,Module_Code,Discription,UpdatedDate,UpdatedBy,Active) 
    VALUES(1,'CI:NWDDefaultWorkGroupID',1,'AVM','Network Device Default workGroupID while creating CI from AVM',GETUTCDATE(),1,1) 
END 
GO 

IF NOT EXISTS(SELECT 1 FROM Summit_Config with(nolock) WHERE Module_Code = 'AVM' AND Config = 'CI:NWLDefaultWorkGroupID') 
BEGIN 
    INSERT INTO Summit_Config (Org_ID,Config,Config_Val,Module_Code,Discription,UpdatedDate,UpdatedBy,Active) 
    VALUES(1,'CI:NWLDefaultWorkGroupID',1,'AVM','Network Link Default workGroupID while creating CI from AVM',GETUTCDATE(),1,1) 
END 
GO 

IF NOT EXISTS(SELECT 1 FROM Summit_Config with(nolock) WHERE Module_Code = 'AVM' AND Config = 'CI:ServerDefaultOwnerID') 
BEGIN 
    INSERT INTO Summit_Config (Org_ID,Config,Config_Val,Module_Code,Discription,UpdatedDate,UpdatedBy,Active) 
    VALUES(1,'CI:ServerDefaultOwnerID',1,'AVM','Server Default Owner ID while creating CI from AVM',GETUTCDATE(),1,1) 
END 
GO 

IF NOT EXISTS(SELECT 1 FROM Summit_Config with(nolock) WHERE Module_Code = 'AVM' AND Config = 'CI:NWDDefaultOwnerID') 
BEGIN 
    INSERT INTO Summit_Config (Org_ID,Config,Config_Val,Module_Code,Discription,UpdatedDate,UpdatedBy,Active) 
    VALUES(1,'CI:NWDDefaultOwnerID',1,'AVM','Network Device Default Owner ID while creating CI from AVM',GETUTCDATE(),1,1) 
END 
GO 

IF NOT EXISTS(SELECT 1 FROM Summit_Config with(nolock) WHERE Module_Code = 'AVM' AND Config = 'CI:NWLDefaultOwnerID') 
BEGIN 
    INSERT INTO Summit_Config (Org_ID,Config,Config_Val,Module_Code,Discription,UpdatedDate,UpdatedBy,Active) 
    VALUES(1,'CI:NWLDefaultOwnerID',1,'AVM','Network Link Default Owner ID while creating CI from AVM',GETUTCDATE(),1,1) 
END 
GO
116454The download file from Attachments under right hand side action panel shows different name than the attached one in all other related places.

Steps:

  1. Navigate to Change > Change Record List. The Change Record List page is displayed.

  2. Open the desired CR ID. The CR details page is displayed.

  3. Navigate to the Attachment field and attach file type.

  4. Click Submit.

  5. Navigate to Attachment under the actions panel. The Attachment pop-up page is displayed.

  6. Download and verify the attachment section of tab and the attachment popup from right side action panel.
The download file from Attachments under right hand side action panel shows same name as the attached one in the task implementation and relationship.  






116619On the Incident List page, for Incidents logged by End User using rules, Description column was not getting displayed.

Steps:

  1.  Select Request > User > Manage Service Requests > Service Request List. 

  2. On the SERVICE REQUEST LIST page, you can view all the SRs that belong to your Workgroup.

  3. You can view the SRs in the Tabular view.

  4. Click in Description column to view the Subject and Description of a Service Request in a pop-up page.
The Description column displays in the Tabular view of SERVICE REQUEST LIST page properly after the resolution.
115966Location field data on the SR was displaying incorrectly for end users and analysts.

Steps:

  1. Navigate to Catalog > Create Service Catalog. Select the Category and enter the Category Name. Other required details need to be entered as well.

  2. Click Next. On the Form Builder page, drag and drop the Dropdown list. Rename the Dropdown list to <user_defined_location_name>. Scroll down on the right panel select Auto Populate, and Editable option.

    set Dependent Attribute to Required and Value Attribute to Location.

  3. Click Next. On navigating we observe that the Dropdown list will be empty. Click Next and SAVE.

  4. On the ACTIONS panel, click Publish and set the Approval Status to Publish.

  5. Request > New Service Request > select Tenant > select the above published Catalog.

  6. Location on Dropdown will be displaying the default value same as location on MY PROFILE. 

  7. Change the Location and click Submit.

  8. Navigate to Request > My service Request > Click on generated SR ID and scroll down.

  9. On the default group, Location dropdown list, the user entered value can be seen.

Location field displays data as entered by user.

120359Users were experiencing, “Oops! An error occurred.” message on opening the SR list page.

Steps:

Navigate to Request > Service Request List.

SR list page opens without any error message.
116780For the new CMDB CI bulk uploads, on the Change History table, details in the Column Name were incorrect. Instead of attribute name, attribute Id was displayed.

Steps:

  1. Navigate to CMDB > Import > Import Configuration Items.

  2. On the General properties, choose Import Type to Add and enter other required fields.

  3. Select the file and Click Submit.

  4. Navigate to CMDB > Configuration Item List.

  5. Select CI NO and click Change History on the right panel.

  6. Verify the Column Name.
Column Name on the Change History updates correctly for the newly created CMDB CI bulk uploads.
116780The SLA by workgroup report displayed Workgroups that were not selected in the FILTERS.

Steps:

  1. Navigate to module Reports > Service Request > Reports > SLA By workgroup report.

  2. Click RESPONSE tab.

  3. Click FILTERS and select Tenant.
  4. Select Workgroups and change date range.

  5. Click SUBMIT.
The report SLA by Work Group report displays only selected Workgroups on the FILTERS.
115517In CR Creation page, when the User changed the Risk value from High to Low, the Risk tab fields were remaining mandatory with asterisk symbol.

Prerequisites:

  1. Navigate to Change > Risk > High.

  2. Set High risk as True.

  3. Create a CR for High risk.


Steps:

 

  1. Navigate to Change > User -> Change record list.

  2. Select the desired CR created for High risk.

  3.  Change the Risk value to Low.

  4.  Verify the Risk tab. Check if Risk tab fields were remaining mandatory with asterisk symbol.
The Risk tab field works appropriately when Risk value is selected as Low and asterisk symbol is not appearing in the related attributes.
115109Incident Management Sort Order for Category not working.

Steps:

  1. Navigate to Incident > Configuration > Incident Masters > Category.

  2. On the right-side ACTIONS tab choose SORT ORDER.

  3. In the box displayed, choose Alphabetically and Click SUBMIT.
Sort order for Category is working after the resolution. 
116967In the standard report under the Incident Dashboard, previous incorrect data(tickets) was displayed when the previous month filter option was selected. 

Steps: 

  1. Navigate to Reports > Incident Management > Incident Dashboard. 
     
  2. Click FILTERS icon. 
     
  3. Select the desired Tenant from the drop-down, which is a mandatory field. 
     
  4. Select previous month from Month drop-down. 
    Click SUBMIT. 
     
The standard report under Incident Dashboard displays proper data for previous month filter options after the resolution. 

113736

Unable to import category for bulk updating of the category for Incident. It was displaying the following error: "Excel contains invalid data."

Steps:

  1. Navigate to Incident > Configuration > Incident Master > Category.

  2. On the ACTIONS menu click Import. 

  3. Upload the excel file and click SUBMIT. 

It supports only to import or create new root node and its child(s) and cannot add a new child to an existing node.

120359SR approvals received through the email were not getting approved if the email had the custom header with the CAUTION text.

Pre-requisites:

  1. Mailbox should be configured, and for Notification Parser, SR approval by Email should be selected. and the respective job should be run.

  2. Create a Catalog with one level approver on Workflow.

  3. Add the custom header CAUTION text value to the servermonitor.exe


Steps:

  1. Navigate to Request > New Service Request.

  2. Select the created Catalog and Submit the SR.

  3. Approver should approve the Service Request Approval Email.

  4. An approved notification email with CAUTION text as defined on the server monitor configuration will be displayed.

Note:

Need to add the below key in Server Monitor Configuration.
<add key="MailBody:RemoveCautionText" value="" />

SR approvals received through email are getting approved, even if it has a custom header with CAUTION text.


Asset Management

Issue #

Issue Description

Scenario

Resolution

117119In the Software Details allocation section, the store information displayed was improper.

Steps: 

  1. Navigate to Asset > User > Manage Assets > Asset Inventory. 
     
  2. Select Software Asset on the Asset Inventory page. 
     
  3. Select the desired Tenant from the drop-down, which is a mandatory field. 
    The Software Details page is displayed. 
     
  4. Select the desired Total count hyperlink for the particular store. 
    The Software Details summary pop-up is displayed. 
     
  5. Verify the name of the asset stores displayed. 
Software Asset Details summary displays the proper store information after the resolution. 
115136

User received Asset Not Contacted alert for Inactive, In-Store, and Allocated Asset category. 
 
NOTE:
Asset Not Contacted alert should trigger only for Allocated and In-Store assets that are not contacted for more than defined days. 

Steps: 

  1. Navigate to Admin > Basic > Infrastructure > Custom Scheduler. 
     
  2. Enable the job Send Notification for Not Contacted Assets. 
     
  3. Verify Summit_Email_queue table and verify the email body. 

 

Asset Not Contacted alert is triggered only for Active and In-Store Assets after the resolution. 
114671

The Accept and Reject button was not present in the Asset Reconciliation Alert email. 

This issue occurred when there was only one asset in the alert email.

Steps: 

To configure the alert email, perform the following steps: 

  1. Navigate to Admin > Basic > Infrastructure > Custom Scheduler. 
     
  2. Configure Asset Reconciliation Alert job and run it. 
     

To approve the alert job, perform the following steps: 

  1. Navigate to Admin > Advanced > Notifications > Notification Parser. 
     
  2. Click ADD NEW from right ACTIONS panel. 
    Notification Parser configuration page is displayed. 
     
  3. Under CONFIGURE PARSING CONDITIONS grid, click APPROVE tab. 
     
  4. Select the Enable End User Asset Reconciliation Acceptance by Email checkbox. 
    Click SUBMIT. 
     

To reconcile the assets, perform the following steps: 

  1. Navigate to Asset > User > Manage Assets > Asset Inventory. 
     
  2. Select Fixed Asset type on the Asset Inventory page. 
    The Fixed Asset List page is displayed. 
     
  3. Click the desired Allocated assets count hyperlink. 
     
  4. Select the checkbox(s) of desired assets.  
    Click Reconciliation option from the right ACTIONS panel and reconcile the assets. 
     

Alert email received by user:

  1. Open the Asset Reconciliation alert email received by the user. 
     
  2. Verify the Accept/Reject buttons. 
     
The Accept and Reject button in Asset Reconciliation alert email is present for one asset and works fine after the resolution. 


Platform

Issue #

Issue Description

Scenario

Resolution

118770In the CMDB CI RELATIONSHIP Details page, users were unable to select the checkbox under Relations dropdown. 

Steps:  

  1. Navigate to CMDB > User > Manage Configuration Items > Configuration Item List> Click the CI NO.  
     
  2. Click on RELATIONSHIP under the ACTIONS Panel. RELATIONSHIP Details page is displayed.  

  3. Click on Relations dropdown and verify if the checkbox is selectable.  
Users can select the checkbox under Relations dropdown in CMDB CI RELATIONSHIP Details page.  
117750

When CR is approved using Mobile App, CR Approval is getting skipped.

Individual Approval Type

Prerequisite:

  1. Create a CR having Individual Approval Type with Mandatory approvers in workflow.

Steps:

  1. Approve the CR using few/all approver IDs which are mandatory approver via Mobile API serviceName – CM_LogorUpdateCR.

  2. Navigate to web app and check approval level and check approval level status and status of approvers who approved CR via API for Individual approval/mandatory approvers in workflow of CR.

 

CAB Approval Type

 Prerequisite:

  1. Create a CR having CAB Approval Type with Mandatory approvers in workflow.

 Steps:

  1. Approve the CR using few/all approver IDs which are mandatory approver via Mobile API serviceName – CM_LogorUpdateCR.

  2. Navigate to web app and check approval level and check approval level status and status of approvers who approved CR via API for Individual approval/mandatory approvers in workflow of CR.
Approval using Mobile App does not get skipped after the resolution.
115266Configured Notification Parser was not creating a Service Request for the POP3 mailbox. 

Prerequisites:

 In the SymphonyAI summit application configure POP3 Mailbox-gmail.com and LOG a SR notification parser for the mailbox. 

 Steps: 

  1. Send a mail to the respective mailbox. 
     
  2. In the customer scheduler run the respective job. 
Service Requests is creating as per the configuration of the Notification Parser page. 
114979In the Incident Feedback Report, was sending blank data into the spreadsheet via email.  

Steps: 

 Log in to the Symphony AI Summit application. 

  1.  
  2. Navigate to the Reports > Incident Management > Incident Feedback Report. 
     
  3. Click Push Report from the left panel. 
     
  4. Configure and schedule the Push Report to send excel via  email. 
The configure Push Reports are sending a spreadsheet with data as designed. 
119687An error message ‘Error loading OLA detail’ was displayed when configuring an OPERATIONAL LEVEL SPECIFICATION (OLS).

Steps:

  1. Log in to the SymphonyAI Summit application.

  2. Navigate to the SLA > Operational Level > New Operational Level Specification.

  3. Enter the required details and click SUBMIT.

  4. Navigate to OLS List page, Open the newly created OLS.

  5. Updated the required details and click SUBMIT. 
You could configure and update an OLS without any errors. 
117750In the SymphonyAI Mobile App, when approving a CR, the CR was getting approved and moving to the next level, skipping the other mandatory approvers.

Prerequisite: 

Create a CR having Individual Approval Type with Mandatory all approvers (Approver 1, Approver 2, and Approver 3) in workflow.

 Steps:

  1.  Log in to the SymphonyAI Mobile App.

  2. Click Approve Change Records.
  3. Select the required CR to approve.
  4. Click 3dots from the CR Details page.
The CR is moving to next level after approving all the configured mandatory approvers without any issue.


Known Issues 

This section describes the known issues detected by the SummitAI Dev and QA team in the release, Tahoe SP3 HF08 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).