Customer Fixed Issues and Known Issues Denali SP3 HF15

Owned by Enterprise IT
May 08, 2024

 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

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

Issue ID


Issue Description

Scenario

Resolution

102787

The Problem Record was not getting created automatically even after the auto-creation conditions were met.

Prerequisites: 

  1. Navigate to Problem > Configurations > Auto Creation Settings > Select the required Tenant. Click Add New under Action Panel. The AUTO CREATION SETTINGS page is displayed.

  2. Configure the required details under GENERAL DETAILS, CONDITION and TARGET Click Submit.

The Problem Record is created automatically after the auto-creation conditions are met.

101953

The filters were not working as expected for any other language than English.

Filter values were getting cleared instead of updating the values.

Prerequisite:

Change language from English to any other language in SummitAI application.

The filters are working as expected for all languages.

102867

The Radio button validation control was not working in the Service Request module. 

Prerequisite: 

Service Request should be logged with Approver.

Steps: 

  1. Navigate to Catalog > User > Create Service Catalog > Select Radio Button Control and Dropdown Control in the Form builder page.

  2. In the ADDITIONAL INFO tab, set Validate Controls Rules for both controls.               
    Select On Control Change.

  3. Select Yes as Mandatory and Select No as Save and Publish the Catalog.

  4. Navigate to Service Request > New Service Request.

  5. Select Yes in Radio control while creating Service Request.
The Radio button validation control is now working as expected in the Service Request module. 
103379User was facing an issue with Status list in Filters option as Resolved status was not displaying under the Status list in Problem Record page.

Prerequisite:

 

Configure the drop-down list of Status in the Filters options as: New, Assigned, In-Progress, Pending, Resolved, Closed, Opened and Re-opened.

 

Steps:

  1.  Log in to the application.

  2.  Navigate to the Problem Record > Relationship.

  3.  Click the link icon on the Relationship tab.

  4.  Select the option Incident under Relation and Click the drop-down list of Status under the Filters option.

  5. Select the Resolved option from Status list and click the search bar. The page displays the list of Resolved incidents.


User is not facing issues with Status list and Resolved option is now displaying list of Resolved incidents under the Problem Record page as expected.
102836When SR was created using Mail to SR feature, the Symptom and Description were getting repeated in the e-mail subject and body line for the generated SR.

Prerequisites:

1.      Configure a Mailbox as Admin > Mailbox.

2.      Configure two Rules as Admin > Notification Parser.

 Steps:

 1.      Create SR through the mail.

 2.      Navigate to Application > Request > Manage Service                        Request > Service Request List.

3.      Open the created SR.

4.      Check the Symptom and Description in the generated SR.

The Mail to SR feature is functioning properly, as Symptom and Description are not getting repeated in the generated SRs.
103470

When the Service Request (SR) was auto closed , Resolution SLA Deadline value was not updated and was appearing in breached status under the SERVICE REQUEST DETAIL page. 

Prerequisite:

Configure Auto Resolve in the Tenant Level.

Refer the following steps, to configure Auto Resolve in the Tenant Level:

  1.  Navigate to Admin > Tenant.

  2. Select Tenant > Configuration details > SR module > Search Auto Resolve Service Request.

  3. Click the link Set Fields for Auto-Resolving Service Requests.

  4. Add the All-mandatory fields and click Submit.


Enable Auto-Assignment of SRs and configure the Resolution SLA

Refer the following steps, to enable Auto-Assignment of SRs and configure the Resolution SLA:

  1. Navigate to Admin > Tenant.

  2. Select Tenant > Configuration details > SR module > Search Auto - Assignment of SRs and enable Auto-Assignment of SRs.

  3. Navigate to Request Module > SLA Service Window > Select 9 to 5 Link and enable the deadline.

Steps:

  1. Log the Service Request.

  2. Move to SR from InProgress to Pending State before the Response Deadline.

  3. Wait for Auto Resolve and check the Resolution SLA and Response SLA.
Resolution SLA is not getting breached for auto closed SRs and it is displaying properly in the SERVICE REQUEST DETAIL page after the resolution.
104055

Analyst was facing an issue to remove the Change Advisory Board Member from the Change Category under the Change Advisory Board page.

Steps:

  1.  Navigate to Change> Configuration > Change Advisory Board > LIST > Change Advisory Board Name.

  2. Click the CAB Approver.

  3. Navigate to Change Advisory Board > Details > Change Category.

  4. Uncheck the Change Category box to remove the Change Advisory Board Member as the application owner.

  5. Click SUBMIT.

  6. Navigate to SHOW LIST on the ACTION The name of the Change Advisory Board Member is not displayed.
Analyst is now able to remove the Change Advisory Board Member successfully from the change category and is not facing issue with Change Advisory Board page.
100103Auto Work order was not getting generated if the SR was raised on behalf of the Approver but was getting auto approved since the Approver was same as caller of the SR.

Prerequisites: 

 

  1. Create Catalog with 2 Approval levels with same user.

  2. Configure the Request > WORKORDER - CATALOG MAPPING.


Steps: 

  1. Login as Analyst.

  2. Navigate to Request > New Service Request For User.

  3. Select the Requestor as same user as Approver of Catalog.

  4. Log the SR.

  5. Navigate to Request > SR List.

  6. Open the logged SR and click the Relationship Tab.

 


Auto Work order is getting generated successfully for the SR raised by the Approver and Relationship tab the Work Order is linked to the SR.
103788In Service Request Catalog Workflow, under Condition, the PROPERTIES of condition option were greyed out. 

Prerequisite: 

Create a Service Catalog with many Custom attributes. 

Steps:

  1. Navigate to Workflow. 
  2. Navigate to Activity > Condition > Properties 
The Condition PROPERTIES in the Workflow will be available. 
103347The number of the Change Records displayed as per the filter option Registration Date values Today, Yesterday, and so on was incorrect. The issue persisted in the Change Management, Incident Management and Service Management modules too.

Prerequisite: 

Ensure you have active Change Records, Incidents, Service Requests created on the current day, last day, etc. in the Change, Incident, Request modules. 

Steps:  

  1. Navigate to Change or Incident or Request > User > Change Record or Incident or Service Request List.  
  2. Select Registration Date/Log time as a Field value. Select = in the Operator and Today, Yesterday, Last Week or any other date in the Value field. 
  3. Click Apply. 
  4. Verify the count of the records displayed in the corresponding List pages.
The number of change records, Incidents or Service requests displayed in the corresponding list pages is correct as per the filter options selected.  
99946IDM integration shows success but not updating issue with mobile number, contact number and password mandatory while updating User details. 

Prerequisite: 

The following API request must be used.


 View API Request
{ 

    "ServiceName": "ADM_CreateorUpdateUser", 

    "objCommonParameters": { 

        "_ProxyDetails": { 

            "APIKey": "v55i0Q8G3wAlX1YmUG4aYVXz57T2buYztnQgUxySo2A=", 

            "AuthType": "APIKEY", 

            "ProxyID": 0, 

            "ReturnType": "JSON", 

            "orgid": 1 

        }, 

        "UniqueField": "NT_UID", 

        "Users": [ 

            { 

                "UserName": "ABC", 

                "EmployeeId": "", 

                "Password": "*****", 

                "Login_ID": "abc@xyz.com", 

                "DomainName": "pqrs", 

                "EmailId": " abc@xyz.com ", 

                "ManagerEmailId": "", 

                "ManagerEmployeeID": "", 

                "Manager_NT_UID": "", 

                "MobileNumber": "", 

                "NT_UID": "dv114957test", 

                "RoleTemplate": "Super Admin", 

                "Designation": "Commercialisation & Labelling Assistant", 

                "Joindate": "", 

                "Address": "", 

                "Location": "", 

                "City": "", 

                "ContactNumber": "", 

                "State": "", 

                "Country": "", 

                "Customer": "Summit", 

                "TimeZone": "(UTC - 02:00) FNT - Fernando de Noronha Time", 

                "UserLevel": "", 

                "ZipCode": "", 

                "LoginType": "FORM", 

                "APIKeyExpiry": "", 

                "Remarks": "", 

                "UserType": "", 

                "AlternateMailID1": "", 

                "AlternateMailID2": "", 

                "AlternateMailID3": "", 

                "AlternateMailID4": "", 

                "SortOrder": "0", 

                "IsLocked": "0", 

                "Active": "False", 

                "checkboxcustomattributes": [], 

                "CustomAttributes": [                 

                ] 

            } 

        ] 

    } 

}

Steps: 

  1. With the unique field as NT UID, on passing the above payload successful response should be obtained. Successful Response must be obtained for this. 

2. Enter unique API key and do not enter –

   a. Mobile Number

    b. Password

   c. Contact Number  

Successful Response must be obtained for this. 

3. Enter unique API key and do not enter Mobile Number. In Designation field, Username, Remarks, Country, Address enter ‘&’ as values. Verify in the application the created User should be configured with the fields as entered. 

4. Enter unique API key and make Employee ID as unique field. Verify for appropriate response. 

5. Enter unique API key and make Email ID as unique field. Verify for appropriate response.

6. Enter unique API key and make FORM as unique field. Verify for appropriate response. 

The IDM integration now successfully updates the mobile number, contact number and password mandatory while updating the User details. 

Asset Management

Issue IDIssue Description ScenarioResolution 
102683On the Patch details page of the ASSET INVENTORY, the information displayed in the “Is Patch Downloaded to Proxy” column was incorrect whereas, the “Is Patch Downloaded” column in the Patch Details by Proxy pop-up of the PATCH MANAGEMENT displayed the proper information. 

Steps: 

To view the Patch details in the Asset Inventory: 

  1. Navigate to Asset > User > Manage Assets > Asset Inventory. 
     
  2. Select Fixed Asset type from the Select the Asset Type grid. 
     
  3. Select the Tenant, which is a mandatory field. 
     
  4. Consider the desired Category, and Asset Type and click the Asset count hyperlink. 
    The Fixed Asset List page is displayed. 
     
  5. Click the desired Asset ID count hyperlink. 
    The Asset Details pop-up is displayed. 
     
  6. Select Patch Details from the left panel.
    The Patch details of the respective asset are displayed. 

    

 To view the Patch details in the Patch Management: 

  1. Navigate to Asset > CONFIGURATION > Patch Management > Configuration. 
     
  2. Select the Tenant, which is a mandatory field. 
     
  3. Select the Regional Proxy from the drop-down. 
     
  4. Select the Patch Details by Proxy option from the right ACTIONS panel. 
    Patch Details by Proxy pop-up is displayed. 
 The Patch details in the Asset Inventory and Patch Management are in synchronization after the resolution. 
103105When the User imported Software Assets through the Excel import option, the application rounded off the Service Pack number (when it was in decimals) and displayed “Invalid Data” in the preview. 

Steps:

  1. Navigate to Asset > User > Manage Assets > Import > Import Asset. 
    Import Asset page is displayed.

  2. In the GENERAL tab, select the desired Tenant, Category, Asset Type, and Import Type from the drop-down. 

  3. Upload the source file in the Source option. The maximum size of the file must be 4MB. 

  4. Select the Primary Field from the drop-down.
    Click SUBMIT.

  5. In the MAPPING tab, select the relevant Source from the drop-down.
    Click NEXT. 

  6. In the PREVIEW tab, check the data under the Service Pack column. 
 The Software Assets import through Excel works fine and the Service Pack number data is displayed properly after the resolution. 
105958

The following error message was displayed on the Software Delivery page when the user tried to perform the Software Delivery Schedule action: 

 “Oops! An error occurred.” 

The error occurred when the Asset Management option was selected under the Source section and Hostname, or IP Address was selected as Attributes. 

Steps: 

  1. Navigate to Asset > User > Software Delivery > Software Delivery Schedule. 
     
  2. In the SELECT SOFTWARE tab, select the Tenant from the drop-down in the FILTERS pop-up, which is a mandatory field. 
     
  3. Select the desired Software Type from the drop-down. 
    The Software List is displayed. 
     
  4. Select the desired Software in the checkbox. 
    Click NEXT. 
     
  5. In the SELECT TARGET DEVICE tab, select the Source as Asset Management from the drop-down, which is a mandatory field. 
     
  6. Select the Location and Customer from the drop-down, which is a mandatory field. 
     
  7. Select the desired Asset Category from the Category drop-down. 
     
  8. In the Attributes section, select the Hostname or IP Address checkbox.
    Click the “>” symbol to select the attributes. 

     

The Software Delivery Schedule works swiftly and displays the Selected Attributes after the resolution.  


Platform

Issue IDIssue DescriptionScenarioResolution
103899An ‘Field contains duplicate options’ error message displayed in the Incident module when adding or modifying a Form builder.

Prerequisites

 

  1. Navigate to Admin > Form Builder.
  2. Select Incident Module from the Module
  3. Click Next, to view Form Builder page.
  4. Select Autofill Control and edit the options from left panel.
Click Next.		User could add or modify the Form Builder in Incident Management module successfully.
102386In the Old Mobile App, configured Category-based Workgroup name was displayed in the Analyst Detail page even after Workgroup name was changed from Web App.

Prerequisites

  1.  Navigate to Incident > Incident Master > Category.
  2. Select a Tenant from the list.
  3. Right-click a Category and click Configure.
  4. Select the Enable Location-wise Workgroup Routing
  5. In the Routing conditions section, select Location as Select All Location and select a Workgroup from the Workgroup field.
  6. Click SUBMIT.

Steps:

  1. Login to SummitAI application.
  2. Navigate to Incident > New Incident.
  3. Create a new Incident.
  4. Select the created Incident ID > Re-assign the Workgroup name> Click SUBMIT.
  5. Login to Old Mobile App.
  6. Navigate to the Workgroup Incident list page > Check the updated workgroup details on Analyst Detail page.
The updated Workgroup name displays correctly in the Incident listing page of the Old Mobile App.
105140Service Request raised from Mobile App unable to search globally. 

Prerequisites

  1.  Navigate to Mobile App.

  2. Raise a Service Request.

  3. Try to search the created Service Request
Service Requests raised through Mobile App could be searched successfully. 
102530In the New Mobile App, the SSO login page device keyboard was not displayedN/AThe device keyboard displays as expected.


Operation Management

Issue IDIssue DescriptionScenarioResolution
103438

CPU and Memory utilization monitoring was assigning old, cancelled Incidents for newly violated events. 

Also, the newly violated incident was not displayed in Event List tab. 

Prerequisite 

Incident template should be set to manual resolve. 

Steps 

  1. Create Incident for either RAM or CPU parameter of the server by violating its threshold value. Example: RAM parameter. 
  2. Change the status of the Incident to Cancelled.
  3. Make the threshold to less than actual utilization like Normal.
CPU and Memory utilization monitoring do not assign old, cancelled incidents for newly violated events, instead new Incidents are created. 

Orchestration

Issue IDIssue DescriptionScenarioResolution
101616

Orchestration Scripts were not linked to the Service Request when Service Request was resolved after all Work Orders were resolved. 

Prerequisites: 

  1. Create a Service Catalog by enabling the checkbox Resolve Service Request and publish the Service Catalog. 
  2. Configure Work Order Catalog Mapping for the above configured Catalog. 
  3. Configure Orchestration for Service Request, Resolved status and Select trigger event as Create/Update -Populate always option. 
  4. Raise the Service Request. 

Steps

  1. Navigate to Request > Service Request List
  2. Select the Service Request raised earlier.
  3. In the Service Request Details page, Navigate to RELATIONSHIP tab.
  4. Click the Work Order ID and resolve the Work Order. Service Request also gets resolved. if the resolved Work Order is the last Work Order in the Service Request.
  5. Click the Service Request ID in RELATIONSHIP tab of the Resolved Work Order.
  6. In Service Request, verify under ORCHESTRATION tab if the scripts are getting linked.
The Orchestration scripts are now linked to Service Request when final or last Work Order is resolved. 

Known Issues 

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


Issue ID


Issue Description

Scenario

Workaround <if applicable>

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

Prerequisites: 

  1. Log in to SUMMIT Application with Admin module access. Have few tenant values configured with access to Asset Management module. 

  2. Software package should be configured/created with package source as 'FTP' with valid credentials. 

  3. SAM Agent should be configured. 

  4. End User machine should be in successful contact. 

Steps: 

  1. Log in to SUMMIT Application. 

  2. 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).