Hotfix Merges

The following Hotfix versions are merged with this release. Please refer to the respective Release Notes for details.

Hotfix Releases from Dec 2021 to Feb 2022 are merged with Tahoe SP3 HF01.

Customer Fixed Issues

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

Service Management

Issue #	Issue Description	Scenario	Resolution
101767	While updating the incident based on Priority matrix configuration, the priority was not getting updated using IM_LogOrUpdateIncident API.	Prerequisites: Navigate to Incident > Manage Incidents > Incident List. The Incident List page is displayed.	Now, while updating the incident based on Priority matrix configuration, the priority is getting updated using IM_LogOrUpdateIncident API.
100283	The default fields were getting displayed instead of the configured fields.	Prerequisites: Configure a rule (Incident > Configuration > Others > Rule). Navigate to Incident > Configuration > Incident Masters > Log Incident Page. The LOG INCIDENT PAGE is displayed. Select the required Tenant. Select Customer as ALL on CONFIGURE FIELDS Select the required fields from the grid. Click SUBMIT. Navigate to Incident > Users > New Incident. The New Incident Details page is displayed. Enter the keyword in the Symptom field. Select the required rule from the list displayed.	The configured fields are getting displayed as expected.
102802	The Standard Templates were not displayed in the Standard Import Template pop-up on the New Change Record page. This issue occurs, if the user creates the standard templates under the Custom Category for the Small Source Category.	Prerequisites: Configure Custom Category under Small Source Category for required tenant level. Configure a Standard Template for configured Custom Category under Small Source Category, and it should be Approved. Steps: Navigate to Change > User > New Change Record. Select the Tenant. Select the Owner Workgroup. Select the Change Type as Standard. Verify the Category field in the Import Standard Template pop-up displayed.	The Standard Templates created under the Custom Category for the Small Source Category are displayed in the Standard Import Template pop-up on the New Change Record page.
97885	The Logged On column on the Knowledge Record List page displayed IST time instead of UTC.	Steps: Navigate to Knowledge > User > Knowledge Record List. View the Logged On column.	The Logged On column on the Knowledge Record List page displays the time in UTC.
102035	The Post Resolution Approval functionality in Incident Management has the following issues and are noticed in the received e-mail notification: The status of the Pending Approval ticket is displayed as Resolved. The Approval Date column is blank in the Approval Table. Approver Name and Approval Remarks columns are not displayed in the Approval Table. Approver Name is displayed only if single Approver is configured. Instead of ‘Pending for Approval’ status the Custom status was displayed in Approval Table, even if the incident was pending for approval.	Prerequisite: The Incident Approval Job should be running. Steps: Navigate to Incident > User > Manage Users > Incident Details Resolve the Incident. The first level Approver will get an e-mail notification once the Incident is Resolved. Check the Incident Status in the e-mail.	Following are fixes provided for the issue description: The status of the Pending Approval ticket is displayed as Pending Approval. The Approval Date is displayed in the Approval Table. Approver Name and Approval Remarks columns are displayed in the Approval Table. Even if there are multiple approvers, all the approver names are shown in the Approver Table. If the Incident is pending for approval, the status is displayed as ‘Pending for Approval’ in the Approval Table. Now, if Approver approves the Incident, the Status column in the Approval Table displays the Custom status against the Approved Record. Note: Functionality of the status related to Approver: If Approver Reopens the Incident, no approver details are displayed in the e-mail, and the Incident is moved to In-progress status. If the incident is approved by the last Approver, the status is displayed as Closed.
101800	The Priority field value was not updated through the API based on the Urgency and Impact fields selection on the New Incident For User page.	Prerequisite: Priority matrix should be configured based on the Urgency and Impact field values on the Priority Matrix page (Incident > Configuration > SLA Configurations > Priority Matrix).	The Priority field value is updated through API based on the Urgency and Impact fields selection.
101855	Issue 1 Category is displayed as ??? in Approve Service Requests Page for Japanese language. Issue 2 Category and Classification field values are displayed as ??? in Approve Knowledge Records Page.	Issue 1 Prerequisites Service Category should be in Japanese language. Service Catalog should be mapped to Category and possess approval. Service Request should be logged using the catalog. Steps Login as Approver. Navigate to Request > Approve Service Requests. Verify the column Category of the Service Request for Japanese language Issue 2 Prerequisites Knowledge Category and Classification should be in Japanese language. A Knowledge Record should be created using the above Category and Classification. Steps Login as Approver. Navigate to Knowledge > Approve Knowledge Records. Verify the columns Category and Classification of the Knowledge Record for Japanese language.	The Category column in Approve Service Requests and columns Category and Classification in Approve Knowledge Records are now displayed in Japanese language appropriately.
96894	Email ID field was not there in User creation when the Login Type was selected as API KEY. When this User was made as Approver / Analyst they did not receive mails as Email ID was not added.	Steps 1.Log in as Admin. 2.Navigate to Admin > Users > User List. 3. Click ADD NEW. 4. Navigate to ACCESS tab > Login Type. 5. Select API KEY as Login type.	Email ID field is now made not mandatory for Login Type as API key.
101254	Email which had Japanese file name attached was not sent to the recipients. The email subject in Japanese was not displayed.	Prerequisites SMTP should be configured. File name that must be attached should be in Japanese language. An incident should be logged. Steps Navigate to Incident >Manage Incidents > Incident List. Access the logged incident. On the right collapsible action panel Click Send E-mail Enter valid Email IDs in 'To' and 'CC' fields. Enter mail subject and body in Japanese language. Attach the File named in Japanese language to the email. Click Send E-mail. Verify the recipient email.	The emails with Japanese file name and Japanese email subject is now sent to the recipient appropriately.
102952	In change history of Knowledge module the logged in time was appearing correct as per JST, but in Knowledge record list page time was appearing in IST.	Prerequisite A knowledge record must be created earlier. Steps Navigate to Knowledge > User > Knowledge Record List > Logged on. Select a knowledge record from the list. On the right collapsible action panel click Change History. Verify the time that is displayed in Step 1 and Step 3.	The time of Knowledge record logged is now displayed appropriately in JST (Japanese Standard Time) in Knowledge record list.
	User logged out of SummitAI application after entering of a valid MFA OTP and pressed Enter key from the keyboard.	Prerequisite Select Enable Multi-factor Authentication checkbox from Domain Configuration. Steps: Open a web browser. Enter the SummitAI application URL in the address bar and press Enter. Enter a valid OTP from third-party authentication. Press Enter key from the keyboard.	User can login to the SummitAI application successfully.
100661	Unable to inactive (deactivate) a category from Incident Management.	Prerequisites Navigate to Incident > Category. Select a Tenant from the list. Right-click a Category and click Inactive option.	The selected category is deactivated successfully.
102032	User unable to receive an email with the attached file in Japanese language.	Prerequisites Create a file in Japanese language. Attached the file to an email and send to a user. Verify if a user received the email.	User received email successfully with the attached file in Japanese language.
	In the Retrieve CMDB Master Methods API, the CMDB master methods CMDB_GetLocationMasterList and CMDB_GetCustomerMasterList are not responding when passing invalid Tenant name.	NA	In Retrieve CMDB Master Methods API, the CMDB master methods CMDB_GetLocationMasterList and CMDB_GetCustomerMasterList are using following validations for Instance name (Tenant name): CMDB_GetLocationMasterList Invalid Instance Name - Exception Error message (Invalid Instance) appeared. Valid Instance Name - Displays the results of Location based on the Instance and Domain. No Instance Name - Displays all the results of active location. CMDB_GetCustomerMasterList Invalid Instance Name - Exception Error message (Invalid Instance) Valid Instance Name - Displays the results of Customer based on the Instance and Domain. No Instance Name - Displays all the results for active customers.
102710	Unable to upload the files with the extensions: .CSV .log .jfif	Prerequisites Navigate to Incident > New Incident. Select a Tenant. Enter the required details and click Attachment to attach a file with .csv, .log, or .jfif extension.	SummitAI application supports files of all extension.
101592	Approval workgroup selection from the Custom Table was not working for Japanese characters.	Prerequisites: For the Custom Table, Japanese language must be selected. The Custom Table must be created in Web Service page to add valued IDs to users. Table Names must be configured in Form Builder. (Admin > Form Builder) Steps: Navigate to Admin > Workflow. In Workflow, add the Custom Table. While creating service request, the Usernames are displayed when the respective IDs are selected. Navigate to Admin > Workgroup. Select the TENANT. Workgroup List Page will be displayed.	The Approval workgroup selection from the Custom Table is now working for Japanese characters.
102508	When an over-sized attachment is added for a KB article, the attachment is not displayed in the ‘Change History’ of the KB article.	Prerequisite: Ensure you have an over-sized attachment handy with you. Click the Knowledge Record from the left pane. Click New Knowledge Record under User section. Attach the over-sized attachment and click Submit. Now open the Knowledge Record submitted from the Knowledge Record list page. Click Change History. The attachment uploaded is not displayed as it was over-sized.	The over-sized attachments are successfully displayed in the ‘Change History’ tab of the KB article successfully.
102427	In the New Change Request or Edit Change Request page in consumer view, after selecting the Tenant for which custom fields are configured, when you select the parent custom field value, the child custom field value in Japanese language was not populating.	Prerequisites: Create two custom fields with parent-child mapping. The datasource of the custom field should be custom table. The data values must be in Japanese language. Steps: Click the Change tab from the left pane. Click New Change Record or Change Record List under User. Select the Tenant which has custom fields defined. Select the parent custom field which has a child custom field defined in Japanese language using a Table.	It correctly displays the child custom field values in Japanese language, when you select the parent custom field value.
102876	KB article expiry alert is not reflecting in Mail History, even when KM Expiry Alert job is running.	Prerequisites: SMTP must be configured KM Expiry Alert job must be running Steps: Click Knowledge on the left navigation panel. Click Knowledge Record List. Select the KB Article which is expired and was created within 3 days (72 hours) of expiry date. Click Change History.	By default, the expiry alert email window is 3 days. Email is sent only 3 days prior to the expiry date set for a KB article. If the KB article is created and expiry date is set within 3 days of creation (less than 72 hours), the expiry email will not be triggered and record not captured in Mail History of the KB article.
102203	The page title was different after you clone a Change Record and was different from the page title of Create New Change Record. The page title is expected to be ‘New Change Record – Symphony SummitAI’ once you clone the CR.	Prerequisite: A CR should be created and pre-existing for desired tenant. Steps: Click Change > User > Change Record List. Select desired change record. Click Clone CR. Select desired check box for tabs > click on clone. New change record page will be displayed. Verify the Page title.	The page title displays ‘New Change Record – Symphony SummitAI’ for the newly cloned CR.

Known Issues

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

Issue #	Issue Description	Scenario	Workaround
95002	If the approver becomes inactive, then no other user can approve on behalf of the inactive approver and the approval is not happening.	Prerequisites: Configure an Incident Approval workflow (Incident > Others > Configure Approval). Resolve an incident and post resolution approval process will start. Once the approval workflow is attached to the incident, deactivate the approver. (Admin > Users > User List > FILTERS > Search User > select the required user > uncheck Active checkbox on User List page.	N/A
91707	Validations were not happening, and the Parser key was still retained in the Conditions section and Parameters section.	Bug Reproduction Steps: Click Admin > Advanced > Automation > Orchestration and go to Orchestration Workflow. Select workflow category for which the workflow with Line Parser or Free Form Parser Type configuration is configured. Select workflow name at which Content Parser is configured for Line Parser of Free Form Parser Type. Double Click on Begin Object > WORKFLOW CONFIGURATION. Click on Content Parser At Parser Type field, click on x icon(Clear all). Close the WORKFLOW CONFIGURATION window. Click Submit.	N/A
	Unable to find the expected result even though value is available in DB for symptom and user search.	Issue arises due to many factors and one most possible case is that in case of backup and restore of DB this issue may arise due to FT index is in inconsistent state after Transaction log restored. There is a known FT dictionary update issue which is documented by Microsoft. Reference: https://docs.microsoft.com/en-us/sql/relational-databases/search/troubleshoot-full-text-indexing?view=sql-server-ver15	Execute the following script which will start updating FT index data population once again. declare @run as table (id int identity(1,1),query nvarchar(2000)) insert into @run (query) select 'ALTER FULLTEXT INDEX ON dbo.['+object_name(object_id)+'] START UPDATE POPULATION;' from sys.fulltext_indexes where crawl_end_date is null declare @maxid int = (select max(id) from @run) declare @minid int = 1 declare @qry nvarchar(2000) while @minid <= @maxid begin select @qry = query from @run where id = @minid exec(@qry) set @qry = null set @minid += 1 end go
94440	Tag Alignment issue in new Change Request page.	Prerequisites: 1. Any browser with set screen size -> 100% 2. Scale & Layout -> 150% 3. Display resolution -> 1920 * 1080 Steps: 1. Navigate to Change > User > New Change Record 2. Keep the cursor in Tags text field and hover the mouse over ACTIONS panel to the right.	NA
98620	The custom attribute as Date control is not working as expected.	Prerequisites: Configure Work Order- Catalog mapping. Raise the SR. Steps to Reproduce the issue: Login as an Analyst. Navigate to Incident > Manage Incidents > Work Order List. The WORK ORDER LIST page is displayed. Under Filters, select the Module as SR, and Status as All. Under Custom Fields select any custom attribute having Date as field. Select the date. Click Apply.	N/A
96645/ 95169	In the Incident Management module, when the user tried to view the linked Incident ticket from Work order which was linked with the Incident, an Error message was displayed.	Steps:  Navigate to Incident > Work Order List. Select the necessary Work Order. The Work Order details page will be displayed. Select the Relationship Tab, and the Incident which is linked to Work Order. Click Incident. The Incidents details page will be displayed.	Add the following key in Web.config file <add key="App:Workaround_ViewAllTickets" value="true"/> as a workaround to skip the error.

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

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