Customer Fixed Issues and Known Issues Tahoe HF24

Owned by Enterprise IT
May 08, 2024
22 min read

 Previous Versions: << Sierra << Sierra HF01 << Sierra SP1 << Sierra SP1 HF01 << Sierra SP1 HF02 << Sierra SP1 HF03 << Denali << Denali HF01 << Denali HF02 << Denali HF03 << Denali SP1 << Denali SP1 HF01 << Tahoe << Tahoe HF01 << Tahoe HF02 << Tahoe HF03 << Tahoe HF04 << Tahoe HF05 << Tahoe HF06 << Tahoe HF07 << Tahoe HF08 << Tahoe HF09 << Tahoe HF10<< Tahoe HF 11 << Tahoe HF12 << Tahoe HF13 << Tahoe HF14 << Tahoe HF15 << Tahoe HF16 << Tahoe HF17 << Tahoe HF18 << Tahoe HF19  << Tahoe HF20  << Tahoe HF21  << Tahoe HF22 << Tahoe HF23


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

 

On this page: Customer Fixed Issues | Known Issues 

Hotfix Merges

The following Hotfixes are merged with this release. Please refer to the respective Release Notes for details.

Resolved Issues

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

Service Management

Issue IDIssue DescriptionScenarioResolution

125488

When special characters were input in the Description and Symptom text boxes while raising an incident, the IM_GetCallerIncident API failed to fetch caller ticket details.

Steps:

  1. Log in to the Summit application.

  2. Navigate to Menu > Incident > User > New Incident.

  3. Enter the required details with special character ‘&’ in the Description and Symptom.

  4. Click Submit.

The IM_GetCallerIncident API fetches caller ticket details without any issues.

130518

The entries under the Mail History section, in Change History screen were sorted in ascending order whereas the rest of the Change History screen were sorted in descending order.

Prerequisite:

Configure 'SMTP Configuration'.

Steps:

  1. Navigate to Incident > User > Click New Incident for User.

  2. Enter the Caller name and Tenant.

  3. Enter all mandatory fields.
  4. Click Submit > Incident ID will be displayed.

  5. Open the created Incident ID.

  6. Update the any values like Private Logs and User Communication and change the Status.
  7. Click Submit.
  8. Open the created Incident ID.
  9. Navigate to Actions panel > Click Change History.
  10. Verify Mail History data.

The entries under the Mail History section are sorted in a uniform order across all the Change History screens.

130385

When the approver referred a Change Request (CR) to the previous level for Approval, the refer back email notification was not getting triggered to the previous level approvers.

Steps:

  1. Navigate to Change > User > New Change Record > Enter the mandatory Details > Click SUBMIT. 

  2. Navigate to Change > User > Approve Change Records. The APPROVE CHANGE RECORDS LIST page is displayed.

  3. Click Filters and select the Approval Status as Pending For Action > A list of CR’s awaiting your approval is displayed under LIST table.

  4. Click the CR No. of the Change Record. On the CHANGE RECORD ID page, click APPROVAL icon on the ACTIONS.

  5. On the APPROVAL pop-up page, select the approval status from the list > Specify your remarks and click SUBMIT.

  6. Refer back the Change Record to the previous level approval. 

The refer back email notifications are getting triggered to the previous level approvers. 

130613

Duplicate Incident reminder emails were sent when reminders were set on the Incident ticket.

Steps:

  1.  Navigate to Incident > User > Manage Incident > Incident List.

  2. Access the logged Incident.
  3. Go to right side ACTIONS > Reminder. 
  4. Select the ‘Self’ checkbox and configure the reminder by selecting the date and time.  

Duplicate Incident reminders are not getting triggered after the resolution.      

133327

When an incident is created with the “copy incident” feature and a template is selected, the category field displays the old value on hover.  

Prerequisites:  

  1. The selected template should have a category configured.  

Steps:  

  1. Navigate to Incident > Incident list.  

  2. Select an incident with a value in the category field.  

  3. Click Copy Incident under the Actions panel.  

  4. After the incident is copied, click Template under the Actions panel. 

  5. Select the required template with a preconfigured category. 


On hover, the category field for the new incident shows the new value.  

130026

A new SAM report – Software Installation Details Report by Vendor- must be configured.  

Steps: 

  1. Navigate to Reports > Asset Management > Software Installation Details Report by Vendor.  

  2. Select the required fields on the filter and Submit.  

A new SAM report – Software Installation Details Report by Vendor- is configured. 

The hyperlink grand total of installations is clickable.  


133652

On the dashboard, the Knowledge Record option was getting displayed within the context of Edit Profile page.

Steps:

  1. Navigate to Admin > Infrastructure > Themes > Theme Configuration. The Theme Configuration page is displayed. Configure a Theme.

  2. Select the same theme for the user using Profile > Edit Profile > Select Theme > Theme. Click Submit.

  3. Select landing page as User Dashboard for the user using Profile > Edit Profile > Select Landing Page > Landing Page.

  4. Log out and re-login.

  5. Click Knowledge Record option. The Knowledge Record pop-up is displayed.

  6. Click Profile > Edit Profile. 

On Dashboard, the Knowledge Record option is not getting displayed within the context of Edit Profile page.

126389

An incident  (via API) is created even if the description is less than 20 characters. However, when trying to update the ticket it throws an error. "Errors":"Description should not be less than 20 

Manual ticket update works even if the symptoms is less than 20 characters.  


API for IM_LogOrUpdateIncident Create  

Sample Request 
{ 

    "objCommonParameters": { 

        "incidentParamsJSON": { 

            "IncidentContainerJsonObj": { 

                "Ticket": { 

                    "Status": "New", 

                    "Category": 221, 

                    "Description": "Testing description for characters.", 

                    "Urgency_Name": "test1", 

                    "CI_ID": "", 

                    "IsFromWebService": true, 

                    "Sup_Function": "Info", 

                    "SLA_Name": "9 to 6", 

                    "PageName": "TicketDetail", 

                    "Source": "Person", 

                    "Assigned_WorkGroup_Name": "Network WG", 

                    "Priority_Name": "\"IT P2\"", 

                    "Caller_EmailID": "abc.sg@xyz.com", 

                    "Medium": "Web", 

                    "OpenCategory": 221, 

                    "Classification": 217, 

                    "Impact_Name": "IT Impact 3" 

                }, 

                "CustomFields": [], 

                "Updater": "Executive", 

                "TicketInformation": { 

                    "InternalLog": "#InternalLog#", 

                    "UserLog": "", 

                    "Information": "Symt." 

                } 

            } 

        }, 

        "_ProxyDetails": { 

            "SAASOrgID": "0", 

            "LoginUID": 0, 

            "RequestType": "mobile", 

            "MobileVersion": "5.10.3", 

            "Password": "test@123", 

            "AuthType": "FORM", 

            "ProxyID": 0, 

            "OrgID": "1", 

            "TokenID": "", 

            "ReturnType": "JSON", 

            "UserName": "abc.efg@xyz.com" 

        }, 

        "RequestType": "RemoteCall" 

    }, 

    "ServiceName": "IM_LogOrUpdateIncident" 

}

API for IM_LogOrUpdateIncident Update  

Sample Request 
{ 

    "objCommonParameters": { 

        "incidentParamsJSON": { 

            "IncidentContainerJsonObj": { 

                "Ticket": { 

                    "Ticket_No": "47450", 

                    "Status": "Assigned", 

                    "Description": "Description characters length testing.", 

                    "Assigned_WorkGroup_Name": "Network WG", 

                    "CancelRemarks": "", 

                    "Caller_EmailID": "abc.sg@xyz.com", 

                    "Medium": "Web", 

                    "IsFromWebService": true, 

                    "Sup_Function": "Info", 

                    "PageName": "TicketDetail", 

                    "Source": "Person" 

                }, 

                "TicketInformation": { 

                    "InternalLog": "#InternalLog#", 

                    "UserLog": "UserId:zp8si<br><label for=\"fname\">First name:</label><br>\n  <input type=\"text\" id=\"fname\" name=\"fname\" value=\"John\"><br>\n  <label for=\"lname\">Last name:</label><br>\n  <input type=\"text\" id=\"lname\" name=\"lname\" value=\"Doe\"><br><br>\n  <input type=\"submit\" value=\"Submit\">", 

                    "Information": "Update." 

                } 

            }, 

            "Updater": "Executive" 

        }, 

        "_ProxyDetails": { 

            "SAASOrgID": "0", 

            "LoginUID": 0, 

            "RequestType": "mobile", 

            "MobileVersion": "5.10.3", 

            "Password": "test@123", 

            "AuthType": "FORM", 

            "ProxyID": 0, 

            "OrgID": "1", 

            "TokenID": "", 

            "ReturnType": "JSON", 

            "UserName": "abc.efg@xyz.com" 

        }, 

        "RequestType": "RemoteCall" 

    }, 

    "ServiceName": "IM_LogOrUpdateIncident" 

}

After making changes to the API, the ticket updating works as expected. 

API for IM_LogOrUpdateIncident Create  

Sample Response 
{ 

    "Errors": "Symptom should not be less than 10 characters.", 

    "Input": null, 

    "Message": "Not able to save ticket details.", 

    "OrgID": 0, 

    "Output": null, 

    "OutputID": 0, 

    "OutputObject": null, 

    "TokenID": null, 

    "Priority": null, 

    "ResolutionDeadLine": null, 

    "Resolution_DeadLine": null, 

    "SLA": null, 

    "TicketID_Encrypted": null, 

    "TicketID_Internal": 0, 

    "TicketNo": 0 

}

API for IM_LogOrUpdateIncident Update  

Sample Response 
{ 

    "Errors": "Symptom should not be less than 10 characters.", 

    "Input": null, 

    "Message": "Not able to save ticket details.", 

    "OrgID": 0, 

    "Output": null, 

    "OutputID": 0, 

    "OutputObject": null, 

    "TokenID": null, 

    "Priority": null, 

    "ResolutionDeadLine": null, 

    "Resolution_DeadLine": null, 

    "SLA": null, 

    "TicketID_Encrypted": null, 

    "TicketID_Internal": 0, 

    "TicketNo": 0 
}

Asset Management

Issue IDIssue DescriptionScenarioResolution

132147

The following software Microsoft 365 Apps for enterprise -en -us which was installed was not displayed under the Software Discovery page (Details or Summary) when the user discovered the asset by using Sam Agent version 2.2.4.35. 

 

 

Steps:  

  1. Navigate to Reports > Asset Management > Agent Online Status Report. 
     
  2. In the FILTERS pop-up, select the desired options and click SUBMIT. 
    Agent Online Status List is displayed. 
     
  3. For the desired record, click the Serial Number hyperlink. 
    Asset Details pop-up is displayed. 
     
  4. Under Asset Information > Software Discovery, verify the details displayed. 
     
  5. In the Type drop-down, select Summary / Detail and verify the results displayed. 

The following software Microsoft 365 Apps for enterprise -en -us will be displayed under the Software Discovery page (Details or Summary) when the user discovers the asset by using the latest Sam Agent version 2.5.6.18 (or later versions). 

 

Known Issues 

This section describes the known issues detected by the SummitAI Dev and QA team from previous releases. 

Issue Number

Issue Description

Scenario

Workaround

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:

  1. Log in to the SummitAI application as an Approver.

  2. Navigate to Request > Service Request List.

  3. Click the newly created SR ID hyperlink.

N/A

92233

On submitting the cloned CR, the following message is displayed:

“The Standard Template is mandatory.”

Prerequisites:

  1. Navigate to Change > User >New Change Record. The NEW CHANGE RECORD page is displayed. Enable the check box Propose for Standard Change. Enter the value for Standard Template Name and Proposal Justification, and click SUBMIT after mentioning other mandatory fields. A new CR ID is created.

  2. Authorize this newly created CR and click on the CLONE CR tab under Actions panel.

  3. CLONE CR pop-up is displayed. Enable all the check boxes and click Clone. A New CR page will be displayed. Enter the value at Standard Template Name, Proposal Justification and other mandatory fields and click SUBMIT.


NA



Issue

An Administrator has remapped the Resigned approver approvals to a new approver in the Resigned Approver List. Before the original approver has resigned, an asset task for floor or store movement is awaiting approval. It is now assigned to the new approver as per action taken by Admin. The new approver is getting an information message "You are not an approver" on the Movement Approval page (Asset > Manage Assets > Approvals > Movement Approval) while approving an asset for floor or store movement. (#86330)

On Change Record List screen, the selected field value for the Tag filter is getting cleared when you select the field value for the Tenant filter as ALL. (#86329)

A sub-status that is not default, is deactivated even though the sub-status is assigned to an Asset.

Recommendation: To deactivate the sub-status, move the active Assets to another sub-status and then deactivate the sub-status. (#86269)

Full Name is not displayed under FIXED ASSETS upon selecting Dashboard > Asset Dashboard. This issue occurs when you have configured the Sub Status parent with 50 characters or more. (#86159)

Note

The Full Name is displayed, if you rotate the PIE Chart to 90 degrees.

The sub-status value of previously selected Tenant is retained still for the newly selected Tenant. For example, the sub-status value selected for a Tenant ‘IT Solutions’ is ‘server’. Now search for a different Tenant and select another Tenant as ‘Information Technology’. The sub-status value ‘server’ of previous Tenant is displayed incorrectly for the newly selected Tenant ‘Information Technology’. (#86273)

On the Remote Desktop Sharing screen, when you request for a Microsoft Teams meeting link (Advanced > RDP Type > Microsoft Teams) and click on Audit Log hyperlink under Session History tab, the message "Your request is processing please wait…" is displayed, but no further action is being made (#86297).

The formatting of Custom Attributes and Attribute Values using nicEditor on the User Communication tab of the Service Request Details page is missing when you click on the Print icon of the My Service Request Details page (#84048).

The text alignment of Custom Attributes and Attribute Values mentioned on the Service Request Details page is not getting displayed properly on the My Service Request Details page under the Additional Information tab (#83888).

On the notification window, the scheduled CAB meeting time is displaying incorrectly (#85493).

On accepting the meeting invite (calendar invite), the date and time are displaying incorrectly in the When field of the acceptance e-mail in the Sent Items folder (#84971).

On Microsoft Teams, the joined user details are displaying as 'U'(Undefined). But on hovering the mouse on 'U', the user details are displaying on the screen. This issue is happening only with the Admin account (#84966).

While sharing the screen, the selected screen is getting displayed multiple times and the screen gets stuck. Due to this issue, the data on the screen is not completely displayed. This issue is occurring only when the user logs in to the MS Teams desktop app as well as a browser app at the same time and tries to share the screen (#84978).

Admin is not getting any notification that users are waiting in the lobby when the Admin has opened the MS teams in two different browsers or two different devices (#84982).

On the COMMUNICATION HISTORY pop-up, the data (Custom attributes and its values) of the User Communication is not displayed in proper format and all the data is displayed in a single line without any delimiter. This issue occurred when Custom Attributes and their values were updated from the User Communication section on the SR Details page (#84018).

On the Communication tab and Change History tab of the Service Request Summary pop-up, the Custom attributes, and its values are not aligned properly. This issue occurred when Custom Attributes and their values were updated from the User Communication section on the SR Details page (#83893).

In the User Communication tab of the Service Request Detail page, formatting applied to Custom Attributes and Attribute Values using nicEditor is not retained in the End-User e-mail body when the ticket is updated.

(Bug# 84047)

In the Text Editor, when text alignment (Middle, Centre, Left) option is used, the UI alignment is not working as expected throughout the SummitAI application.

(Bug# 85770)

Following known issues are observed in the Problem Record Detail page for Mobile application:

  • When the RCA Approver refers back the PR, the RCA Approver Name and RCA Approve Date are not captured.
  • When the Reviewer refers back the PR, the Reviewer/Approver Name, Reviewer/Approver Date and Reviewer/Approver Status are not captured.
  • When the Reviewer rejects the PR, the Reviewer/Approver Name and Reviewer/Approver Date are not captured.

(Bug# 85946)

On the SEARCH ASSET page (ASSET > USER > MANAGE ASSETS > ASSET INVENTORY page > Click Non-Fixed Asset icon (Consumable, Accessories, or Software) > Click Search Asset icon), an error message "Oops! An error occurred" was displayed when the length of the specified search text is more than 30 characters. This issue exists for the following scenarios:

  • When in the search text field, a relational operator i.e., <, >, <=, or >= is specified to search Assets.
  • When the user tries to search Non-Fixed Asset.

(Bug# 73532)

For the Custom Attribute (Drop-down), if any value is set as default on the Form Builder page (Admin > Basic > Infrastructure > 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 > Drag and drop the Drop-down Custom Attribute > Type in the Label for the Custom Attribute > Select Options (data source) as Manual > Type in the Drop-down Values and Make one value as default), then the default value is not automatically set for that Custom Attribute (Drop-down) across the Incident Management module

(Bug# 71703).

If the SLA is paused during the PR resolution and the Paused Time is before RCA Deadline, the paused duration is not getting added to the Resolution Deadline. This issue is occurring when the Resolution Deadline Type is selected as RCA Deadline Time in the Deadline Configuration. (Bug#74495)

Note: 

If the SLA Paused Time is between RCA Actual Time and RCA Deadline, the paused duration does not consider for the Resolution Deadline.

Example:

Consider the PR Log Time as 9:00 AM, RCA Deadline as one hour, and Resolution Deadline two hours.

The paused duration does not add if the Analyst performs the below actions:

  • If the RCA completed at 9:30 AM (RCA Actual Time), where RCA Deadline is 10:00 AM.
  • If the Analyst pauses the PR at 9:40 AM to 9:50 AM before RCA Deadline Time (10:00 AM), the paused duration 10 mins is not getting added to the Resolution Deadline.

The Expected Resolution Deadline should be:

RCA Deadline Time + Resolution Deadline + Paused Time = 10:00 AM + 2 hours + 10 mins = 12:10 PM.

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

  1. 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).
  2. 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).
  3. 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:

  1. Login to the Application as Checker.
  2. Click Asset > User > Manage Asset > Approvals Maker-checker Approval > Click Filters on the ACTIONS panel.
  3. On the Filter pop-up page, select the Tenant and specify the required details.
  4. Select the Assets that you want to approve and click APPROVE icon on the ACTIONS The APPROVE pop-up page is displayed.
  5. On the APPROVE pop-up page, select the Approval Status as Approved to approve the Asset and click
  6. Click Asset > User > Manage Asset > Asset Inventory > Click FIXED under the SELECT THE ASSET TYPE section > Click Filters on the ACTIONS
  7. On the Filters pop-up page, select the Tenant, Select the Status as Allocated and specify required details.
  8. Click SUBMIT.
  9. Validate the data.
(Bug# 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:

  1. Log into the Application as an Administrator.
  2. Configure a Bulletin Board. For more information, see Configuring Bulletins.
  3. Send a POST request for the GetBulletinBoard API. Pass Tenant Code, in the Instance parameter and User ID in the UserID parameter.
  4. 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:

  1. Log into the Application as an Administrator.
  2. Select Admin > Advanced > Automation > Orchestration.
  3. On the WORKFLOW LIST page, click the NEW
  4. On the WORKFLOW CONFIGURATION pop-up page, select Module as Service Request, and specify other details to configure the Orchestration Workflow.
  5. Map the Target Host Type to From Previous Output value for the scripts of the Orchestration Workflow.
  6. Log out and log into the Application as an Administrator or as an Analyst.
  7. Select Request > Manage Service Requests > Service Request List.
  8. On the SERVICE REQUEST LIST page, specify the Filters and open an SR.
  9. On the SERVICE REQUEST DETAILS page, click the ORCHESTRATION tab.
  10. 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.
  11. 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.

On the IMPORT ASSET and ADD ASSET pages, the users can add multiple Assets with same Serial No., although, Serial No. is a unique field for Assets. This issue is found if Maker/Checker configuration is enabled. For example, a user added an Asset with Serial No. 123 and is pending for Checker’s approval. The user is able to add another Asset with same Serial No. 123. And send for Checker’s approval. The Checker is also able to approve two Assets with same Serial Number on the MAKER-CHECKER ASSET-APPROVAL page.

Bug Reproduction Steps:

  1. Select Asset > User > Manage Asset > Import > Import Asset.
  2. On the IMPORT ASSET page, under GENERAL tab, select the required options and upload the updated Asset Import Template. Click SUBMIT.
  3. Select the sheet to import the Assets. Click the Mapping tab and select the required options if not already selected.  Click Next.
  4. Click the Preview tab and select the store where you want to import the Assets from the Store list.
  5. Click IMPORT ASSETS TO QUEUE on the ACTIONS panel.
  6. Alternatively (Steps 1-5), select Asset > User > Manage Assets > Asset Inventory.  On the ASSET INVENTORY page, click FIXED.  On the ACTIONS panel, click ADD. On the ADD ASSET page, specify the required information and click SUBMIT.
  7. Add two Assets with same Serial Number.
  8. The Application allows to import or add two Asset with same Serial Number.
  9. Select Asset > User > Manage Assets > Approvals > Maker Checker Approval . On the MAKER-CHECKER ASSET-APPROVAL page, click Filters  on the ACTIONS panel. Select the Tenant. Select the Transaction Type as Add to view the list of requests from the Maker.
  10. The Assets with duplicate Serial Number are displayed. Click APPROVE on the ACTIONS panel. On the APPROVE pop-up page, select the  Approval Status as Approved.

(Bug#67236)

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.

(Bug#67240)

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