Customer Fixed Issues and Known Issues Tahoe SP3 HF06
| 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
On this page: Customer Fixed Issues | Known Issues
Merged Releases
Following are the merged releases in Tahoe SP3 HF06:
Customer Fixed Issues
This section describes the issues reported by the customers and their fixes in Tahoe SP3 HF06 version.
Service Management
Issue ID | Issue Description | Scenario | Resolution |
114353 | The user was not able to update the user status (Active/Inactive). | Steps:
| The user can update the user status as Active or Inactive after the resolution. |
113813 | The API payload ADM_CreateorUpdateUser not updating Remarks. | API Request: API Response: | Earlier Password field was not passed as login type was NT.  This was the cause for Remarks field not getting updated. This issue is now fixed and    ADM_CreateorUpdateUser updates the Remarks field successfully.  |
111044 | While the analyst changed the ticket from InProgress to Assigned status, the Assigned To  field still shows mandatory.  | Prerequisite:  1.Create an Incident. Steps: 
| This issue is fixed and the Assigned To field doesn’t display as mandatory after change in status.  |
111912 | When the Cancel button was clicked on a knowledge record, it returned to the first page of the Knowledge record list instead of the previously selected page. | Steps:
| This issue is now resolved and a click on Cancel properly navigates. |
114069 | In the change history table the date value was updated with the "0001-01-01 00:00:00" format for a few requests. Due to this while opening the change history tab an error message "Opps error occurred" message is displayed. | Steps: 1. Navigate to Release > Release Record List > RR ID > Change Records. 2. The change record history date format should be of the accurate values. | Correct date format for the date value in the change history table is updated. Page loads without any error and the issue has been resolved. |
114064 | Issue 1: In Problem Management Classification/Category field the text was getting high lighted upon selection however it had to be greyed out. Issue 2: In Problem Management under Classification/Category field manually entered value though not present in the search list was not getting erased upon closing the search dialog box. | Steps: 1. Select Problem > New Problem Record > Classification. 2. Click search icon in the Classification field. 3. Select the text field value from the list. 4. Only Selected value remains in the Classification field and gets greyed out. Note : Same steps repeated for Category field. | Classification/ Category field gets greyed out upon selection of a value and manually entered values are erased after selecting the value from search dialog box. |
111793 | In the ETR and ETR Justification fields values could not be added through API method. | Steps: 1. Navigate to Incident > Manage Incident > Incident list > Incident ID -> Expected Time to Resolve (ETR). 2. The ETR and ETR Justification should have values. | The API is updated to allow editing the Expected Time to Resolve (ETR) and ETR Justification Values field. |
112562 | In the Knowledge Dashboard, knowledge article distribution does not show the count of one specific category. | Prerequisites:
Steps:
| In the Knowledge dashboard, Article distribution bubble shows all the category and correct count of articles. |
Asset Management
Issue # | Issue Description | Scenario | Resolution |
---|---|---|---|
112822 | End user was unable to view the assets on My Asset List page when the view was set to Tabular view whereas the allocated assets were visible when the view was set to Tile View. | Steps:
| My Asset List page displays assets in both Tile and Tabular view after the resolution. |
112956 | The Proxy Name column was displayed on the Agent Online Status Report. When the User clicked the Export To Excel/Export All option, the Proxy Name column was not present in the downloaded excel sheet. | Steps:
| The downloaded excel sheet on the Agent Online Status Report page displays the Proxy Name column with other existing columns after the resolution. |
Platform
Issue # | Issue Description | Scenario | Resolution |
114163 | All the details of the Oracle software were not getting discovered. | Prerequisites:
| All the details of the Oracle software are getting discovered after adding the following two registries:
|
112310 | In the Incident and Service Request modules, email notifications were not triggered to the configured email addresses and workgroups by the Auto Assignment functionality. | NA | The auto-assignment functionality triggers email notifications to configure email IDs and workgroups successfully. |
112881 | On the GIMIFICATION SUMMARY page, the Inserted Date format was not displayed based on the User’s time zone. | Prerequisites: Configure User Time Zone as GST in the Profile page. Steps:
| In the SummitAI application, all the time format entries are displayed in GST (Gulf Standard Time) format in the Data column. |
111597 | In the Operational Level Specification (OLS) page, an error message ‘Error loading OLA details’ was displayed when creating or updating records. | Steps:
| OLS records are created or updated without any errors. |
112816 | In the Release Management module, the email ids entered in the Pre Release Notification E-mail Ids and Post Release Notification E-mail Ids fields was not receiving the notification emails. | Steps:
| Email Notification is triggering for the email ids in the Pre Release Notification E-mail Ids and Post Release Notification E-mail Ids fields successfully. |
111907 | In Incident Module, when tickets were resolved via BULK UPDATE and Solution was added, the same Solution got updated automatically on the tickets which were resolved manually. | Steps:
| The BULK UPDATE functionality is working as expected. |
112688 | While raising a Service Request using Service Catalog with Multivalued fields and 3 attachments fields in Form Builder, users were getting an error “Oops an Error occurred”. | Steps:
| New Service Request page using the Service Catalog is working as expected. |
110213 | In the New Incident for User page when user selected the Template/Rule configured, the Category field validation was not working as expected. Even when the Category field value was selected it displayed an error stating “Please Specify Category.” | Steps:
| In the New Incident for User page the Category field validation is working as expected. |
110213 | In Incident Module, The Category values were not getting sorted in the Alphabetical order even when the Sort order was selected to be Alphabetical. | Steps:
| Category values are getting sorted in the Alphabetical order. |
Known Issues
This section describes the known issues detected by the SummitAI Dev and QA team in the release, Tahoe SP3 HF06 Release.
Issue ID | Issue Description | Scenario | Workaround |
101982 | An approver encountered an error ‘Opps, Error Occurred’ message when opening an SR for approval. | Prerequisites:
Steps:
| 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 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 > 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. | 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
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. |
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:
(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:
(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:
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:
Prerequisites
Bug Reproduction Steps:
|
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:
|
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:
|
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:
(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:
|
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). |
Confluence Cloud Migration Alert: Please refer to known issues you may encounter in Confluence Cloud: https://eitdocs.atlassian.net/wiki/x/wDGwAQ