Customer Fixed Issues and Known Issues Alps SP1 HF03

Owned by Enterprise IT
May 09, 2024

Download Release Notes

<< Alps << Alps HF01 << Alps SP1 << Alps SP1 HF01 << Alps SP1 HF02

 

Customer Fixed Issues and Known Issues

Customer Fixed Issues

This section describes the issues reported by the customers and their fixes in the release, Alps SP1 HF03.

#

Issue

Resolution

59205

On the OPEN INCIDENT REPORT page under the Reports drop-down list, the duplicate Incidents were getting displayed for some users This issue was found when a user was mapped to the User Type with the same name for two different Tenants.

 Bug Reproduction Steps:

  1. Log into the Application.
  2. Select Reports > Incident Management.
  3. Select the Open Incident Report under the Reports drop-down list.
  4. Select Filters. Specify the required details and click SUBMIT.
  5. Select the Details tab. Duplicate Incidents are displayed if the above-mentioned condition is met.

Now, the duplicate Incidents are not getting displayed on the OPEN INCIDENT REPORT.

 

59578

When an Analyst used a Notification Template with table format under the User Communication section of the COMMUNICATION tab on the INCIDENT DETAILS page, the table format was not getting displayed. This issue was found when the user tried to select a template with table format.

Bug Reproduction Steps:

  1. Log into the Application.
  2. Select Incident > User > Manage Incidents > New Incident for Users.
  3. Select the COMMUNICATION tab.
  4. Under the User Communication section, select a template with table format, and then click SUBMIT.

Now, the table format is displayed in the User Communication section under the COMMUNICATION tab of the Incident page.

59874

If a Knowledge Record was published, and the Workgroup Owner, say, John was Inactive, and the Workgroup Owner was changed to Roy. Roy was not able to edit the Knowledge Record or change its Status to Maintenance.

Bug Reproduction Steps:

  1. Log into the Application.
  2. Select Admin > Basic > Infrastructure > Workgroup. 
  3. On the WORKGROUP page, select the Owner and click SUBMIT.
  4. Create a Knowledge Record for the Workgroup and publish it.
  5. Change the Workgroup Owner of the Knowledge Record.
  6. Try to change the status of the published Knowledge Record or edit it by logging into the Application as the new Workgroup Owner. You cannot edit the Knowledge Record or change its Status to Maintenance.

Now, the Knowledge Records can be edited or moved to Maintenance Status by the new Workgroup Owner (Roy in our example).

58991

On the PIR REVIEWER page, if the Change Type was selected as any value (example: Normal) and Category as ALL, the PIR Reviewer was also able to close the Change Requests of different Change Types. For example, Change Type as Emergency and Category as All. This issue was occurring because the Application was taking Category ALL as Change Type ALL.

Bug Reproduction Steps:

  1. Log into the Application.
  2. Select Change > Configuration > PIR Reviewer
  3. Select Change Type, Category as All, and specify the PIR Reviewer. Click SUBMIT.
  4. Try to close a Change Record of a different Change Type. You can close Change Records of different Change Types too, which is incorrect.

Now, the PIR Reviewer can only close the Change Records for the Change Type they have access, and not to any other Change Records.

59656

The following issues were observed on the OPEN SERVICE REQUEST REPORT page.

  • SUMMARY BY PRIORITY tab: The count of Service Requests was not matching with their drill-down pages. This issue was occurring as the SRs that were logged without specifying Customer and Location were not considered.
  • SUMMARY BY WORKGROUP tab: The count of Service Requests was not matching with their drill-down pages as the total number of SR count was displayed for each Workgroup instead of actual Workgroup-wise count.

Bug Reproduction Steps:

  1. Log into the Application.
  2. Select Reports > SERVICE REQUEST from the MODULE drop-down list >
  3. Search and select Open Service Request Report. The count of Service Requests does not match with their drill-down pages.

The issues found on the OPEN SERVICE REQUEST REPORT page are now fixed.

  • SUMMARY BY PRIORITY tab:Now, the SRs that are logged without specifying the Customer and Location are also considered in the report. Hence, the count is matching with the drill-down pages.
  • SUMMARY BYWORKGROUP tab: Now, the actual Workgroup-wise SR count is displayed for each Workgroup. Hence, the count of Service Requests is matching with their drill-down pages.

59620

When an End User replied to the Incident Reminder e-mail for a pending Incident, a new Incident was getting created instead of updating the pending Incident. The issue was found in the E-mail Template Keywords. The word "IM" was not present as a prefix for the Incident Number in the subject line.

Bug Reproduction Steps:

  1. Reply to the Incident Reminder e-mail for a pending Incident.
  2. A new Incident is created instead of updating the pending Incident.

Now, the pending Incident is updated when an End User replies to the Incident Reminder e-mail.

 

58933

After updating Custom Attribute details of a CI under a Classification on the CI ID page, the Custom Attribute details of all the CIs belonging to the same Classification were getting auto-updated.

Bug Reproduction Steps:

  1. Log into the Application.
  2. Select CMDB > User > Configuration Item List.
  3. Select a CI and Click ADDITIONAL INFORMATION tab.
  4. On the CI ID page, update the Custom Attribute details of a CI under a Classification. The Custom Attribute details of all the CIs belonging to the same Classification were getting auto-updated.

Now, on updating the Custom Attribute details of a CI under a Classification, the Custom Attribute details of the specific CI only gets updated.

 

59388

If a Service Request was not mapped to a Customer, it was not getting displayed on the PENDING SERVICE REQUEST REPORT page.

Bug Reproduction Steps:

  1. Log into the Application.
  2. Select Reports > Service Request Module.
  3. Select Pending Service Request Report from the Reports drop-down.
  4. On the PENDING SERVICE REQUEST REPORT page, the Service Request which is not mapped to a Customer is not getting displayed.

Now, all the Service Requests are displayed on the PENDING SERVICE REQUEST REPORT page even if they are not mapped to any Customer.

57888

The fields configured for the General and Additional Info tab on the FORM BUILDER page were displaying properly for Incident and Service Requests page. However, when a Work Order was created from the Incident or Service Request, the fields were displayed as text boxes instead of the correct control types. This issue was found for E-mail, User, Website, File, Radio Button, and Multi Value Drop-down control types.

Bug Reproduction Steps:

  1. Log into the Application.
  2. Select Incident > User > Manage Incidents > Incident List.
  3. On the INCIDENT LIST page, select an Incident.
  4. Click on Relationship tab and select Create Workorder.
  5. On Workorder ID page, specify the required details. Click SUBMIT. The field of Work Order created from the Incident or Service Request, were displayed as text boxes instead of the correct control types.

Now, all the fields are displaying properly on the Work Orders.

58958

When a user opened the Others section of the OPERATING SYSTEM pie chart, the SERVERS FOR OPERATING SYSTEM heading on the SERVER DETAILS page displayed an operating system's name in place of "Others".

Required Configuration:

Make sure that operating systems count is more than 10 in the OPERATING SYSTEM pie chart. This enables the Others section in the OPERATING SYSTEM pie chart.

Bug Reproduction Steps:

  1. Log into the Application.
  2. Select IT Operations > Servers > Server Dashboard.
  3. Open the FILTERS pop-up page and specify the details. Click SUBMIT.
  4. Scroll down to the OPERATING SYSTEM pie chart.
  5. Click the Others section on the OPERATING SYSTEM pie chart.
  6. Check SERVERS FOR OPERATING SYSTEM heading on the SERVER DETAILS page. It shows an operating system's name in place of "Others".

Now, the SERVERS FOR OPERATING SYSTEM heading on the SERVER DETAILS page shows "Others" for the Operating System name.

59036

The Subject line of the Incident template displayed the default Keywords in place of their values. This issue was occurring when an Incident was logged due to Event Monitoring from the SummitAI IT Operations module after the SummitAI application was upgraded to the Summit Alps SP1HF01 version.

Required Configuration:

  1. Log into the Application.
  2. Select Admin > Notifications > Notification Template.
  3. Select a Tenant on the NOTIFICATION TEMPLATE page.
  4. Open a Template from Analyst Table under INCIDENT MANAGEMENT section.
  5. Configure the Subject field as '*URGENCY*-*SUP_FUNCTION*-*CALLID*-*WORKGROUP*' for Incident Workgroup e-mail.

 Bug Reproduction Steps:

  1. Trigger an Incident from Event Monitoring using the SummitAI IT Operations module.
  2. Check the Subject line of the e-mail notification. The Incident template Keywords were displayed in place of their values in the Subject line of the e-mail.

Now, the Subject line of the Incident template shows the correct values in the e-mail notifications triggered due to Incidents logged from Event Monitoring of the SummitAI IT Operations module.

57426

The CPU and MEMORY average utilization data was not getting displayed on the SERVER DETAILS page.

Bug Reproduction Steps:

  1. Log into the Application.
  2. Select IT Operations > User > Views > Server View.
  3. Open the FILTERS pop-up page and specify the details. Click SUBMIT.
  4. On the SERVER VIEW page, open a Server.
  5. Select CPU & MEM. tab on the SERVER DETAILS page.
  6. Check for Average utilization data. No data is displayed.

Now, the CPU and MEMORY average utilization data is displayed on the SERVER DETAILS page.

59018

On the END USER DASHBOARD page, when a user was searching for any Rule e in the Search and Log issue\Request field, the search results was displaying duplicate Rules. This issue was happening even if one Rule was configured on the Rule configuration page.

Bug Reproduction Steps:

  1. Log into the Application.
  2. Select Dashboard >End User Dashboard.
  3. Type in a Rule in the Search and Log issue\Request field. The search log shows he duplicate Rules.

Now, no duplicate Rules are displayed while searching for Rules on the END USER DASHBOARD page.

59825

On the FILTERS pop-up of the MASTER SETTINGS page when a user re-selected a different Tenant and Server values after the first submission, an error message was getting displayed.

Bug Reproduction Step:

  1. Log into the Application.
  2. Select Operation > Configuration > General > Master Settings.
  3. Open the FILTERS pop-up page and specify the details. Click Submit. 
  4. Reopen the FILTERS pop-up page and change certain filter criteria and re-submit. An error message is displayed.

Now, no error is displayed on changing the Tenant and Server values criteria and resubmitting the filter criteria on the MASTER SETTINGS page.

60086

Using the Dashboard menu, the users, who were not having access to view the Analyst Dashboard and Asset Dashboard, were able to select the Analyst Dashboard and Asset Dashboard menu items and view these Dashboards.

Required Configuration:

  1. Log into the Application.
  2. Select Admin > Basic > User > Role Template.
  3. On the ROLE TEPLATE page, select the appropriate Role Template.
  4. On the ROLE TEMPLATE - MENU CONFIGURATION page, select DASHBOARD under the MODULES menu.
  5. On the Dashboard section, uncheck the Asset Dashboard and Analyst Dashboard check boxes.

Bug Reproduction Steps:

  1. Log into the Application as a user who is not provided access to view the Asset Dashboard and Analyst Dashboard (as configured in the above steps).
  2. Select Dashboard > Asset Dashboard. The ASSET DASHBOARD page is displayed.
  3. Select Dashboard > Analyst Dashboard. The ANALYST DASHBOARD page is displayed.

 

Now, the options to view the various Dashboards from the Dashboard menu are displayed based on the user access.

60754

The Service Requests were getting assigned to the Analysts without getting approved by all the Approvers configured in the Approval cycle.

For example: If there are four Approvers, let’s say, Approver 1 is Harry, Approver 2 is Tom, Approver 3 is John and, Approver 4 is Nancy. After Harry and Tom approved an SR, the SR was getting assigned to an Analyst without the approvals from John and Nancy.

Bug Reproduction Steps:

  1. Log into the Application and click on the Service Request icon.
  2. Select User > New Service Request.
  3. Select the Tenant and the Catalog.
  4. Specify the Description and click SUBMIT.

Now, the Service Requests are assigned to Analysts after they are approved by all the Approvers configured in the Approval cycle.

59749

On the Analyst WORK ORDER LIST page, other Analysts’ Work Orders for the same Tenant were also displayed. This issue was found when the signed in Analyst had access to single Tenant.

Bug Reproduction Steps:

  1. Log into the Application.
  2. Select Dashboard > ANALYST DASHBOARD.
  3. Click ASSIGNED TO ME under Work Order section. Other Analysts’ Work Orders for the same Tenant were also displayed on the Analyst WORK ORDER LIST page.

Now, the Work Orders assigned to a specific Analyst are displayed on the WORK ORDER LIST page.

59523

On the RELATIONSHIP pop-up page of the INCIDENT ID page, when a user was searching for an Incident by typing in values in the Search field, it was taking a long time to display the search results.

Bug Reproduction Steps:

  1. Log into the Application.
  2. Select Incident > Manage Incidents > Incident List.
  3. Open the FILTERS pop-up page and specify the details. Click SUBMIT.
  4. On the INCIDENT LIST page, open an Incident.
  5. Open the Relationship tab and select the Incident under Link drop-down.
  6. On the RELATIONSHIP popup page, Type In the text in Text search field. Click SEARCH. It takes a very long time to load the result.

Now, when a user types in the text in the Search field and searches for an Incident, the search results are displayed much faster on the RELATIONSHIP pop-up page of the INCIDENT ID page.

59036

When an Incident logged from SummitAI IT Operations module was getting auto-resolved from the PENDING Status, the correct Elapsed Time By Workgroup was not calculated from the PENDING to another Status.

Required Configuration:

  1. Log into the Application.
  2. Select IT Operations > Configuration > General > Incident Template.
  3. On the FILTERS pop-up page and specify the details. It loads the INCIDENT TEMPLATE page.
  4. On the INCIDENT TEMPLATE page, open the Incident template auto-resolve.
  5. On the DETAILS section, select the Do Not Update check box.

Bug Reproduction Step:

  1. Select Incident > User > New Incident.
  2. Select IT operation in the Tenant list and specify the details. Click SUBMIT. An Incident is created.
  3. Select Incident > Manage Incidents > Incident List.
  4. Open the FILTERS pop-up and specify the details. Click SUBMIT.
  5. Open the Incident and manually change the Workgroup.  Move the Incident status from NEW to IN-PROGRESS.
  6. Open the Incident and manually change the Workgroup and move the status from IN-PROGRESS to PENDING.
  7. The Incident gets Auto-Resolved. The Elapsed Time By Workgroup is not calculated from IN-PROGRESS to PENDING and from PENDING to Auto-Resolve.

Now, the correct Elapsed Time By Workgroup is calculated from Pending to another status (i.e., the start of PENDING status to end of PENDING status) for auto-resolved Incidents.

56100

The incorrect Resolution deadline was found for some of the Incidents triggered from the SummitAI IT Operations module. This issue was occurring when a few of these Incidents were reopened, and Retro-active SLA was not working for the re-opened Incidents.

Required Configuration:

  1. Log into the Application.
  2. Select Admin > Advanced > Notifications > Alert. Configure it.
  3. Select Admin > Advanced > Notifications > Incident Template. Configure Log Incident for status.
  4. Select Incident > Configuration > SLA Configurations > Priority. Set Response SLA 5 mins Resolution SLA 7 mins.
  5. Select Admin > Advanced > Notifications > Incident Template. Configure it to manually resolve.

Bug Reproduction Steps:

  1. Select Incident > Manage Incidents > Incident List.
  2. On the FILTERS pop-up page, specify the details. Click SUBMIT.
  3. Select a new Incident on down Server. Move the incident to In-Progress and resolve it manually in 2 mins.
  4. Wait for Resolution SLA time (7 min) to expire.
  5. Run the Status all and Monitor all commands. The status of the Incident is changed to In-Progress.
  6. Change the Incident Status from In-Progress to Resolve. The incorrect Resolution deadline was observed for the Incident.

Now, the correct Resolution deadline is displayed for the reopened Incidents, which are logged from the SummitAI IT Operations module.

60415

When the user mouse-hovered on the Description field of the Change Record and the Description had a special character (~,!,#,$,%, etc.), the special character was not getting displayed instead some coded characters were displayed.

Bug Reproduction steps:

  1. Log into the Application and click on the Change icon.
  2. Click on Change Record List under User.
  3. Select a Change Record with special characters in the Description field.
  4. Mouse hover on the Description field of the Change Record

Now, if there are special characters in the Description field of a Change Record, on mouse hovering, the special characters are getting displayed correctly

60617

When a referred back SR was canceled, the Status of the SR was getting updated as New instead of Canceled.

Bug Reproduction Steps:

  1. Log into the Application.
  2. Select Request > User > My Service Requests.
  3. Select an SR referred back to you.
  4. Click the CANCEL REQUEST icon on the ACTIONS panel to cancel the SR. Click SUBMIT.
  5. The Status of the SR is displayed as New instead of Canceled.

Now, when a referred back SR is canceled, the Status of the SR is displayed as Canceled

59854

While logging an Incident using the SummitAI Mobile App, the complete list of Locations for the selected Tenant was not displayed. However, the complete list of Locations was displayed in the SummitAI web application.

Bug Reproduction Steps:

  1. Log into the SummitAI Mobile App.
  2. On the Home screen, tap the New Incident icon.
  3. Select a Tenant and view the list of Locations.
  4. Log into the SummitAI web application.
  5. Select User > New Incident.
  6. Select the same Tenant as selected in Step 3 and view the list of Locations. More Locations are found in the web application.

Now, the same set of Locations (based on configuration) is displayed to the End Users while logging Incidents using the SummitAI web application or SummitAI Mobile App. The following steps need to be performed:

  • Upgrade the Mobile App and respective Web services to the latest version.
  • Configure Location on the LOG INCIDENT PAGE in the SummitAI web application.
  1. Log into the Application.
  2. Select Incident > Configuration > Incident Masters > Log Incident Page
  3. On the LOG INCIDENT PAGE, select the Tenant and the Customer.
  4. Select the check boxes for the Location that is to be displayed on the NEW INCIDENT page. Click SUBMIT to save the configuration.

62266

For Palo Alto Network Devices, the Hostname was getting displayed under the Serial Number column on the JOB DETAILS page.


Bug Reproduction Steps:

  1. Log into the Application.
  2. Select Admin > Discovery & Monitoring > Discovery.
  3. Click on the Filters icon. Select Operations Management from the Tenant drop-down list. Provide values in all the fields and click SUBMIT.
  4. Click the Search icon in the Network discovery Job Name.
  5. From the Scan Details section, click the Search icon located under the View Scan Details column for the Palo Alto Network Device.
  6. The Hostname was displayed under the Serial Number column.

New MIB OIDs are added for Palo Alto Network Devices. When the Application discovers the Palo Alto Network Devices, it shows the Serial Number under the Serial Number column header.


60981

In the SummitAI Web Application, the separators were not displayed in-between the menu items on the left Navigation Pane. See the following screenshot:


Now, on the left Navigation Pane, the separators are displayed in-between the menu items on the left Navigation See the following screenshot:


59404

The Push Notifications were not getting triggered in the SummitAI web application. An issue was found related to data storage in the database tables.

Required Configuration:

Enable Pop-up on browser level on Google Chrome browser.

Bug Reproduction Steps:

  1. Check the push notifications on the Application Settings and configure the Push Notifications (Admin > Advanced > Notifications > Push Notification > Select Notification Type as Web > Fill in required details > Click Submit)
  2. Log an Incident and configure ETR (BY SLA and By Time)
  3. Run the Web Push notification and ETR job.

Now, Push Notifications are getting triggered in the SummitAI web application.

60365

On the ANALYST DASHBOARD page, on clicking the Red and Green sections of the pie chart under the Response SLA and Resolution SLA sections, the INCIDENT LIST page was displayed with no records.

Response SLA Performance

  • Response SLA: Upon clicking the Red section (not met records)
  • About to Miss: Upon clicking both Red and Green sections

Resolution SLA Performance

  • Resolution SLA: Upon clicking the Red section (not met records)
  • About to Miss: Upon clicking both Green and Red sections

Bug Reproduction Steps:

  1. Log into the SummitAI application.
  2. Select Dashboard > Analyst Dashboard.
  3. On the ANALYST DASHBOARD page, under the SLA Summary section, click the red and green sections on the Response SLA, About to Miss, Resolution SLA, and About to Miss pie charts. The INCIDENT LIST page is displayed with no records.

Now, on the ANALYST DASHBOARD page, on clicking the Red and green sections of the pie chart under the Response SLA and Resolution SLA sections, the INCIDENT LIST page is displayed with correct data.

60431

The Problem Record configurations were not getting displayed on the AUTO CREATION SETTINGS list page. This issue was occurring when the Incident Workgroup field was blank on the AUTO CREATION SETTINGS page.


Bug Reproduction steps:

  1. Log into the SummitAI Application.
  2. Click Problem > Configuration > Auto Creation Settings.
  3. On the AUTO CREATION SETTINGS page, click ADD NEW on the ACTIONS panel.
  4. Enter the required details. Do not select any value in the Incident Workgroup field. Click SUBMIT. 
  5. Click SHOW LIST on the AUTO CREATION SETTINGS page. The Problem Record configuration with no Incident Workgroup value is not displayed.

Now, the Problem Record configurations, with no Incident Workgroup field value, are getting displayed on the AUTO CREATION SETTINGS list page.

60434

If the SOP description was added or updated on the STANDARD OPERATING PROCEDURE (SOP) page with different formatting styles or text written in new lines, after submitting the changes, if the SOP template was opened for viewing or editing, all the text formatting was lost, and all the previously written text appeared in a single line (new line and formatting was getting lost).

Example: On the STANDARD OPERATING PROCEDURE (SOP) page, the description in SOP field was specified as per the following screenshot:

After submitting the changes, if the SOP was opened for viewing or editing, the SOP description was displayed as per the following screen shot:

Bug Reproduction Steps:

  1. Log into the SummitAI Application.
  2. Click Admin > Advanced > Documents > Standard Operating Procedures.
  3. Click Add New to create a new SOP template.
  4. Type in the Tenant and Template Name for the SOP.
  5. Type in the description in the SOP field with text written in multiple new lines and using different formatting (Bold, Italics, and Underline). Click SUBMIT.
  6. Select the Template that you created from the LIST section of the STANDARD OPERATING PROCEDURE (SOP) page. The formatting is lost, and the text written in multiple new lines are added up to a single line.

Now, the text format of the description content is retained as specified by the user on the STANDARD OPERATING PROCEDURE (SOP) page.


60056

When a Delegated User tried to log an Incident on behalf of the user (for whom this is the Delegated User), the Asset Allocation field was displaying the Asset of the Delegated User in place of the Assets of the User.

Example:

User: John

Delegated User: Sam

The Assets of Sam was getting displayed when Sam was logging an Incident for John.

Required Configuration:

  1. Log into the Application.
  2. Select Incident > Configurations > Log Incident Page.
  3. On the LOG INCIDENT PAGE, select a Tenant. Enable Asset Allocation and make it a mandatory field.

Bug Reproduction Steps:

  1. Select Incident > User > New Incident.
  2. On the DETAILS section, type in the caller name.
  3. The Assets of the Delegated User were displayed in place of the Assets of the User under Asset Allocation.

Now, the correct Assets are displayed when a Delegated User tries to log an Incident on behalf of the user.

When an Analyst tried to log a Service Request on behalf of the End User, the Asset search was displaying the Assets allocated to the Analyst in place of the Assets allocated to the End User under the Asset Allocation field on the NEW SERVICE REQUEST page.

Required Configuration:

  1. Log into the Application.
  2. Select Catalog > User > Create Service Catalog.
  3. On the FORM BUILDER page specify the details. Enables Asset Search checkbox under ADDITIONAL INFO tab.
  4. Make sure an Asset is allotted to the End User.

Bug Reproduction Step:

  1. Select Request > Manage Service Request > New Service Request for User.
  2. On the New Service Request For User section, select a Tenant and specify the details in Requested for and select a Catalog.
  3. On the NEW SERVICE REQUEST page, the Assets allocation filed shows Assets of the Analyst in place of Asset allocated to the End User.

Now, the correct Assets are displayed when an Analyst tries to raise a Service Request for an End User.

60418

When a user, not tagged with any Asset, tried to log a new Incident, the Application was not allowing the user to log the Incident. This issue was occurring when Asset Inventory was set as a mandatory field.

Required Configuration:

  1. Log into the Application.
  2. Select Incident > Configurations > Log Incident Page.
  3. On the LOG INCIDENT PAGE, select a Tenant. Enable Asset Allocation and make it Mandatory field.

Bug Reproduction Steps:

  1. Log into the Application.
  2. Select Incident > User > New Incident.
  3. Select a Tenant and specify the details.
  4. Click SUBMIT. No Incident is logged if no Asset is allocated to the user.

Now, a user, who is not tagged with any Asset, can also log Incidents even if Asset Inventory is a mandatory field on the Incident configuration page.


On the ASSET DETAILS page, the username was not getting populated in the Updated By field under the ASSET REGISTER tab for an action performed on the Fixed Assets.

Bug Reproduction Steps:

  1. Log into the Application.
  2. Select Asset > User > Manage Assets > Asset Inventory.
  3. On the ASSET INVENTORY page, select FIXED under the SELECT THE ASSET TYPE section.
  4. Open the FILTERS pop-up page and specify the details. Click SUBMIT.
  5. Select an Asset ID from the FIXED ASSET LIST.
  6. Perform any one of the following actions under the ACTIONS column.
    • UPDATE
    • ALLOCATE
    • BULK ALLOCATE
    • SEND TO REPAIR
    • STORE MOVEMENT
    • ASSET DEACTIVE
  7. Specify the required details and click SUBMIT.
  8. On the FIXED ASSET page, open the same Asset ID.
  9. On the ASSET DETAILS page, select the Asset Information menu.
  10. Check the Updated By field under ASSET REGISTER tab. It does not display the name of the user who last updated the Asset.

Now, the correct username is getting displayed in the Updated By field under the ASSET REGISTER tab for an action performed on the Fixed Assets.


62530

In the Change Workflow, the Migration Approval is the User-selectable Approval and is set to be defined at the Pre-Migration Approval 1 stage. However, the Application was displaying a message to specify the Migration Approval in the Approval 1 stage of the Workflow. This issue was occurring when the same user was configured for Approval 1 and Pre-Migration Approval 1.

Required configuration:

  1. Log into the Application.
  2. Select Admin > Basic > Infrastructure > Workflow.
  3. Open the FILTERS pop-up and specify the details. Click SUBMIT.
  4. On the WORKFLOW page, select Change Workflow under Workflow tab. Configure the Workflow. Click SUBMIT.

Bug Reproduction Steps:

  1. Select Change > User > New Change Records.
  2. On the NEW CHANGE RECORDS page specify the details. Click SUBMIT. A new Change Record is created.
  3. Select Change > User > Change Record List.
  4. On the CHANGE RECORD LIST page, open the same Change Record.
  5. On the WORKFLOW section, select Approval 1 and specify the details. Click SUBMIT.  A warning message is displayed, “Please select an Approver for: Migration Approval”.

Now, when the same user is configured for Approval 1 and the Pre-Migration Approval 1, a warning pop-up message, “Please select an Approver for: Migration Approval.” is displayed for the correct level Pre-Migration Approval 1 of the Workflow.

63155

The Operational Level Agreement was not getting displayed under the ADDITIONAL INFORMATION tab of Service Requests when the Workgroup was changed.

Required Configuration:

  1. Log into the Application.
  2. Select SLA > User > Operation Level > New Operation Level Specification.
  3. Configure the Operational Level Agreement specification.
  4. Login as Target and Source Workgroup Owners and approve the Operational Level Agreement Specification. The Operational Level Agreement is created automatically.
  5. Navigate to the Operational Level Agreement list page and publish the Operational Level Agreement.
  6. Create a Service Request.

Bug Reproduction Steps:

  1. Log in as an Analyst and update the Service Request. View the Operational Level Agreement details under the ADDITIONAL INFORMATION tab.
  2. Assign the Service Request to another Workgroup.  Check ADDITIONAL INFORMATION tab, the Operational Level Agreement details is not displayed under the ADDITIONAL INFORMATION tab.

Now, the Operational Level Agreement details are displayed even if the Workgroup information is changed for a Service Request.

63139

When users try to log into the SummitAI web application account using multiple devices, or two different browsers, or two different tabs (including incognito mode), a DUPLICATE LOGIN pop-up window with a message "Your last logged in session is still active was displayed. Also, a pop-up message, “Click CONTINUE to log out of the previous session and to continue with this device.” and CANCEL button was displayed.

  • If the user clicked CONTINUE, the previous session became inactive, and if any actions were performed on this inactive session, an error message was displayed.
  • If the user clicked CANCEL, the user was logged out of the current session and was able to continue to work in the previous session.

Bug Reproduction Steps:

  1. Log into the Application using the IE browser.
  2. Log into the Application using the same credentials on some other browser. A DUPLICATE LOGIN pop-up window with a message is displayed, "Your last logged in session is still active."

Now, the DUPLICATE LOGIN pop- message is not displayed when a user logs into the SummitAI web application using multiple browsers.

Known Issues

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

Issue

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.

While accessing the SummitAI application using Mozilla Firefox web browser, the pages, which have tree view are not loading. (#64315)

Workaround: To get the tree view, remove the following key from the web.config file:

<!--add name="Content-Security-Policy" value="script-src 'unsafe-inline' 'unsafe-eval' *.symphonysummit.com; style-src 'self' 'unsafe-inline'" /-->

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