Customer Fixed Issues and Known Issues Denali HF13
Previous Versions: << Sierra << Sierra HF01 << Sierra SP1 << Sierra SP1 HF01 << Sierra SP1 HF02 << Sierra SP1 HF03 << Denali << Denali HF01 << Denali HF02 << Denali HF03 << Denali HF04 << Denali HF05 << Denali HF06 << Denali HF07 << Denali HF08 << Denali HF09 << Denali HF10 << Denali HF11 << Denali HF12
On this page: Merged Releases | Customer Fixed Issues | Known Issues
Merged Releases
The bug fixes for the bugs found in the following version are also merged with this release. Please refer to the respective Release Notes for details.
- v5.7 SP5 HF22
- ALPS SP1 HF24
Customer Fixed Issues
This section describes the issues reported by the customers and their fixes in Denali HF13.
Issue # | Issue Description | Scenario | Resolution |
---|---|---|---|
92057 | The mapped workgroup for a user location is not appearing while raising a Service Request from Mobile Application. | Pre-requisites:
Raising a Service Request from Mobile Application the Workgroup field is appearing blank which is a mandatory field. | In the Service Request Details page, the mapped Workgroup for a user's location is appearing as expected. |
93670 | In a change password e-mail notification, the password has appeared in an encrypted format. | Pre-requisites: Enable Send Password Change Notification check box from the Access section of the User Details page. When an administrator changed the password of a user. The password appeared in an encrypted format in the notification e-mail. | The changed password now appearing as expected in the change password e-mail notification. |
91865 | When using DTAC - ERP integration tool, the customer was getting an error while using the “Add Asset” or the “Update Asset” features with API due to the invalid json request format for custom fields. | NA | The customer is able to use the “Add Asset” or the “Update Asset” features with API without any error. |
83663 | Issue1: When the Work Order is created from SR, E-mail notifications were not getting triggered as per configuration done at Tenant level. Issue2: When the Work Order is created from IM, E-mail notifications were not getting triggered as per configuration done at Tenant level. | Pre-requisites: Issue1: (For SR Module)
Issue2: (For IM Module)
| Issue1: When the Work Order is created from SR, E-mail notifications are getting triggered as per configuration done at Tenant level. Issue2: When the Work Order is created from IM, E-mail notifications are getting triggered as per configuration done at Tenant level. |
91071 | The end user was not able to resubmit the service request after modifying the required details. | This issue occurred when the SR was referred back by any of the approvers in the approval workflow. | Now, the end user is able to resubmit the referred back service request after modifying the required details. |
92553 | When the manager of a user is changed, the Asset Reconciliation mail was sent to the new manager correctly. However, the previous manager was able to take action on those assets. The authority to take action should only be with the new manager and not with the previous manager. | When an asset is put in Reconciliation mode, its approval consent mail also goes to the user's Manager. | After the fix, whenever a new Manager is assigned to an end user, all the pending approvals from the previous manager get assigned to the new manager automatically. With this improvement, the previous managers cannot take action on end users’ assets. |
91744 | Asset Dashboard Warranty Report not able to display entire expired records on screen as there was no pagination. Also, the complete warranty expired records were not getting exported to Excel sheet on the corresponding button-click. | Steps:
| Pagination is available now for the Asset Dashboard Warranty Report and it displays the list of entire warranty expired assets. Also, the correct dataset is getting exported to the Excel sheet on button-click. |
Known Issues
This section describes the known issues detected by the SummitAI Dev and QA team in the release, Denali HF12.
Issue |
---|
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:
|
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. (#67240) |
When a user opens any page in a new tab in the SaaS Environment, the Switch Tenant pop-up is displayed in all the pages. This issue occurs only when the user is using the Firefox private window/tab. (#72276) |
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