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 << Denali SP3 HF14 << Denali SP3 HF15 << Denali SP3 HF16

What's New? | Customer Fixed Issues and Known Issues | Prerequisites | Installation, Configuration, and Upgrade

On this page: Hotfix Merges | 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.

Customer Fixed Issues

This section provides details about the fixed customer issues in following modules.

Service Management
Agentless Discovery
Platform
Operation Management
Asset Management

Service Management

Issue ID	Issue Description	Scenario	Resolution
107256	Under SERVICE CATALOG DETAIL page, the field values are stored in Chinese language, however, when the notification email Is triggered, the field values are not displayed in Chinese language.	Prerequisites: 1. Select "Include SR Details in SR E-mail" check Box in Application Setting Page. 2. Use *SERVICEREQUEST_DETAILS* keyword in SR mail templates. example- Approval Required Template. Step: 1. Navigate to Request > User > New Service Request > log a Service Request providing Chinese language characters in Catalog field. 2. For the above example check in the received approval mail sent to approver if the Chinese language characters are displayed.	The notification email is now displaying the Chinese language characters.
105556	There was Resolution SLA mismatch for the same Incident ID on Incident List page and Incident ID details page.	Prerequisites: Configure the Resolution SLA for an Incident. Check for Resolution SLA on Incident Id details page and Incident List Steps: Raise an Incident and configure the Priority with SLA configuration. Configure the SLA Service window as 9 to 12 (Assignments > Service Window) and click Submit. After 9 to 12 SLA, change it to 24/7 SLA Service window (Assignments > Service Window) and check the Resolution SLA and Response SLA. Navigate to Incident > Manage Incidents > Incident List and observe the Resolution SLA.	There is not any Resolution SLA mismatch for the same Incident ID on Incident List page and Incident ID details page.
97156	The name was getting displayed only for the first attachment.	Prerequisites: Create a Custom tab in Knowledge Management module. Add Multivalued Group having Attachment field under Custom tab using Form Builder. Steps: Attach one attachment. Click Submit. Attach the next attachment. Click Submit.	The name is getting displayed for all the attachments instead of only first attachment.
107804	The search results were getting redirected to the New Problem Record page.	Prerequisites: Login to SummitAI application and navigate to the top panel of the application. Type in the Problem Record ID in the global search that you want to search and click the icon. Click on the Problem Ticket number hyperlink under Problem Ticket No column.	The search results redirect to the Problem Record ID details page.
107335	When the Analyst raised a Change Request (CR), the default value was not populated on the CR Details page. The issue occurred when an additional dropdown was created, and a default value was set for the CR Details page in the Form Builder option.	Prerequisites: Navigate to Admin > Infrastructure > Form Builder. Select the desired Tenant, which is a mandatory field. Select Change Management from the Module dropdown. The Custom Attributes for Change Management page is displayed. Configure the custom dropdown value as the default value in the Form Builder. Steps: Navigate to Change > User > New Change Record. Select the Tenant from the dropdown, which is a mandatory field. Verify the custom dropdown values.	The Change Request (CR) Details page displays the set default value after the resolution.
103123	On the SR Detail page of the Service Request module, the Status Bar was not displayed for an analyst.	Prerequisite: Create an analyst name with all the access pertaining to the analyst role, such as including a different font for the single quote than the standard single quote. Steps: 1. Navigate to Request > Manage Service Requests > Service Requests List. 2. Create the Service Request (SR) by filling in all the necessary information. 3. Select the SR Id created in the Service Requests List page and see the Status Bar in the SR Detail page. OR 1. Navigate to Incident > Manage Incidents > Incident List. 2. Select an Incident ID. 3. Select CONVERT TO REQUEST. A pop-up will appear, click OK. 4. In the New Service Request For User page, fill out all the necessary information and click SUMMIT. A SR ID will be created. 5. Navigate to Request > Manage Service Requests > Service Requests List. 6. Select the SR Id created and see the Status Bar in the SR Detail page.	The Status Bar is now loading fine without any issues on the SR Detail page.
102865	The Excel Template for Catalogue "New Joiner Formalities (Regular /Contractual)" Bulk SR Option was not allowing the download. receiving a Oops error.	Prerequisite: 1. Make a Catalogue with names that include specific characters (? /:\| etc.). 2. Enable bulk SR creation option for the above catalog. Steps: 1. Login to Application. 2. Navigate to Request > User > My Service Request. 3. Select the created Catalog and Download Catlog Template. 4. The Excel file is downloaded.	The Excel is working fine, and the Excel Template for Catalogue "New Joiner Formalities (Regular /Contractual)" Bulk SR Option is allowing the download.

Platform

Issue ID	Issue Description	Scenario	Resolution
104671	The email notification template which got triggered to the caller when an action/update was performed on any Incident/SR through API had the Incorrect Incident/SR URL and the Incident/SR ID was missing.	Step: Update an Incident/SR through an API.	The API has been fixed and the email notification template is getting triggered without any Issues.
102384	System was displaying the following error message: "Value cannot be null.\r\nParameter name: source.” “Login_ID and Password parameters are mandatory for the NT Login type. Specify the Login_ID and Password values.”	Prerequisite: Scenario - 1 In ADM_CreateorUpdateUser payload, create a user with LoginType as NT, and keep Password, Mobile Number and Contact Number field empty. Scenario - 2 If Mobile Number is specified and Contact Number is not specified or vice versa.	System does not display any error message and creating the user without asking for Password, Mobile Number and Contact Number fields.
107811	The ADM_CreateorUpdateUser API created duplicate multiple user records on passing unique IDs, such as EmailId, EmployeeId, or NT_UID in UniqueField field.	Prerequisites: Log in to the SummitAI application. Navigate to Admin > User List. In the Filter Pop-up, enter the required details and click SUBMIT.	Duplicate multiple records are not created on passing unique field.
108576	In the Mobile App, the text was displayed with HTML tags in the Description and Solution fields of the following pages: Approve Service Request Incident Details Service Request Details	Prerequisites: Raise an SR in SummitAI application or Mobile App. Enter the required details to resolve Service Request (SR), such as Solution, User Communication, and Closure Code. Click Submit. Steps: Log in to the Mobile Application. Click the Requests widget from the Dashboard. Click the SR ID of the recently raised and resolved SR. Click SR Details tab. Notes: Issue persists in both Old and New Mobile App. Issue fixed for New Mobile App.	In the new Mobile App, the text in the Description, Remarks, and Solution fields appear without HTML tags.
107305	The Account and Manager fields in the ADM CreateorUpdateUserAPI were updated as blanks even though the system was submitting the Reporting Manager details.	Steps: Navigate to Admin > Basic > User > User List. Enter all the mandatory fields in the filters and click on Submit. Click on the User ID created. On the User Details page, go to GENERAL and fill out the Manager information. Navigate to ORGANIZATION DETAILS and fill out the Account Details. Click on SUBMIT.	The Account and Manager fields in the ADM CreateorUpdateUser API are now getting updated.
107811	The ADM_CreateorUpdateUser API created multiple duplicate user records on passing unique IDs, such as EmailId, EmployeeId, or NT_UID in UniqueField field.	Prerequisites: Log in to the SummitAI application. Navigate to Admin > User List. In the Filter Pop-up, enter the required details and click SUBMIT.	Multiple duplicate records are not created on passing unique field.
108576	In the Mobile App, the text was displayed with HTML tags in the Description and Solution fields of the following pages: Approve Service Request Incident Details Service Request Details	Prerequisites: Raise an SR in SummitAI application or Mobile App. Enter the required details to resolve Service Request (SR), such as Solution, User Communication, and Closure Code. Click Submit. Steps: Log in to the Mobile Application. Click the Requests widget from the Dashboard. Click the SR ID of the recently raised and resolved SR. Click SR Details tab. Notes: Issue persists in both Old and New Mobile App. Issue fixed for New Mobile App.	In the new Mobile App, the text in the Description, Remarks, and Solution fields appear without HTML tags.
105299	In the ADM_CreateorUpdateUser API, to update CustomAttributes field, user had to enter all the required fields to pass the payload.	NA	CustomAttribute fields are updated without entering the mandatory fields.

Asset Management

Issue ID

Issue Description

Scenario

Resolution

104370

The following error message was displayed on the My Asset List Page in the User Dashboard when the Reconciliation option was selected:

“You do not have access to this page. Please contact administrator.”

Prerequisite:

The end user using the application must not have access to the User Dashboard. This should be configured in the Role Template.

Steps:

Navigate to Dashboard > User Dashboard.
In the User Dashboard, scroll down to OTHERS section.
Select MY ASSETS option.
My Asset List page is displayed.
Click the Reconciliation option from the right ACTIONS panel.

The navigation to Asset Reconciliation page works successfully and no longer displays the error message.

Operation Management

Issue ID	Issue Description	Scenario	Resolution
107244	User was facing an issue while monitoring the VM host servers in the Secure Shell (SSH) under the Operations Module.	Prerequisite: Add the monitoring server(ESXi server (4. 0. 7. x)). Steps: Navigate to Operations > Server > Server List. Click FILTERS on ACTION panel, select the Tenant and click SUBMIT. Click the specified Host Name. The SERVER DETAILS pop-up displays the details of the selected server ID. Select CPU & Mem tab and observe the CPU and Memory Utilizations.	User monitors the VM host server in SSH successfully under the Operations Module and is not facing issues after the resolution.
105343	User was facing an issue in while monitoring the EXSi servers under the Operations Module.	Prerequisite: Add the monitoring server (ESXi server (4.0. 7. x)). Steps: Navigate to Operations > Server > Server List. Click FILTERS on ACTION panel, select the Tenant and click SUBMIT. Click the specified Host Name. The SERVER DETAILS pop-up displays the details of the selected server ID. Select CPU & Mem tab and observe the CPU and Memory Utilizations.	User monitors the ESXi server in SSH successfully under the Operations Module and is not facing issues after the resolution.
106693	Events were not getting closed for RAM parameter when devices were in maintenance. When the Servers were kept in maintenance mode even after the parameter which had breached was back to normal the events did not close.	Steps: Navigate to Operations > Views > Server View. Select Department from Filters section. Select a Server from the list. Navigate to CPU&MEM to verify if the RAM utilization is normal. Navigate to EVENTS LIST where If RAM utilization is normal and still verify if open event exists for same.	This issue is fixed, and the events are closing as required when RAM parameter is back to normal in server’s maintenance mode.
104805	Oracle rollback information data exceeded the limit in the table.	The primary key identity in AvM_Ora_Rollback_Info Table had exceeded its limit due to which the table was not accommodating the new records.	The table column’s capacity is now increased to accommodate larger numbers on Oracle rollback information.
105925	It was observed that the HDD utilization of the Linux server failed to monitor the utilization when HDD drive utilization is less than 4MB, while converting into GB it was giving exponential value.	Steps: Navigate to Operations > Views > Server View. Select Department from Filters section. Select a Server from the list. Navigate to HARD DISK and check the utilization.	Even if the HDD utilization is less than 4 MB the value is converted to GB and is displayed appropriately in decimal value.
107977	SSH servers are unable to monitor which had more than 32,000 as port number.	Steps: Navigate to Operations > Servers > Server List. Select the server for edit by clicking on host name or Add New server from action panel. In Monitoring By field select SSH. In SSH Port field enter a port value greater than 32,767.	The value for port number is increased in Add new server and Edit server pages. Now, the port number accepts till 999999999. Also, the page doesn’t display the default port number but displays the port number that the user newly added.
104805	Script based monitoring created multiple errors of the same type and of same entity. These were stored in error log table.	Steps: Create Script based monitoring. Let the job run multiple times.	Multiple errors are not created in the error log table. Now, if for the same parameter new errors are found we are updating the existing record.

Agentless Discovery

Issue ID

Issue Description

Scenario

Resolution

106631

User was facing an issue with Content Parser pop-up in Discovery Template page, as it was not fetching the data from hard disks of multiple sizes (GB and TB).

Steps:

Navigate to Discovery & Monitoring > Discovery Template > Content parser.
On the Discovery Template page, Click the specific Template Name.
Click Actions for the specific Parameter Name.
Under the CONTENT PARSER pop-up, select Content Type, Output Type, Unit and make all Final output as false for the multiple parsers to work.

User is not facing issue while fetching data from multiple hard disks and is working properly after the resolution.

106808

User was facing an issue while fetching IP Address for Windows Management Instrumentation (WMI) discovery.

Steps:

Navigate to Admin > Discovery & Monitoring > Discovery.
On the Discovery page, Click View Jobs under LIST. The Subnet Details displays the IP ADDRESS of the scanned discovery.

User is not facing issue while fetching IP Address for Windows Management Instrumentation Discovery (WMI) and it is displaying appropriately after the resolution.

Known Issues

This section describes the known issues detected by the SummitAI Dev and QA team in the release, Denali SP3 HF17.

Issue ID

Issue Description

Scenario

Workaround <if applicable>

101982

An approver encountered an error ‘Opps, Error Occurred’ message when opening an SR for approval.

Prerequisites:

Create a Catalog with fields including an Attachment field.

Create an SR and attach an email with a symbol in the attached file name.
For Example:

Steps:

Log in to the SummitAI application as an Approver.
Navigate to Request > Service Request List.
Click the newly created SR ID hyperlink.

N/A

99798

Software Deployment functionality was not working for FTP protocol with the latest 2.5.6.15 SAM Agent Version.

Prerequisites:

Log in to SUMMIT Application with Admin module access. Have few tenant values configured with access to Asset Management module.
Software package should be configured/created with package source as 'FTP' with valid credentials.
SAM Agent should be configured.
End User machine should be in successful contact.

Steps:

Log in to SUMMIT Application.
Initiate the software deployment of any software (For example, Safari browser) using Agent/Remote.

NA

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

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. Issue 2: Similar issue was also found for the prerequisite of On Success criteria configuration being Resolve if all actions are successful. This paired with Do not update if value already exists check box not being selected led to a similar bug. (#83602)
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).

Loading