Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

 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

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 describes the issues reported by the customers and their fixes in Denali SP3 HF13 version.

Service Management 

Issue IdIssue DescriptionScenarioResolution
97400Service Request (SR) List Page was loading slowly, and timeout error logs were discovered. 

Prerequisite 

Large number of Service Requests (SRs) must be present for each Tenants. 

Steps: 

  1. Log in as Super Admin. 
  2. Navigate to Request > User > Manage Service Requests > Service Request List 
  3. Click Filters  
  4. In the Values field corresponding to Tenant select ALL. 
  5. In the next Field select Log Time, in Operator field select > and in Values corresponding to Log Time must be a date ten years older. Example: Select the Log Time as 30-03-2012.

  6.Click Apply. 

 

The Service Request List Page is now loading faster, and the slowness issue has been fixed
99986 When any user was sending an email with the same subject to multiple mailboxes which were configured in application for different tenants, the same ticket was created and updated. 

Prerequisites 

  1. Configure two Mailboxes for two different Tenants.

2.Corresponding Notification Parsers should be configured for the Tenants respectively.

3.Make sure the Email Parsing job is running.

Steps: 

1.Send mail to both the Mailboxes with same Subject. 

2.Navigate to Incident>User>Manage Incident>Incident list 

The Incident tickets are now created separately for different Tenants. 
102276A Change Manager encountered an error message when you click the Change Record ID hyperlink from auto-escalation email.

Prerequisites 

  • Configure an auto-escalation for CM module.
  • Configure and schedule CR Auto Escalation Job.

Steps:

  1. Navigate to Change > New Change Record.
  2. Enter the required details and click Submit.
Change Record can be accessed from Auto-escalation email successfully. 
101377In the Frequently Used Service Catalogs widget of User Dashboard, the last five frequently used service catalogues were not displayed, and the widget appeared as blank. 

Prerequisites

  1. Log in SummitAI application.
  2. Navigate to Dashboard > User Dashboard.
The service catalogues that are frequently used are displayed in the Frequently Used Service Catalog widget successfully. 
99996In the Incident SLA By Workgroup Report, the workgroup names at the horizontal axis (x-axis) of bar graph were not displayed. 

Prerequisites 

  1. Navigate to Reports > Incident Management
  2. In the Report Field, search and select the Incident SLA By Workgroup Report.
  3. The Resolution tab selected, by default. 
The workgroup names corresponding to the bar graph are successfully displayed. 

96959 

When the Analyst assigns the Service Request to a different Analyst, the mail Subject displayed the syntax error. 

Example: 

It is used to display as “<br /><br />” in the mail Subject. 

This issue occurred when the Analyst used ‘Space’ or ‘Enter’ in the Description field of the Service Request Details page. 

Prerequisites: 

  1. Navigate to Admin > Advanced > Notifications > Notification Template > Select the Tenant > Select the Service Request module.   
  2. Verify if the Service Request Analyst Changed notification template is available under the Workgroup section.  
  3. In the Tenant level configuration the following options should be enabled under Service Request module (Admin > Basic > Tenant > Select the Tenant > Select the Module).  
    • Notification For All Status Updates  
    • Notify Workgroup Owner(s) for SR Reassignment  

Steps:  

  1. Select Request > User > New Service Request  
  2. Create a new Service Request.  
  3. Add ‘Space’ or ‘Enter’ in the Description field.  

Example:  
 Hi,  
   
 VPN Access

There is no syntax error found on the mail Subject if the Analyst assigns the SR to a different Analyst. 

99653 

The user could not access the Change History of a few tickets since a performance issue was observed in loading the Incident and Service Request change history details. 
 

This issue occurred if the ticket's User Communication / Private Log  field had a long description (more characters) on the Incident Detail / Service Request Detail page. 

 

Steps: 

On the Incident Detail / Service Request Detail page, 

  1. Navigate to Incident / Request > User > Incident List / Service List > Select the Incident / Service Request. 
  2. Enter all User Communication and Private Log fields with larger text and submit. 
  3. Select the Change History from the Actions panel. 
  4. The change history details of the Incident / Service Request will not load, the page remains blank. 

 

The performance issue is fixed, and page takes less time to load the Incident / Service Request Change History. 

101125 

There is an overlapping issue on the Category pop-up of New Knowledge Record page. The Category name was exceeding outside the container/grid. 

Steps: 

  1. Navigate to Knowledge > User > New Knowledge Record. 
  2. Search the Category. 
  3. Check the category name in the Category pop-up. 

Removed the container/grid and now the Category name is displayed in the Tree view. 

100014In the Incident Module, a mismatch of Response and Resolution time was observed in the View icon of the Incident dashboard and in the Ticket (Analyst view). 

Prerequisite: Configure Customer SLA Matrix for the desired TENANT, WG and priority P1. 

 Steps: Scenario 1 

  1. Log in to SUMMIT Application.
  2. Navigate to Incident > New Incident. 
  3. Create an Incident for the configured Tenant, WG and Priority P1. 
  4. Navigate to Incident > Incident List- Open the created Incident. 
  5. In the Incident List- Click on 'Summary' Icon for the respective ticket ID. 
  6. Compare the Response Deadline, Response Time, Resolution Deadline and Resolution Time in the summary popup with the same parameters displayed in Incident detail page. 

Scenario 2 

  1. Log in to SUMMIT Application.
  2. Navigate to Incident > New Incident for User. 
  3. Create an Incident for the configured Tenant, WG and Priority P1. 
  4. Navigate to Incident > Incident List- Open the created Incident. 
  5. In the Incident List- Click on 'Summary' Icon for the respective ticket ID. 
  6. Compare the Response Deadline, Response Time, Resolution Deadline and Resolution Time in the summary popup with the same parameters displayed in Incident detail page. 
The Response Deadline, Response Time, Resolution Deadline and Resolution Time values are same in both Summary pop-up and detail page after resolution.
99043While trying to fetch Workflow in the Change Management module, it displayed status as “Processing” state. 

Steps: 

  1. Navigate to Admin > Workflow- The Filters pop-up will be displayed. 
  2. In Filters, select the necessary Module, Tenant, Change Type, Customer, Owner Workgroup, and Category from the drop-down list. 
  3. Click SUBMIT.
The Workflow in Change Management module works fine after the resolution.  

Operation Management

Issue IdIssue DescriptionScenarioResolution
96663

In the Oracle database’s Table space usage parameters, the ITOM tool did not trigger events (alerts and incidents) when there was a threshold breach for other parameter types, if any one of the parameters already had an open event. 

Prerequisites:

  1. Navigate to Dashboard > Oracle Dashboard. 
  2. Add Oracle tablespace for monitoring the events. 

Steps: 

  1. Navigate to Dashboard > Oracle Dashboard 
  2. Monitor Oracle -Table Space parameter. Example: Table Space Name -SYSTEM, whose Variable being monitored is Used space %. 
  3. Breach the Threshold value of SYSTEM and event and ticket will be created for the same. 
  4. Breach the threshold for any other parameter like Users and keep the previous threshold event open.
  5. Navigate to Operations > Views >Server View > Select a Tenant and SUBMIT.
  6. Select the Oracle device that was added for monitoring.
  7. Click EVENTS LIST tab. 



The alerts and events are now created separately when there is a threshold breach for different Table Spaces that are being monitored. 

96721Modified HDD thresholds are not visible in Change History Tab. 

Prerequisites:

1)Navigate to Operations > User > Views > Server View.

2.Select a Server.

3.In SERVER DETAILS pop-up click HARD DISK tab.

4.In THRESHOLD CONFIGURATION update Threshold High %, Threshold Medium % or Threshold Low % of any drive.

Steps: 

  1. Navigate to Operations > Configuration >Servers > Server List. 
  2. Select any server for which the threshold was updated. 
  3. Navigate to > ACTIONS > CHANGE HISTORY.
Modified threshold values at HARD DISK tab are displayed under Server's Change history details. 
98911In the URL Response Time Report, status of response in the column Status was not appropriate. 

Prerequisites: 

URL should be monitoring. Perform the following steps: 

  1. Navigate to Operations > URLs > URL List. 
  2. Select TENANT from drop-down. 
  3. Click ADD NEW. 
  4. Enter the URL to be monitored in the URL section. 
  5. Enter other required details and SUBMIT

Steps: 

1.Navigate to Reports > IT Operations Management > URL Response Time Report. 

2.Enter the desired values in Filters and Submit.

3.In Average Response Time (Sec) click any hyperlink. 

4.In URL RESPONSE DETAILS pop-up, check the Status column.

Status column was displaying the latest monitored state of the URL and not on the date mentioned in the column Monitored Date. To avoid confusion, the column Status is removed from URL Response Time Report to maintain uniformity across other reports.
96936The links were going down for SNMP V3 type devices. 

Prerequisites :

1.Navigate to Operations > Configuration > Networks > Views > Create View.

2. Select TENANT and Job Name.

3.Select Devices and Add Selected for monitoring. 

4. Click

5. Enter View Name, select Customer and

6.Create link between SNMP V3 device and other device whose interface is up and available.

Steps: 

  1. Navigate to Operations > User > Views > Network View. 
  2. Select Tenant 
  3. Or 
  4. Navigate to Operations > User > Views > Network Device View. 
  5. Select Tenant and select any link. 
  6. Verify the status of the link that was created earlier and check if its status is going down.

  

Now the links don’t go down for SNMP V3 type of devices if the device is in up status.
97815In the Backup Report that was created, the backup configuration of Network Device was not formatted properly.

Steps: 

  1. Navigate to Reports > IT Operations Management. 
  2. In the REPORTS drop- down specify Network Device Configuration Report. 
  3. In the filters pop-up Select TENANT, specify Frequency and From Date. 
  4. Select a Network Device from Devices drop-down and SUBMIT. 
  5. In the report that is generated click hyperlink View. 
  6. A .txt document is downloaded, or it can be saved manually on to the end user computer. 
The data in the Network Device Configuration Report is now legible and formatted appropriately.

Asset Management

Issue IdIssue DescriptionScenarioResolution
99879

In Fixed asset, the multi-valued search for serial number and other fields were unable to display all the available records, displayed only limited records after the search filter submission. 

The multi-valued search was unable to display data above 24 records.

Steps: 

  1. Navigate to Assets> Inventory> Fixed Asset.
  2. Select any category.
  3. Navigate to Tenant> Status and Category-select all.
  4. Select Search by Serial number- enter more than 50 serial numbers. 
  5. Click SUBMIT.

The List page asset count matches the specified serial number count after the filter submission. 

100659 

Improper display of barcode showing only 80 asset entries when the user selected 200 assets. 

 The user was unable to print all the selected assets barcode in Summit application.

Steps: 

  1. Navigate to Assets> Inventory> Fixed Asset. 
  2. Select more than 80 Assets of any Fixed Asset category. 
  3. Change the assets count from 15 to 200. 
  4. Click Print Barcode from Action panel. 
  5. Print Barcode- Details will be displayed. 
  6. Count Match- The selected asset count from List page Should match with asset barcode count in the Print Barcode - Details Page. 
The selected assets in the Asset list page matches the asset barcode count in the Print Barcode details page making it printable.
100040

The user was getting Oops error while accessing the following Asset Dashboard reports: 

  1. Asset contacted before 30 days 
  2. Warranty about to expire in 30 days 
  3. Allocated Pending Return 

Steps:

  1. Navigate to Dashboard > Asset Dashboard.  
  2. Scroll down to Others section at the bottom of the page.  
  3. Click the count hyperlink on ASSET CONTACTED BEFORE 30 DAYS tab. Verify whether Oops error is received on the report page.  
  4. Click the count hyperlink on WARRANTY ABOUT TO EXPIRE IN 30 DAYS tab.  Verify whether Oops error is received on the report page. 
  5. Click the count hyperlink on ALLOCATED PENDING RETURN tab. Verify whether Oops error is received on the report page.
Oops error is no longer displayed on the Asset Dashboard report pages after the resolution. Corresponding asset details are correctly displayed on the report pages. 


Known Issues 

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

Issue NoIssue DescriptionScenarioWorkaround <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
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).

  • No labels