Customer Fixed Issues and Known Issues Alps SP1 HF14

Owned by Enterprise IT
May 09, 2024

Download Release Notes

<< Alps << Alps HF01 << Alps SP1 << Alps SP1 HF01 << Alps SP1 HF02 << Alps SP1 HF03 << Alps SP1 HF04 << Alps SP1 HF05 << Alps SP1 HF06 << Alps SP1 HF07 << Alps SP1 HF08 << Alps SP1 HF09 << Alps SP1 HF10 << Alps SP1 HF11 << Alps SP1 HF12 << Alps SP1 HF13

 

Customer Fixed Issues and Known Issues

Customer Fixed Issues

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

#

Issue

Resolution

73315


While copy-pasting an image under the User Communication field or Private Log of the Incident Details page, the same image was displayed twice. 

Now, the image is not displayed twice while copy-pasting an image under the User Communication field or Private Log of the Incident Details page.

74156 

On the CHANGE RECORD WORKGROUP REPORT, upon clicking on a CR number from the Change Record column, the user was navigated to the CHANGE RECORD LIST page where no details were displayed instead, a message “No Data” was displayed. This issue occurred when the From Date and To Dates were the same on the FILTERS pop-up page.

Now, upon clicking on the CR number, all the available details displayed on the respective CHANGE RECORD LIST page even though the From and To Dates are the same.

74317 

The additional Workgroup owner who was configured as Authorizer but deactivated from the User List, was still displaying as Authorizer on the AUTHORIZATION pop-up page of the Change Records.

Now, the only the active and configured user are displaying as Authorizer on the AUTHORIZATION pop-up page of the Change Records.

74116

On the Accessories ASSET DETAILS page, while navigating from the Movement History tab to Asset Register tab, the fields listed under the DEFAULT GROUP section were not displayed.

Now, while navigating from the Movement History tab to Asset Register tab, the fields listed under the DEFAULT GROUP section are displayed. 

71160 

The Hardware and Software variance e-mail notifications were sent to the unmapped recipients of the respective Location. Also, the variance information of different Locations was captured in the attachment. This issue was observed when there were a huge number of alert jobs that were scheduled to trigger the E-mail notification.

Now, the Hardware and Software Variance e-mail notifications are sent to the mapped recipients of the respective Location. Also, the variance information of the respective mapped Location is captured in the attachment.

74606 

While allocating Fixed and Non-Fixed Assets in bulk, the following issues were observed:

  • The Assets were not allocated to the users.
  • In the Remark column, the comment “Location and/or floor is not valid.” was displayed.

This issue was occurring when more than 50 characters were specified in the Location column of the uploaded excel sheet.

Now, while allocating the Fixed and Non-Fixed Assets in bulk, no issue is encountered even though the Location column of the uploaded excel sheet, contains more than 50 characters.

Note: The maximum length for the Location column is set to 500 characters.

75179

On the ACCESSORIES page, No Data was displayed instead of the filtered data. This issue occurred when more than ten characters were specified in the Attribute Value field of the FILTERS pop-up page.

Now, the filtered data is displayed even though more than ten characters are specified in the Attribute Value field of the FILTERS pop-up page.

73728 

 

The Assigned To user name was getting populated under the Change BY column of the Work Order Effort section on the CHANGE HISTORY pop-up page of the Work Order instead of logged user. This issue was occurring when Work Order Estimate was updated by user other than the Assigned To user.

Now, only the logged-in user name is populated under the Changed By column of the Work Order Effort section on the CHANGE HISTORY pop-up page of the Work Order when Work Order Effort is updated.

74531


Incorrect pending incident data was displaying on the PENDING INCIDENTS-SUMMARY DETAILS pop-up page when the user clicked the Total column hyperlink of the Pending Incident Report page. However, the details that were displayed in the Total column were correct as per the selected date range on the FILTERS pop-up page.

Now, the pop-up report is displaying the correct pending incident data as per the selected date range on the FILTERS pop-up page.

72421 

Incorrect percentage of the uptime report was displaying for a Server. This issue was occurring when a new Server was added later in the month, and the report was taken for the complete month.

Example:

Consider the following scenarios:

  • Server was added on 15th June.
  • Server was down from 15th to 22nd June.

The actual uptime report of the Server was 50%. But the Application was considering the Server uptime report from 1st June till 30th June and displaying the uptime report of the Server as 25%, which is incorrect.

Now, the uptime report of the Server is considering only the date from which the Server is added and the actual downtime.

74756 

The Log Service Request page was getting refreshed, and the details of the child attributes of another group was getting reset when values in the Multi-Valued group were submitted while raising a Service Request using Service Catalog.

Now, the details of the child attributes of another Group are not changed when values in the Multi-Valued group are submitted while raising a Service Request using Service Catalog.

71008

Duplicate Incidents were creating while monitoring the CPU and Memory utilization of the same Server and there was a violation. This issue was occurring when an Analyst tried to resolve the Incident manually.

Now, no duplicate Incidents are creating while monitoring the CPU and Memory utilization of the same Server and there is a violation.

75154

 

With SSO Auth type, upon clicking the login link after the idle session timeout, the user was redirected to the Error page instead of reauthenticating the login link and directing to the actual page. This issue occurred when the user logged in from a different URL other than the base URL or SSO login page.

Example

If the URL is used as:

Now, the login link is reauthenticated and directed to the actual page after the idle session timeout, even if the entered URL is different from the base URL.

Known Issues

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

Issue

The following two known issues are observed:

  • Duplicate Incidents are getting created while monitoring various parameters except for the CPU and Memory utilization. This issue occurs when an Analyst tried to resolve the Incident manually.
  • After configuring the Number of Polling on the ACTION TEMPLATE page, the Incidents are logged, and assigning incorrect Incident for the Events.

For Example:
Consider the utilization threshold values for Low, Medium, and High as 60%, 70%, 80% and Number of Polling for Incident Logging as 2. After the first polling there is a breach in Low threshold value and event gets created. On second polling there is High level breach and a critical event gets created.

The issue is, after the second polling an Incident is logged for the Low threshold breach and assigning the Incident to the Critical Event of the High threshold breach.

(#74254)

Consider a scenario where an Asset is first allocated to Multiple Users without Maker-Checker configuration and deallocated with Maker-Checker configuration. Again, the same Asset is allocated to Single User without Maker-Checker configuration. The Asset is displayed in the In-Store list instead of getting displayed in the Allocated Asset list. (#70998)

Bug Reproduction Steps:

  1. Log into the Application.
  2. Make sure that the Maker Checker configuration is disabled on the TENANT
  3. Add an Asset. For more information on adding an Asset, see Adding Fixed Assets.
  4. Select Asset > User > Manage Assets > Asset Inventory.
  5. Click FIXED on the ASSET INVENTORY On the FIXED ASSET page, click In-Store count.
  6. On the FIXED ASSET list page, select the check box corresponding to the Asset and click ALLOCATE on the ACTIONS
  7. On the ALLOCATE FIXED ASSETS page, under the ALLOCATION DETAILS section, select Multiple User in the Allocate To field and specify other fields. Click SUBMIT.
    Example:
    Allocate the Asset to multiple Users, such as sam.123@symphonysummit.com, and john.1@symphonysummit.com.
  8. On the TENANT page, enable the Maker Checker configuration.
  9. Select Asset > User > Manage Assets > Asset Inventory.
  10. Click FIXED on the ASSET INVENTORY On the FIXED ASSET page, specify the filter criteria and search the same Asset that is Allocated in steps 4 to 7. Click SUBMIT.
  11. On the FIXED ASSET list page, select the check box corresponding to the Asset and click DEALLOCATE on the ACTIONS panel.
  12. On the DEALLOCATE FIXED ASSET page, specify the required fields and click In-Store count.
  13. Make sure that the Asset Deallocation request is sent for approval on the Maker-Checker Approval page.
  14. Log into the Application as Checker Approver.
  15. Approve the Asset on the MAKER-CHECKER ASSET APPROVAL For more information on approving Maker-Checker Asset, see Approving Asset Using Maker-checker.
  16. Log out and log into the Application as an Administrator.
  17. On the TENANT page, disable the Maker-Checker configuration.
  18. Select Asset > User > Manage Assets > Asset Inventory.
  19. Click FIXED on the ASSET INVENTORY On the FIXED ASSET page, click In Store count.
  20. On the FIXED ASSET list page, select the check box corresponding to the same Asset that was allocated to Multiple Users and click ALLOCATE on the ACTIONS panel.
  21. On the ALLOCATE FIXED ASSETS page, under the ALLOCATION DETAILS section, select Single User in the Allocate To field and specify other fields. Click SUBMIT. 
  22. On the FIXED ASSET page, specify the filter criteria for Status as Allocated and click SUBMIT.
  23. On the FIXED ASSET page, the Asset is not displaying in the Allocated Assets list.
  24. On the FIXED ASSET page, specify the filter criteria for Status as In-Store and click SUBMIT.
  25. On the FIXED ASSET page, the Asset is displaying in the In-Store Asset list.

The Incident Description is getting cropped when an Analyst (with edit-rights) is editing the Incident Description using the Google Chrome browser. (#69984)

Bug Reproduction Steps:

  1. Log into the Application as an Administrator.
  2. Select Admin > Basic > Infrastructure > Tenant.
  3. On the TENANT page, specify the Filters criteria.
  4. On the TENANT LIST page, select a Tenant and click CONFIGURE DETAILS under ACTIONS panel.
  5. Select INCIDENT MANAGEMENT under MODULES and select Allow Analyst to Edit Description check box under the For Analyst section.
  6. Log into the Application as an End User.
  7. Select Incident > User > New Incident.

  8. On the New Incident page, in the Description fields enter text and an image copied from Web or other sources. Specify the other fields and click SUBMIT.

    Note:

    Make sure that the Description field includes both an image and text.

  9. Log into the Application as an Analyst using the Google Chrome browser.
  10. Select Incident > User > Manage Incidents > Incident List.
  11. On the INCIDENT LIST page, specify the Filter criteria and open the same Incident.
  12. Verify the Description field content. The Incident description is getting cropped.

The Username, E-mail ID, Emp Id, and values for few of the columns are not displayed in the columns under the DEALLOCATED ASSETS section on the ASSET DETAILS pop-up page when the Checker refers back Assets of Deallocation Transaction type.(#67805)

Precondition:

  1. Make sure that the Asset is allocated to Single User with Maker-checker.
  2. Make sure that the Asset is sent for Deallocation and Checker refers back the Asset.

Bug Reproduction Steps:

  1. Log into the Application.
  2. Select Reports > Asset >Maker-checker Dashboard.
  3. On the FILTERS pop-up page, select a Tenant, Location, and specify Referred Back in the Status. Click SUBMIT.
  4. On the MAKER-CHECKER DASHBOARD page, click Deallocated count hyperlink.
  5. Check the Username and E-mail ID for the Asset. The Username, Email ID, Emp id and values for few of the columns are not displaying under the DEALLOCATED ASSETS section on the ASSET DETAILS pop-up page

On the FIXED ASSET INVENTORY page, only added Assets with Maker Checker configuration are displayed when Referred Back is selected in the Checker Status drop-down list on the FILTERS pop-up page. (#65848).

Required configuration:

  1. Log into the Application
  2. Select Admin > Infrastructure > Tenant.
  3. On the TENANT LIST page, select a Tenant.
  4. On the TENANT page, click CONFIGURE DETAILS under ACTIONS panel.
  5. Select ASSET MANAGEMENT under MODULES.
  6. Select Enable Maker-Checker check box.

 Bug Reproduction Steps:

  1. Select Asset > Manage Assets > Asset Inventory.
  2. On the ASSET INVENTORY page, select FIXED under SELECT THE ASSET TYPE.
  3. On the FIXED ASSET page, select a Tenant.
  4. On the FILTERS pop-up page, select Referred Back in the Checker Status drop-down list. Only the added Assets with Maker Checker configuration are displayed.
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.

Overlapping of content is observed on the Pagination bar of all the pages having lot of records (typically in the range of 5 digits).

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.

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