| 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 << Tahoe SP3 HF15

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

Customer Fixed Issues

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

Service Management
Asset Management
Platform
Service Automation

Service Management

Issue ID	Issue Description	Scenario	Resolution
131789	The Reporting Manager was not getting updated for the existing users.	Prerequisites: Navigate to Admin > Users > Import > AD Import. The AD Import list page is displayed. Verify Manager under Attribute Details section. Run (Admin > Infrastructure > Custom Scheduler. Select Job Options as Import AD Users. Observe Reporting Manager name (Admin > Users List).	The Reporting Manager is getting updated for the existing users.
131775	The Log Time and Catalog Attachment timings were different on Service Request details page.	Prerequisites: Create a catalog with an attachment. Change the time zone of the logged in user (Edit Profile > My Profile > Time Zone). Steps: Raise an SR with above created catalog with an attachment. Verify the Log Time and Catalog Attachment timings on Service Request details page.	The Log Time and Catalog Attachment timings are not different on Service Request details page.
132485	After submitting the PIR, the count was not getting removed from the Thumb icon.	Prerequisites: At Tenant level select Auto in the Change Request Closure drop-down. Select None in the PIR Configuration for Tasks drop-down. Steps: Navigate to Change > New Change Record. Create a new CR (in implemented state). Check the PIR Required checkbox in Approval pop-up under Action Panel. Click Submit. Click Approvals icon on Change Record Verify the Change Record Pending for PIR Click PI Review under Action Panel and submit the PIR. Observe the Approvals icon .	After submitting the PIR, the count is getting decreased from the Thumb icon.
129267	Auto Resolved Incidents were not displayed in the Resolved Tickets List.	Prerequisites: Auto Resolve incident should be configured (3 reminders). Alert should be configured. Priority should be Resolution SLA as '0'(P5). Auto Resolve jobs should be running & completed. Steps: Login to the application. Navigate to Incident > Manage Incidents > New Incident for Users Enter all the mandatory details (select the priority as P5). Click Submit. Access the Incident by clicking Incident ID and move the Incident to Pending.	Auto Resolved Incident gets displayed in the Resolved Tickets List.
133391	When End Users were trying to open the Workorder, they were getting an Oops error and respective work order details were not getting loaded. The page was redirecting to a new WO page with the username as a Caller of the Workorder.	Prerequisites: Configure a catalog without any approval levels & publish the catalog. Configure Workorder - Catalog mapping for catalog. Steps: Login to application. Change to desired language by using Language icon. Raise an SR. Navigate to Request > Service Request List. Click SR ID. Service Request Details page gets displayed. Click Workorder ID under Relationship tab on the Service Request Details page. On the Workorder Details page update the status to Resolved status verify the Solution & Closure code fields.	Workorder page works appropriately after the resolution.
132807	Analyst was facing issue with the work order notifications, as SOURCE field values were not displayed in the notification.	Steps: To check the status for Workorder notification templates in SR Module, perform the following steps: Login to application. Navigate to Request >Service Request List. Click SR ID. Now create a Workorder under Relationship tab in Service Request Details page. Check the triggered Workorder notification templates. The SOURCE field is getting displayed. To check the status for Workorder notification templates in IM Module, perform the following steps: Login to application. Navigate to Incident > Incident List. Click Incident ID. Now create a Workorder under Relationship tab on Incident Details page. Check the triggered Workorder notification templates. The SOURCE field is getting displayed.	The SOURCE field value gets displayed in the email notification after the resolution.
131231	Analyst was facing an issue Copy Incident functionality.	Steps: Navigate to Incident > New Incident. Click Copy Incident icon. Select any Incident from Select from recent 50 Incident dropdown list.	Analyst is not facing with Copy Incident functionality.
132070	When trying to fetch View all Work Order using Filters for the Work Order List, the user was experiencing a webpage error. Note: Issue was occurring only when huge data was fetched.	Steps: Log in to the application with the valid credentials. Navigate to Incident > User > Manage Incidents > Work Order List. Click Filter on the right side of the page. Enter the required value. Click Apply.	Webpage error is not seen upon filtering Work Order List.
133739	Users were not able to add more than 1000 characters in the Other E-Mail IDs text area box.	Steps: Log in to the application. Navigate to Incident > Configuration > Others > E-mail Notification. Select Tenant. Select Workgroup. Add more than 1000 characters in the Other E-Mail IDs text area box. Click Submit.	Users can add more than 1000 characters in the Other E-Mail IDs text area box.
134173	Few new joined users were not created in the application tool automatically when imported from Excel.	Precondition: CSV will be in Pending Folder. Run UserImport_csv Job. Users will be imported to summit application. CSV file will be moved to Completed Folder. Steps: Navigate to Admin > Basic > Users > User List. Validate the user data. The manager column was not mapped in the web config file, after updating the below key CSV Import is working as expected. <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" /> For mapping manager column use EmpID as primary key in the summit_config table. Query:   Update Summit_Config SET Config_Val = 'EmpID' where Config = 'CSVUserImport_PrimaryKey'	Users are created on the application tool without any issues.
130102	When the SRs were bulk updated to the Resolved status, the Subject of the email was not the same. The email Subject content was not displayed in the Japanese language.	Steps for 1: Log an SR. Navigate to the Analyst SR List page. Select the SR. Click on the Bulk Update icon in the Actions panel. In the popup select status as Resolved. Provide remarks and enter the required details in the appropriate fields. Click submit. Check the status of the email. Steps for 2: Update/create mail template/NOTIFICATION TEMPLATE in the Japanese language which is configured for resolved SR status. Log an SR. Navigate to the Analyst SR List page. Select the SR. Click on the Bulk Update icon in the Actions panel. In the popup select status as Resolved. Provide remarks and enter the required details in the appropriate fields. Click submit. Check the status of the mail.	The email subject displays the same upon manual and bulk resolution. The email subject displays in the Japanese language.
132709	When the reopened SR was resolved the SLA Deadline was breached.	Steps: Log in to the application. Navigate to Request > User > Manage Service Requests > New Service Request For User. Create SR. Navigate to Request > User > Manage Service Requests > Service Request List. Select created SR. Note the SLA Deadline. Change the SR Status to Resolved. Change the SR Status to Reopen. After a few minutes change the status of the CR to Resolved. Validate the SLA Deadline.	SLA Deadline does not breach when the Resolved SR is Reopened.
133420	Resolved/Closed Incidents were not able to be linked to the Problem Record.	Steps: Navigate to Problem > User > Problem Record List. Click the specific record and go to the Record detail page. Go to the Relationship tab. Click the link and add the Resolved/Closed Incident record.	Resolved/Closed Incidents can be linked to the Problem Record after the resolution.
132374	Validation control is not working for Change Management.	Steps: Navigate to Admin > Infrastructure > Form Builder. Select Change Management. Select the Tenant > Click Add icon under the Actions panel. Select the desired Display At value from the Display At drop-down. Click Next. Drag and drop Group control onto Form Builder. Drag and drop the Drop-down control under the Group. Give the Label name and enable the Required check box and configure the drop-down value. Drag and drop the Dropdown control under the Group. Give the Label name and uncheck the check box of Required. Click Next > Click Save. Again, access the same form. Click Validate Controls under the Actions panels. Click Add icon. Add the conditions with ‘OR’ operator. Configure the Validate Control. Navigate to Change > New Change Record. Select the same Tenant. Select other field values.	Validation control is working successfully for Change Management.
132775	Existing VIP User details were getting updated in a different tenant and were not present in the previously selected tenant.	Steps: Navigate to Incident > User Type > Select a VIP User of any tenant. Copy the User details and paste it to an Excel sheet. Navigate to a tenant other than the selected tenant. Click Import Master > General Section > Upload the User detail file. Click Submit. Click Select. Verify the source details – User Type and Email ID. Click Next. Click Bulk Upload. Navigate to the selected tenant. Access the VIP User.	Existing VIP User details are present in the selected tenant and are not getting updated in a different tenant.
134142	While submitting a new Workorder and opening the same Workorder, there was an error - “Oops an error occurred”.	Steps: Navigate to Incident > Manage Incidents > New Workorder. Fill in all the details. Click Submit.	The Workorder is successfully getting submitted without showing any error.
132486	On the service request details page, the log time of the SR and the catalog attachment time are different.	Prerequisites: Create an SR catalog with file attachment controls. Save and publish the catalog. Change the time zone for the logged-in user. Raise a Service Request, upload attachments, and submit the SR. Steps: Navigate to Request > Service Request list. Select the created SR from the list. The service request details page is displayed.	The log time of the SR and the catalog attachment time on the Service request details page is the same.
134127	When an SR catalog is created with an attachment and mandatory approval, if the end-user attaches a blank attachment, the file is not displayed after submitting the SR. If the end user attaches a non-empty file, the name of the file displays after submitting the SR.	Prerequisites: Create an SR catalog with file attachment control. Make the control as non-mandatory. In the Workflow, configure an approver for the catalog. Create validation control in the catalog. Save and publish the catalog. Steps: Login to the Summit application as an Analyst. Navigate to Request > New Service Request for User. Create a new SR with the above catalog. Attach an empty file to the SR. Attach a non-empty file to the SR.	If the end user attaches an empty file, there is a validation message stating empty file cannot be attached.
133988	In the SR list page Behalf of the username is displayed as logged by username and logged by username is displayed as caller name.	Prerequisites: Create an SR catalog. Steps: Login to the Summit application as an Analyst. Navigate to Request > New Service Request for User. Select the on behalf of user from the search field. Create a new SR.	In the SR list page Behalf of the username is displayed as the caller name and logged by displays the actual logged-in username.
130235	Switch between different tabs in the Executive Dashboard to view the reports, even if the dashboard is still loading.	Steps: Navigate to Dashboard > Executive Dashboard. Switch between the different tabs to view the reports.	The dashboard displays the message ‘Patience requested until the tab has completed loading’ when switching between different tabs while the dashboard was still loading. Switch between the different tabs in the Executive Dashboard after it is completely loaded.
133941	Issue 1: Invalid Problem Reviewer (RCA Approver) was showing as a Problem Reviewer. Issue 2: Problem Record status was changing to Reviewed even when user was not configured as Reviewer.	Pre-requisite: Ensure that a Server Monitoring Job is already running. Steps: Navigate to Problem > Configuration > Approver > Configure a user as an Approver to a specific Workgroup (Workgroup 1). Navigate to Problem > Configuration > Reviewer > Configure a user as a Reviewer to a specific Workgroup (Workgroup 1). Configure the Email Parser and Mailbox > Enable Approve Problem Record via mail option in the Mail Parser Configuration. Navigate to Problem > User > New Problem Record > Create a Problem Record in the same Workgroup 1. Navigate to Problem > User > Problem Record List > Open the Problem Record created > Authorize the Problem Record and Submit the RCA. Approve the Problem Record (PR) via Email > Send email from the Problem Record Approver email id. Send an email from PR Approver email id again. Send an email from Reviewer email id, to review the PR.	The correct Problem Reviewer are now showing, and the status does not change to reviewed when user not configured as Reviewer.
130981	While creating an Incident using a Category having a special character, some of the tabs like Additional Information tab and Vendor Information tab were missing.	Pre-requisite: Create a category with special character. Steps: Navigate to Incident > User > Manage Incidents > New Incident for Create an Incident and choose a Category with a special character. Navigate to Incident > User > Manage Incident > Incident List. Click the Incident Id of the Created Incident and verify if the tabs are present.	The Additional Information and Vendor Information tabs are displaying while creating an Incident under a Category having a special character.
130925	The user experienced slowness and time-out error under the CMDB module on the following pages: Configuration Item List CI Details page Reports CIs by Attribute Report CI Status Report	Steps: Navigate to CMDB > User > Manage Configuration Items > Configuration Item List. Click the desired CI ID hyperlink. CI Details page is displayed. Check and verify the data displayed under the CI Relations, Version History, and Relationship (Relationship diagram and export to Excel option) tabs. Navigate to Reports > CMDB. Check and verify the following reports: CIs by Attribute Report and CI Status Report.	CMDB module pages load successfully without any slowness or time-out errors after the resolution.
129560	To introduce an option to disable incident creation for mail to the ticket using config key.	Steps: Add the below-mentioned key in the following location: <add key="MailParserAllowNewIncident" value="false" />  Jobs>>Server Monitor >> App.config	The incident creation will be disabled after adding the key but updating the incident can be done successfully after the resolution.

Asset Management

Issue ID

Issue Description

Scenario

Resolution

134120

The Form Builder page for IT Asset Management module had a loading issue.

Steps:

Navigate to Admin > Basic > Infrastructure > Form Builder.
Click Add New to create a new configuration.
Create a category with 2 dropdowns (Dropdown1, Dropdown2)
Dropdown1 should be the parent to Dropdown2.
Using Import Values in the Import Asset page and import around 1000 values for each dropdown.
Navigate to Form Builder page and the open above-created category. Click the dropdown and verify.

Step for Administrator:

AM_CtAttribute_No_Edit flag should be updated to 1 for desired attributes which holds large record list values.
For example:
update AM_CategoryAttributes set AM_ctAttribute_No_Edit= 1 where AM_CtAttribute_ID in (1142,1141) and AM_Category_ID=267.

The Form Builder page for IT Asset Management loads fine without any issues after the resolution.

Platform

Issue ID

Issue Description

Scenario

Resolution

131166

When raising or updating the SR ticket, duplicate tickets were generated.

Steps:

Log in to the Summit Application.
Navigate to Request > User > New Service Request.
Enter the required details and click Submit.

The SR ticket proceeded without generating any duplicate tickets.

133803

In the Problem Management module, question marks were inserted instead of the Thai language characters.

Steps:

Log in to the Summit Application.
Navigate to Problem > New Problem Record.
Enter the multi value details and click Submit.
Configure a Service Catalog with location drop-down attribute.

The Thailand language characters were successfully inserted without any issues.

Service Automation

Issue ID	Issue Description	Scenario	Resolution
136185	In the old Orchestration framework under Orchestration trigger, when the module was selected as Work Order and the source as Service Request, the AutoWorkOrder field was a mandatory option. Due to this, the orchestration was only linked to the work orders created from templates and not to those created from APIs.	Steps: Navigate to Admin > Advanced > Automation > Orchestration. In the Orchestration configuration page, select the following options: Module – *Work Order Work Order Source* – *Service Request* Service Catalog – *Select any desired option* Auto Work Order Name *– None (empty)* Click SUBMIT. Create a Work Order through API. Verify whether the Work Order created through API is linked to this Orchestration.	The Orchestration trigger links to Work Order created through APIs successfully without any issues after the resolution.

Issue ID

Issue Description

Scenario

Resolution

136185

In the old Orchestration framework under Orchestration trigger, when the module was selected as Work Order and the source as Service Request, the AutoWorkOrder field was a mandatory option.

Due to this, the orchestration was only linked to the work orders created from templates and not to those created from APIs.

Steps:

Navigate to Admin > Advanced > Automation > Orchestration.
In the Orchestration configuration page, select the following options:
Module – Work Order
Work Order Source – Service Request
Service Catalog – Select any desired option
Auto Work Order Name – None (empty)
Click SUBMIT.
Create a Work Order through API.
Verify whether the Work Order created through API is linked to this Orchestration.

The Orchestration trigger links to Work Order created through APIs successfully without any issues 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: Log in to the SummitAI application as an Approver. Navigate to Request > Service Request List. 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.
100781	When 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
100796	The ‘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
100798	The 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
100813	The 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 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). 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). 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: Login to the Application as Checker. Click Asset > User > Manage Asset > Approvals Maker-checker Approval > Click Filters on the ACTIONS panel. On the Filter pop-up page, select the Tenant and specify the required details. Select the Assets that you want to approve and click APPROVE icon on the ACTIONS The APPROVE pop-up page is displayed. On the APPROVE pop-up page, select the Approval Status as Approved to approve the Asset and click Click Asset > User > Manage Asset > Asset Inventory > Click FIXED under the SELECT THE ASSET TYPE section > Click Filters on the ACTIONS On the Filters pop-up page, select the Tenant, Select the Status as Allocated and specify required details. Click SUBMIT. 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: Log into the Application as an Administrator. Configure a Bulletin Board. For more information, see Configuring Bulletins. Send a POST request for the GetBulletinBoard API. Pass Tenant Code, in the Instance parameter and User ID in the UserID parameter. 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: Log into the Application as an Administrator. Select Admin > Advanced > Automation > Orchestration. On the WORKFLOW LIST page, click the NEW On the WORKFLOW CONFIGURATION pop-up page, select Module as Service Request, and specify other details to configure the Orchestration Workflow. Map the Target Host Type to From Previous Output value for the scripts of the Orchestration Workflow. Log out and log into the Application as an Administrator or as an Analyst. Select Request > Manage Service Requests > Service Request List. On the SERVICE REQUEST LIST page, specify the Filters and open an SR. On the SERVICE REQUEST DETAILS page, click the ORCHESTRATION tab. 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. 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: Select Asset > User > Manage Asset > Import > Import Asset. On the IMPORT ASSET page, under GENERAL tab, select the required options and upload the updated Asset Import Template. Click SUBMIT. Select the sheet to import the Assets. Click the Mapping tab and select the required options if not already selected. Click Next. Click the Preview tab and select the store where you want to import the Assets from the Store list. Click IMPORT ASSETS TO QUEUE on the ACTIONS panel. 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. Add two Assets with same Serial Number. The Application allows to import or add two Asset with same Serial Number. 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. 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).