Customer Fixed Issues and Known Issues Denali SP3 HF04
Previous Versions: << Sierra << Sierra HF01 << Sierra SP1 << Sierra SP1 HF01 << Sierra SP1 HF02 << Sierra SP1 HF03 << Denali << Denali HF01 << Denali HF02 << Denali SP1 << Denali SP1 HF01 << Denali SP1 HF02 << Denali SP1 HF03 << Denali SP3 << Denali SP3 HF01 << Denali SP3 HF02 << Denali SP3 HF02 B010
On this page: Customer Fixed Issues | Known Issues
Customer Fixed Issues
This section describes the issues reported by the customers and their fixes in Denali SP3 HF04 version. The bug fixes for the bugs found in the following versions are also merged with this release. Please refer to the respective Release Notes for details.
Issue # | Issue Description | Scenario | Resolution |
---|---|---|---|
86794 | On the Approve Service Request page, the attachments that were added after the first uploaded attachment in the Attachment field with Multi-valued Approver Group, retained the first attachment’s file name. | NA | The attachments that are added after the first uploaded attachment, contains the actual file name. |
87032 | The Password Management feature was not working with the OTP option when GDPR was enabled. | NA | Now, the Password Management feature is working with the OTP option when GDPR is enabled. |
87040 | Earlier, the License Expiry Alert e-mail was sent to the users who had access to Admin pages under any modules. | NA | Now, the License Expiry Alert e-mail is sent to the users who have access to Admin pages under Admin module or Admin Reports only. |
86726 | On the SWITCH USER LIST and RESIGNED APPROVER LIST pages, the Search box/ field was not searching the user input to be searched for in a database. | This issue occurred when the key <add key="IsDecryptExceptionIgnoreDisabled" value="True" /> was not added in web.config. The SWITCH USER LIST page can be accessed using Admin > Basic > Users > Switch User List. The RESIGNED APPROVER LIST page can be accessed using Admin > Basic > Users > Resigned Approver List. | Now, on the SWITCH USER LIST and RESIGNED APPROVER LIST pages, the Search box/ field is working as expected. |
80680 | For the non-fixed assets (accessories), in the Asset Allocation form, under the Other Asset Details, the details of the accessories that are allocated to User were not displayed. | NA | Now, in the Asset Allocation form, under the Other Asset Details, the details of the accessories that are allocated to User and Asset are displayed. |
86086 | The following issues were observed for the Asset that is in-transit status:
| The in-Transit asset was waiting for movement approval. | Now, a message “Asset deactivation action for asset(s) with the current as in-transit, cannot be performed.” is displayed when the user tries to deactivate the asset which is in transit status and waiting for movement approval. |
87978 | PM approval e-mails were sent to the recipients of other workgroups who were not configured as a PM approver for the dedicated PR. | NA | Now, the issue is fixed and PM approval e-mails are triggered to the respective Workgroup approver. |
87036 | After creating the user from the NEW USER page, the GDPR compliant fields were shown as plain text in the ADM_Configuration_History table even though the GDPR was enabled in the application. | NA | Pre-requisites Execute the following script only when GDPR is enabled and ADM_Configuration_History table has existing data. Resolution Now, in the ADM_Configuration_History table the GDPR compliant fields are shown in the encrypted format. |
87285 | Blank response was received after running the report API. | This issue was occurred when the customer had two DB server i.e, one for Application and another for reporting. And the report DB is pointing to different DB and application connection string in different DB. Due to which the application was validating the API from the Application DB rather than reporting DB. Note: By default, the value of DBconnection_TargetServer config key is taken from connection string by default. | Now, the fix is done for the following scenarios:
For example, if customer has 2 servers named SV1 and SV2 where SV1 is Application DB and SV2 is Reporting DB which is holding the connection string as DB target. In such case application will always validate the API key from SV1 and data will be taken from the Reporting DB SV2.
For example, if customer has Server SV1 and 2 different databases, DB 1 (application is hosted) and DB2 (Reporting DB), and the "DBconnection_TargetServer" is not empty. Then the API key is validated from the application the DB1 and reporting data is fetched from the DB2. However, if the DBconnection_TargetServer connection is empty, then system takes data from the connection string which is configured in web.config.
For example, if the target server (where DB connection is set) is empty, then both application and report gets data from the connection string which is configured in web.config. |
86442 | Tool tip depicting the name of the selected category is not displayed when the analyst hovers on the selected category at Closure Category field.
| Pre-Conditions: Tenant must be fully configured for Incident Management module. 1) On Tenant Details page, Enable Capture of Closure Category checkbox should be selected. 2) There should not be any default closure code for the tenant. 3) Log an incident for the tenant.
Prerequisite Steps : 1) Log into the application as an analyst. 2) Go to Incident > Incident List. 3) Open the previously logged incident. 4) Change status to Resolved state on the status bar 5) Fill out all the mandatory fields. 6) At Closure Category field, select the desired category. | Tool tip depicting the name of the selected category is displayed correctly. |
Known Issues
This section describes the known issues detected by the SummitAI Dev and QA team in the release, Denali SP3 HF03.
Issue |
---|
While trying to uninstall the TLS 1.2 agent from the control panel, a pop-up message “Network connect failed. Please contact Administrator “is displayed and TLS 1.2 agent was not getting uninstalled. Work around: Using the Uninstall_SAM_SSI.exe, you can uninstall TLS 1.2 agent. (#87625) |
Under the Asset Movement Details section of the Asset Transaction Details Report, the assets which are in In-Transit status and waiting for movement approval (such as Return From Repair movement approval, Send To Repair movement approval, and Assets waiting for Deactivation approval) are not getting displayed. (#86416) |
Under the Checker Status column of the FIXED ASSET inventory page, When the Fixed Asset is allocated the Asset status is shown as Referred Back even though the Maker-Checker configuration is disable for the Allocate asset transaction. This issue occurred when the Maker-Checker configuration is enabled for the Deallocate and Deactivate Asset transactions and the Checker refers back the asset deactivation request. In an ideal scenario, the Checker Status column of the FIXED ASSET inventory page must get cleared after allocating the In-Store asset that was referred back by the Checker for asset deactivation request. (#83900) |
Mail Parser configured with O365 API cannot run on the summit Proxy Server, it can only run on the Summit Server. Email to ticket creation feature is not supported for the following configuration combination on the MAILBOX page.
Note: Email to ticket creation works when you select Server Type as O365 API and Monitoring Source as Summit Server. The MAILBOX configuration page can be accessed using Admin > Advanced > Notifications > Mailbox. (#83831) |
When the user re-login into the SummitAI application and performs the same action for the second time on the same page (Ex: MY APPOINTMENTS) and clicks SUBMIT, an error message “Error Occurred” is displayed. This issue is found when the user has logged into the SummitAI application using the Microsoft Internet Explorer browser (IE Version: 11.719.18362.0) (#82553). |
Issue 1: Urgency and Impact values of Orchestration are not getting updated on the SR details page. Orchestration values should override the Catch & Dispatch values. Pre-Requisites:
Bug Reproduction Steps:
|
SAM Agent unable to block the installed software’s, mapped in the Master profile though the same software is getting block when mapped with the normal profile of an Asset. The master profile should work as default when a normal profile is configured for the Asset. (#82494) |
In the Universal Agent, Software installation is not working through Run Book Automation (RBA) script. (#83612) |
After configuring the remediation Script as User-preference in the new Universal Agent, the Endpoint Automation (EPA) is not working and the EPA script is always displayed with In-progress status. (#83611) |
Post the SAM agent update, the Software Silent Installation functionality using RBA script is not working. This issue is occurred when the Agent machine has two IP addresses (#83770) |
The servers with IP Addresses 192.168.100.30, 192.168.100.100 servers, the Universal Agent parameter EPA, Patch Management, and RBA functionalities were not working. The application was showing the following error message (#82939): Error Message: The underlying connection was closed: An unexpected error occurred on a send. at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request) at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at SAMAgent.Entwidgets.Service.GetRBAScripts(String sAssetInfo, String sProxyName, ProxyDetails _pxy) at SAMAgent.AssetDetails.Agent_RunbookAutomation.ExecuteRBA() at SAMAgent.Program.Main(String[] args)
|
When an AD Import record is modified on IE Version 11.719.18362.0, the error message is displayed as “Error Occurred” when you click SUBMIT button on the AD IMPORT page (Admin > Basic > Users > Import > AD Import) (#82733). |
While raising a CR, if the Requestor is changed after selecting Category and Change Type, the Line Manager and Reporting Manager for the selected Requestor are not getting updated in the workflow. But after submitting the CR, the Line Manager and Reporting Manager are updated in the workflow based on the selected Requestor. Similarly, the same issue is happing while raising CR using a template too. |
While importing data through the Import Excel option, the Include Sub-Customer value in the respective column can only be True or False for all the statuses in the excel sheet. To import the excel navigate to:
|
On the Incident Details/ Service Request Details page (Incident/ Request > User > Manage Incidents/Manage Service Requests > Incident List/Service Request List > Click an Incident ID/SR ID), click the Assigned To drop-down where analysts are displaying, but their availability status is not displayed (#78647). |
Application is allowing the Administrators to save the Connector details though there is a validation message while updating the Connector details page. The Connector details page can be accessed from EDIT VIEW page (Operations > Configuration > Networks > View > Edit View > Select the required device from the list > Click the Connector on the Drawing Board > Click Edit Node to update the Connector details > Update the details with incorrect data to pop-up the validation message > Click SAVE). (#81100) |
After adding a new device on the Drawing Board of the EDIT VIEW page sometimes the position of the added device is not displaying correctly on the Drawing Board. The Edit VIEW page can be accessed using (Operations > Configuration > Networks > View > Edit View > Select the Tenant and other required details> Click Add Node icon and click on the empty space of the drawing board to add devices into the View > Click SUBMIT). (#80641) |
The following issues are there on the EDIT VIEW page (Operations > Configuration > Networks > View > Edit View > Click ADD NEW on the ACTIONS panel > On the DRAW VIEW page, select the Tenant and other required details > Click ADD DEVICE on the ACTIONS panel to add devices into the View > On the ADD DEVICE pop-up page, select the devices you want to add to the View and click SUBMIT) while adding a new device to the view:
(#80269) |
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:
|
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