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 << DENALI SP3 HF04 << Denali SP3 HF05 << Denali SP3 HF06 << Denali SP3 HF07 << Denali SP3 HF08 << Denali SP3 HF09 << Denali SP3 HF10 << Denali SP3 HF11 << Denali SP3 HF12 << Denali SP3 HF13
Background Color | ||
---|---|---|
| ||
What's New? | Customer Fixed Issues and Known Issues | Prerequisites | Installation, Configuration, and Upgrade |
On this page: Hotfix Merges | Customer Fixed Issues | Known Issues
Scroll export button scope current template-id c9a14909-8f27-452d-bca0-164bee1a9265 caption Download this Page add-on Scroll PDF Exporter
AnchorHotfix Merges Hotfix Merges
Hotfix Merges
Hotfix Merges | |
Hotfix Merges |
The following Hotfix versions are merged with this release. Please refer to the respective Release Notes for details.
AnchorCustomer Fixed Issues Customer Fixed Issues
Customer Fixed Issues
Customer Fixed Issues | |
Customer Fixed Issues |
This section describes the issues reported by the customers and their fixes in Denali SP3 HF14 version.
Service Management Anchor Service Service
Service | |
Service |
Issue ID | Issue Description | Scenario | Resolution |
---|---|---|---|
102835 | Analyst was getting an error while opening the Service Requests (SR) in the Mobile App. | Prerequisites:
| Create and open SR option in Mobile App can be opened successfully without any errors. |
92897 | After upgrading to the Denali SP3 HF11 version, only closure auto escalation emails were getting triggered. However, the RCA escalation deadline emails were not getting triggered. | Prerequisites:
| After upgrading to the Denali SP3 HF14 version, all auto escalation emails are getting triggered successfully as expected. |
102904 | Issue 1: The Change Record with same ID as Problem Record ID was not getting displayed under the RELATIONSHIP tab. Issue 2: The Problem Record with same ID as Change Record ID was not getting displayed under the RELATIONSHIP tab. | Prerequisites: Issue 1:
Issue 2:
| Resolution 1: The Change Record with same ID as Problem Record ID is getting displayed under the RELATIONSHIP tab. Resolution 2: The Problem Record with same ID as Change Record ID is getting displayed under the RELATIONSHIP tab. |
101182 | If the incident status is changed, it was not displaying the assigned Analyst name. | Prerequisite: Select the checkbox Enable Secondary Analyst (Admin > Infrastructure > Tenant) for the required Tenant and configure sub-workgroup (Admin > Workgroup). Steps to reproduce the issue:
| If the incident status is changed, it is displaying the assigned Analyst (Primary and Secondary) name successfully as expected. |
101176 | Escalation e-mail was triggering for Service Request out of the configured SLA Window. | Prerequisites:
Steps to reproduce the issue:
| Escalation e-mail is not triggering for Service Request out of the configured SLA Window. |
101697 | When the user was opening the deactivated Category to re-activate the Category, it was giving the following error message: | Prerequisites:
| Deactivated category is opening to re-activate the Category without any error message. |
102835 | When fetching the Daily Service Request Report for multiple days, the following Oops error was displaying under Actions panel: “Oops! An error occurred.” | Prerequisite: Click the Filters icon on the ACTIONS panel to specify the filter criteria to display records in the DAILY SERVICE REQUEST REPORT. | Daily Service Request Report displays a list of all SRs reports during the specified time period for a selected set of Workgroups and Tenant. |
100911 | User was facing an issue to approve Service Requests (SRs) as they were automatically moving to New status without the approval of a Second level approver. | Prerequisites:
| After the First level Auto Approval,the SRs with specified catalog automatically moves to Second level approver Technician Selectable on Refer Back scenario. |
101239 | When fetching the Daily Service Request Report for multiple days, the following Oops error was displaying. “Oops! An error occurred” | Prerequisite: Click the Filters icon on the ACTIONS panel to specify the filter criteria to display records in the DAILY SERVICE REQUEST REPORT. | Daily Service Request report displays a list of all SRs reports during the specified time period for a selected set of Workgroups and tenant. |
102434 | Radio button validation control was not working in the Service Request module. | Prerequisite: Service Request should be logged with Approver. Steps:
| The Radio button validation control is now working as expected in theService Request module. |
102512 | After creating a Webservice Stored Procedure (SP), with input values these input valueswere not saved in the API InputString. | Steps:
| This issue has been fixed and the Webservice SP now saves the new parameter added successfully. |
102253 | User communication field was not updated in BI Report (DN Table). | Prerequisite: Whenever user updated User communication tab or status, post this, De-Normalizationjobs should run and then same should get updated in proper DN Tables. | This issue has been fixed and the User Communication displays correct status now. |
100016 | In the Incident Module, a mismatch of Response and Resolution Timewas observed in the Viewicon of the Incident dashboard and in the Ticket(Analyst view). | Prerequisite: Configure Customer SLA Matrix for the desired TENANT, Work Group and priority P1. Steps: Scenario 1
Scenario 2
| The Response Deadline, Response Time, Resolution Deadline and Resolution Time values are same in both Summary pop-up and detail page after resolution. |
101298 | Issue with the Customer enabled location-based routing option in the Service Request Module.
When the user selected Location “A” while raising the SR and the user location was “B”, the ticket was routed to Location “B”. | Prerequisites:
To configure this, perform the following steps:
Steps:
| The Customer enabled location-based routing option works successfully after the resolution. |
99946 | Issue with records display in the Summit application after successful IDM Integration. The user was unable to sync few user data in Summit Application through IDM. The user had to insert Mobile or Contact number and Password which was mandatory fields. | The End User was unable to sync few user data in the Summit Application through IDM integration. The Login type NT_UID integration does not require any password. This is related to Create or Update User Master API. | Necessary changes are made to Create or Update User Master API, where the Login type NT_UID nolonger requires mandatory Mobile or Contact number and Password as part of the resolution. |
Operation Management AnchorOperations Operations
Operations | |
Operations |
Issue ID | Issue Description | Scenario | Resolution | ||
---|---|---|---|---|---|
101847 | User was facing a network configuration error on viewing the assigned template, though default template was removed from the page. | Prerequisites:
| The user template option displays for newly added devices under Default Configuration. | ||
102843 | In the Network device configuration, SNMP V3 username was displayed incorrectly. | Steps:
| The username which was referring to monitoring account ID which was displaying as an integer is now displaying SNMP V3 username correctly. | ||
100734 | Server listed in server view, showed CPU and memory Monitoring as failed. | Prerequisite: Enable Store and Forward & enable CPU and Memory Monitoring. | The CPU and memory monitoring for Servers is currently monitoring successfully on the utilizations pop up page. | ||
101101 | The current assigned CPUNMEM command is giving incorrect values for the AIX Servers. | Step: Add the following Configuration key to monitor the CPU and Memory of the AIX server with appropriate provided commands.
| Enable the Configuration Key provided for AIXservers. | ||
101529 | Network Default configuration template was not showing in theNetwork Configuration page. | Steps:
| if the Users have created Template only for Network, then in the Network Configuration page the templates are listed correctly in the dropdown. |
Asset Management AnchorAsset Asset
Asset | |
Asset |
Issue ID | Issue Description | Scenario | Resolution |
---|---|---|---|
102191 | The following error message was getting displayed after clicking on the count hyperlink instead of displaying the data. | Prerequisites:
| The data is displayed as expected after clicking on count hyperlink without any error. |
101077 | The user was unable to extract the available licenses data to excel in the Software License Compliance Report.
The issue occurred in the condition, when the Host name was not mapped in the Key Field Mapping.
| Steps:
| Software License Compliance Report licenses data is exportable after fixing the Key Field Mapping.
The condition works successfully when the Host name is Mapped/ Not Mapped in the Key Field Mapping. |
Anchorplatform platform
Platform
platform | |
platform |
Issue ID | Issue Description | Scenario | Resolution |
---|---|---|---|
100901 | In the Authentication Configuration, if two Domains were configured then he user from the Domain that was set as ‘False’ were not able login to the Mobile Application. | Prerequisites:
| User can now login to the Mobile Application successfully even if the Domain is ‘Is Default’ as False when there is more than one Domain configured. |
102574 | User was logged out of SummitAI application after entering a valid MFA OTP and pressed Enter key from the keyboard. | Prerequisite: Select Enable Multi-factor Authentication checkbox from Domain Configuration. Steps:
| User can login to the SummitAI application successfully after enabling MFA check box. |
101333 | The configured Custom Fields in the Form Builder are not aligned as configured. The alignment of the fields was appeared inappropriately. | Prerequisite: Configure and align the field controls in the Form Builder for the respective Tenant. Steps:
| The configured field alignments display appropriately. |
99281 | The Change History was not visible for few of the Service Request (SR) that are in Resolved Status. | Prerequisites:
| The Change History of the Resolved Service Requests are displayed successfully. |
101652 | In the Daily Service Requests Report, the Subject column of the Service Request was displayed with HTML tags. | Prerequisite Convert an Incident to a Service Request. Steps:
| The Subject column in Daily Service Requests Report no longer displays HTML tag. |
102593 | The Category Wise Incident report was not displayed for all the tickets. | Prerequisites:
Steps:
| All the tickets now display the Category Wise Incident report successfully. |
102463 | The configured fields in Log Service Request page were not displayed in the Service Request. | Prerequisites:
| The configured fields in Log Service Request are displayed successfully. |
101188 | An approver encountered an error ‘Opps, Error Occurred’ message when opening an SR for approval. | Prerequisites
Steps:
| Approver can approve an SR even with the email with a symbol in the file name. |
103186 | User Communication was not attached or displayed on the Service Request Details page and mails are moved to the unparsed configured folder. | Prerequisites:
Steps:
| The user communication displayed successfully, and mails are moved to configured parsed folder. |
Agentless Discovery Anchor Agentless Discovery Agentless Discovery
Agentless Discovery | |
Agentless Discovery |
Issue ID | Issue Description | Scenario | Resolution |
---|---|---|---|
100820 | User was getting a server error while locating ESXi server using the Discovery option. | Prerequisites: To upgrade Secure Shell (SSH) server to ESXi server for locating the assets, refer the following steps:
| The user is not experiencing server-related issues, and ESXi server is getting discovered from the Discovery option. |
AnchorKnown Issues Known Issues
Known Issues
Known Issues | |
Known Issues |
This section describes the known issues detected by the SummitAI Dev and QA team in the release, Denali SP3 HF14.
Issue ID | Issue Description | Scenario | Workaround <if applicable> |
---|---|---|---|
88818 | The value selected for the Priority is getting cleared after CAB Approval. Prerequisite: Configure a PIR Reviewer. Bug Reproduction Steps: Click Change > User > New Change Record. Create a CR by selecting the Change Type as Emergency and e-CAB Approval Required as After Implementation. Authorize the CR. Implement the CR. Approve the CR. | This issue occurs only when the CAB approver approves the CR. | NA |
99798 | Software Deployment functionality was not working for FTP protocol with the latest 2.5.6.15 SAM Agent Version. | Prerequisites:
Steps:
| NA |
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. Server Type = O365 API Monitoring Source = Proxy Server 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: In Catch & Dispatch configuration page, switch to Service Request Module and select Show As Recommendation checkbox for all. In the Orchestration Configuration page, select Update if any one action fails in the On Failure drop-down list and keep the Do not update if value already exists checkbox unchecked. Bug Reproduction Steps: Navigate to Request > New Service Request. Create an SR where Orchestration script is linked. Navigate to Request > Service Request List page. Access the same Service Request and apply the catch and dispatch value from CINDE Suggestion popup. After Orchestration script fails, all Service Request details should update as per the Orchestration configuration. Verify the Service Request details against Orchestration configuration values. |
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: SR: Request > Configuration > Others > SMS Notification > Select the Tenant > Select the IMPORT option under ACTIONS panel. IM: Incident > Configuration > Others > SMS Notification > Select the Tenant > Select the IMPORT option under ACTIONS panel. (#81164) |
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: The existing devices on the page are not getting displayed. The validation message is not populating while submitting without selecting the devices. (#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: 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. (#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. |
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: 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). |
Scroll ignore | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|