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

« Previous Version 3 Current »

Download Release Notes | 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 SP1 HF04 << Denali SP1 HF05

What's New? | Customer Fixed Issues and Known Issues | Prerequisites | Installation, Configuration, and Upgrade | Security Best Practices for SummitAI Application Deployment

On this page: Customer Fixed Issues | Known Issues 

Customer Fixed Issues 

This section describes the issues reported by the customers and their fixes in Denali SP1 HF06. The bug fixes for the bugs found in the following version are also merged with this release. Please refer to the respective Release Notes for details.

#IssueResolution

 81584

On the CHANGE HISTORY pop-up, the Assigned Workgroup and Assigned To values were not captured under the New Value column. This issue occurred when an Incident was moved from a Workgroup and an Analyst to another Workgroup and Analyst.

The CHANGE HISTORY pop-up is displayed upon clicking Incident > User > Manage Incidents > Incident List > Click the required Incident ID > Click CHANGE HISTORY on the ACTIONS panel

Now, the Assigned Workgroup and Assigned To updated values are getting captured under the New Value column on the CHANGE HISTORY pop-up.

81972

The Analyst was not able to unselect the selected vendor from the Vendor drop-down. The Vendor drop-down retained the old value even after the same is unselected and submitted.

The Vendor drop-down can be selected using Incident > User > Manage Incidents > Incident List > Click on Incident ID > Click VENDOR INFORMATION tab

Now, the Vendor drop-down is not retaining the old value when the same is unselected and submitted.

82896

The Response SLA Violation Reason was non-mandatory when a Service Request with response SLA violated moved from New to Pending status.

Now, the Response SLA Violation Reason is mandatory when a Service Request with response SLA violated is getting moved to Pending from New status.

82612

On the CHANGE RECORD DETAILS page an error message, “Please select approver for User Selectable”, was displayed when the authorizer adds users for user-selectable approvers and clicks SUBMIT. This issue occurs when you have create workflow with two user selectable approvers and you have selected Authorization at Users who can Add Approvers drop-down for both of them.

The CHANGE RECORD DETAILS page can be accessed using Change > User > Change Record List> Click the required CR NO.


Now, no error message is getting displayed when the authorizer adds users for user-selectable approvers and click SUBMIT.

81232

On the New User page, the Designation field dropdown list was not in alphabetic order.

Following enhancements are made to overcome this:

  • A new Search option is introduced in the Designation field.
  • The Designation field dropdown list is displayed in alphabetic order.

81780

There is an overlapping issue on the following pages:

  • On the New Incident page and New Service Request page, the Tenant name was found to be overlapping with the Details section.
  • On the Analyst Dashboard page, the Response SLA summary and Resolution SLA summary graphs of both SR and IM modules are overlapped.
Now, the overlap issue is fixed on all the applicable pages listed in the Issue description.

80304

On the Service Request List page, the Service Requests Updated Time was displayed incorrectly.

The Service Request List page is displayed upon clicking Request > User > Manage Service Requests > Service Request List.

Now, the Service Requests Updated Time is displayed correctly.

84009

When simultaneously CR is approved, except the first approver, the error message was shown to the remaining approver(s), even after reloading the page it was not allowing the approver to submit the CR. 


To overcome this issue, the existing validation message changed to “This Change Record is modified after the Change details are loaded. Refresh the page before saving. Click here to refresh”.


Now, the approvers can use the “Click here” hyperlink from the message to refresh the page and make the required changes.
84010

If the Initiator and Approver both are same then user could approve the CR even if Do Not Allow CR Approval check box was enabled at Tenant level.

This issue occurs for Dynamic, Individual and User Selectable approval levels.

Now, if the Initiator and Approver both are same, the user cannot approve the CR.

Also,

  • Dynamic approver
  • Individual approver and
  • User Selectable approvers 

cannot approve the CR.

80668

The Incident was not logged using the Mail to Ticket functionality, but the E-mails were moved to the processed E-mails folder.  This issue occurred when two different User-Defined key values were specified as an E-mail Subject.

Example:

Subject: Network Devices

Where Network and Devices were two different User-Defined key values of User-Defined Key (Subject).

Now, the E-mail is getting converted into an Incident successfully even though two User-Defined key values are specified as an E-mail Subject.


83203

When the GDPR was enabled in the application, the Service Requests were not getting created using API key and the application was showing conversion error. This issue occurred because few of the GDPR sensitive fields such as Address, City, State, Pin, and so on were not encrypted while consuming the API.


Now, when the GDPR is enabled and the user tries to create the SR through API key then all the GDPR sensitive fields such as Address, City, State, Pin, and so on are encrypted. Hence, no conversion error is shown.

73812


The Movement Returnable Asset e-mail notifications were sent to the recipient even though the Asset Alert Configuration was not configured for that particular location. Example: The Movement Returnable Asset e-mail was configured for Bangalore location only, but the recipient of Mysore location received the e-mail notification on moving the Asset from in-store to Mysore location.

Now, the Movement Returnable Asset e-mail notifications are not sent to the recipient of other locations for which the Asset Alert Configuration is not configured.

82739

  While updating the Assets in bulk from the IMPORT ASSET page, the application was performing the Update action instead of Add action and validating the number of remaining licenses while updating the Assets.

Now, while updating the asset in bulk from the IMPORT ASSET page, the application is performing the Update action correctly hence, it is not validating the number of remaining licenses while updating the assets

81831

On the SEARCH ASSET page, all the transactions such as Add, Allocate, and Deallocate of the Accessories were displayed in a separate row under the DETAILS section while performing the search action. Due to this, a mismatch in Accessories quantity is observed.

Now, only the final transaction of the Accessories is displayed on the SEARCH ASSET page. Hence, no mismatch in the Accessories quantity is observed.

80590

After allocating Assets, the e-mail notification was not sent to the configured recipients. Whereas, upon de-allocating the same assets, the e-mail notification was sent to the configured recipients.

Now, after allocating and/or de-allocating Assets, the e-mail notification is sent to the configured recipients.

80217


When the Asset was returned from the Repair status and the asset movement Approver had rejected the Asset then on the RETURN FROM REPAIR page, data was auto cleared for the Vendor Details, Date, and Remarks fields. Also, while resubmitting the asset from the same page, an error message “Oops! An error occurred” was displayed. 

Now, after the Asset movement Approver rejects the asset then on the RETURN FROM REPAIR page, data for the Vendor Details, Date, and Remarks fields are not auto-cleared. Also, while re-submitting the Asset from the same page, no error message is displayed

81959

The Response of the Get attachment API was displayed in an incorrect format.

Now, the correct Response format is displayed for the Get attachment API.

82694

Post Denali SP1 HF03 B004 update, username is not displayed in the License Monitoring page for global domain users who are logged in as a concurrent analyst to another subdomain.

Now, Username is successfully displayed for global domain users post upgrade.
80103

User was unable to save data on the Scripting page because the Control_Attributes column details was not available in the ADM_DScript_Details table.

The issue occurs when the user has written a script in a version older than Alps when scripting wasn’t implemented and then writes a script in a version where scripting is implemented.

We have modified the Store Procedure (SP) to populate the Control_Attributes column data in the ADM_DScript_Details table.

Now, the data is saved successfully when user submits the Scripting page.

Known Issues 

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

Issue

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.

(#73532)

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.
(#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.

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