#

Issue

Resolution

Few of the Analysts were getting access to the Modules that were not part of their configured License Edition.

Example:

The Analysts with Business Edition License were also able to access the Change Management or Problem Management or other modules, which are not part of Business Edition License.

Prerequisites:

Ensure that that the Business and the Enterprise Licenses are applied in the Application.

Bug Reproduction Steps:

1. Log into the Application as an Administrator.
2. Select Admin > Basic > Infrastructure > Analyst.
3. On the ANALYST page, select a Tenant and By Analyst under the Configure drop-down list.
4. Select Business in the Edition drop-down field and specify the Attributes. Type in and select an Analyst in the Select the Analyst field.
5. Configure complete access Role Template to the Analyst. For more information see, Configuring Role Templates.
6. Log into Application as the Analyst with Business Edition License access.
7. Check for the module access. The Analyst can access modules, such as Problem and Change, which are not part of configured Business Edition.

Now, the Analysts can access only those Modules, which are included in the License type.

64369

An Oops error message was getting displayed when a CI record was opened on the CONFIGURATION ITEM LIST page.

Bug Reproduction Steps:

1. Log into the Application.
2. Select CMDB > User > Configuration Item List.
3. On the CONFIGURATION ITEM LIST page, open a CI record. An error message, “Oops! An error occurred.”, is displayed. 

Now, a CI record can be opened from the CONFIGURATION ITEM LIST page without any error.

64370

The Global Search was not displaying any search result while searching for any text value. The Global Search was able to display search results only for integer values. This issue was found after upgrading SummitAI version to ALPS SP1 HF02.

Bug Reproduction Steps:

1. Log into the Application.
2. On the Application, click the Global Search icon  , a search box is displayed.
3. Type in the text in the search box that you want to search and click the  icon. No search results are displayed.

Now, Global Search is displaying search results while searching for text value.

63153

63522

The Analysts were unable to update the Status of Service Requests to Resolved using Bulk Update. A warning message, "None of the SRs are updated.", was displayed.

Bug Reproduction Steps:

1. Log into the Application.
2. Select Request > User > Manage Service Requests > Service Request List.
3. On the FILTERS pop-up page, select a Tenant and specify details. Click SUBMIT.
4. On the SERVICE REQUEST LIST page, select Service Requests and click BULK UPDATE on the ACTIONS panel.
5. On the BULK UPDATE pop-up page, select Resolved under the Status drop-down and specify other details. Click SUBMIT. A warning message, "None of the SRs are updated.", is displayed.

Now, the Analysts can update the Status of Service Requests to Resolved using Bulk Update without any error.

63139

If the user logged into the Application after repetitively logging in and logging out, an error message, “You have logged in from other device.”, or the Duplicate Login pop-up page was displayed. This issue was occurring even after logging off from the Application and closing the browser window.

Bug Reproduction Steps:

1. Log into the Application.
2. Log out from the Application.
3. Do the Steps 1 and 2 multiple times. Close the browser window.
4. Log into the Application again. The error message, “You have logged in from other device.”, or the Duplicate Login pop-up page is displayed.

Now, no Duplicate Login or error message is displayed when the user tries to log into the Application after repetitive log in/log out actions.

Note: The corrections are made for SSO authentication only.

56926

The Data and Graphs were spanning across  multiple pages while generating a PDF of the BI  Dashboard. This Issue was occurring because of incorrect formatting.

Bug Reproduction Steps:

1. Log into the Application.
2. Select Report > Incident Management > New Report  icon.
3. On the REPORTS pop-up page, specify the details under desired tab. Click PREVIEW.
4. On the PREVIEW tab click Save.
5. Select Report > Incident Management > New Dashboard  icon.
6. Click the   icon on the blank dashboard page and select the Category from the Category drop-down list.
7. Select the reports and its format to add to the dashboard.
8. To save the dashboard, click the Save dashboard or Save dashboard as icon on the menu options. Type in the Dashboard name as BI Izenda Dashboard in the Name field and select the dashboard category from the Category drop-down list.
9. Select Report > Incident Management and select BI Izenda Dashboard under REPORTS drop-down.
10. On the BI Izenda Dashboard, click on print  icon and select Print dashboard PDF. Verify the BI Izenda Dashboard PDF details. The Data and Graphs span into multiple pages. 

To resolve BI Dashboard report formatting issue, include the following key in the Web.config file:
<add key="Izenda:PdfPrintMode" value="evopdf" />

63134

The Pending Incident Feedback link on the End User Dashboard page was navigating to the MY INCIDENTS page but none of the Incidents were listed on the page. This link should open up the MY INCIDENTS page displaying the list of Incidents that are pending for Feedback.

Bug Reproduction Steps:

1. Log into the Application.
2. Click the Pending Incident Feedback link on the End User Dashboard. The MY INCIDENTS page is displayed with no records.

Now, on clicking the Pending Incident Feedback link on the End User Dashboard page, MY INCIDENTS page opens up displaying the list of Incidents pending for Feedback.

64987

The Incident Symptom was picking up the Primary Symptom instead of the Secondary Symptom that was defined while raising the Incident from the End User Dashboard page.

Prerequisites:

1. Log into the Application as an Administrator.
2. Select Incident > Configurations > Others > Rule.
3. On the RULE page, select a Tenant and click ADD NEW on the ACTIONS panel.
4. On the RULE page, specify details on the GENERAL, COMMUNICATION, VENDOR INFORMATION, and ADDITIONAL INFORMATION with a Primary Symptom. Click SUBMIT.
5. Select Incident > Configurations > Others > Rule.
6. On the FILTERS pop-up page specify the same Rule name that was created using steps 2-44. Click SUBMIT.
7. On the RULE LIST page, select the Rule and open TROUBLESHOOTING tab.
8. On the TROUBLESHOOTING tab, specify the Secondary symptom and other details. Click SUBMIT.

Bug Reproduction Steps:

1. Log into Application as an End User with Dynamic End User Dashboard enabled.
2. Select Dashboard > End User Dashboard. Type in the configured Secondary Symptom in the place holder.
3. Click on the Secondary Symptom. It is navigating to the NEW INCIDENT page
4. Check the Symptom. The Primary Symptom is appearing instead of Secondary Symptom.

Now, the Incident Symptom is picking up the correct Primary or Secondary symptom that is entered while raising the Incident from the End User Dashboard.

63221

There was a spelling mistake in the e New Value column of the Checklist tab, rue instead of True. This error was found on the Incident SUMMARY pop-up page of the Daily Incident Report.

Prerequisites:

1. Log into the Application.
2. Select Incident > Configuration > Incident Masters > Checklist.
3. On the CHECKLIST page, select a Tenant, and specify the Workgroup, Category and other details under the DETAILS section . Click SUBMIT.
4. On the USER DASHBOARD page (Dashboard menu), click NEW INCIDENT under INCIDENT. Alternatively, select Incident > User > New Incident.
5. On the NEW INCIDENT page, select the same Tenant, Workgroup, and Category that was configured on the CHECKLIST page and type in the required details for the new Incident under the DETAILS section. Click SUBMIT.

Bug Reproduction Steps:

1. Log into the Application.
2. Select Reports > Incident Management.
3. Select Daily Incident Report under the REPORTS drop-down. On the Filters pop-up page specify the details. Click SUBMIT.
4. On the DAILY INCIDENT REPORT page open the same Incident that was created in the Prerequisite steps.
5. On the Incident SUMMARY pop-up page, select the Checklist tab. The New Value column of the Checklist tab shows rue in place of True.

Note: The issue occurs for all statuses of the Incident when the Checklist task is met.

The spelling mistake in the New Value column of the Checklist tab is corrected.

63411

The Category field was blank by default on the OPERATIONAL LEVEL SPECIFICATION page. It was populating, ALL, value only after an Incident Management criterion was added.

Bug Reproduction Steps:

1. Log into the Application.
2. Select SLA > User > Operation Level > New Operational Level Specification.
3. On the NEW OPERATIONAL LEVEL SPECIFICATION page, select the DEADLINE tab under the DETAILS section.
4. On the Incident Management section, the Category field is blank by default. Specify the details and click ADD.
5. Verify the Incident management section. The Category field is displaying a value, All.

Now, by default ALL is displayed in the Category field on the OPERATIONAL LEVEL SPECIFICATION page for the Incident Management section. Also, a  icon is added in the field to revert back to ALL after a specific Category is selected.

63434

No data was displaying in the Location and Manager fields on the USER details page. Also, the user was not able to search Location and Manager while modifying the USER page details. This issue was occurring for both single and multi-domain users.

Bug Reproduction Steps:

1. Log into the Application as a Single Domain user.
2. Select Admin > Basic > Users > User list.
3. On the FILTERS pop-up page, specify the details. Click SUBMIT.
4. On the USER LIST page open, a User detail.
5. On the USER page, type in the Location name. No results are displayed.
6. Under the GENERAL tab of the USER page, type in the manager name in the Manager field, No results are displayed.
7. Repeat the steps 1 to 6 for Multi-domain user.

Now, the Location and Manager data is displayed on the USER page. Also, the user is able to search Location and Manager while modifying the USER page details.

63792

Some of the users who were not having access to a Catalog were able to raise the SRs for such Catalogs using the New Service Request page Application URL shared by a user who was having access to that particular Catalog.

Prerequisites:

1. Make sure there are two users, one who belongs to User level & other does not belong to User level in the SummitAI application.
2. Create, Approve, and Publish a Service Catalog to any applicable user level’. For more information Creating, Approving, and Publishing a Service Catalog, see Creating Service Catalog and Approving and Publishing Service Catalog.

Bug Reproduction Steps:

1. Log into the Application.
   Note: Make sure the that the user is part of User Level for which the Catalog is Published in the Prerequisites.
2. Select Request > New Service Request.
3. On the New Service Request page, select the Department and the same Catalog that was published in the Prerequisites.
4. Now, copy the application URL and share it with a user who does not belong to the same User level for which the above Catalog is published.
5. Log into Application as a user who does not belong to the User Level for which the above Catalog is published.
6. Copy the URL and browse the URL. The user who does not have access to the Service Catalog can log Service Requests using the shared URL.

Now, when a user not having access to a Service Catalog tries to log a Service Request for that Service Catalog using the Application URL shared by another user who is having access to the Service Catalog, a validation message is displayed and is not allowed to raise SRs for the Service Catalog ,"You do not have access to the Service Catalog, (CATALOGNAME)."

63821

The Summary tab on the PENDING SERVICE REQUEST REPORT page was not showing the correct count. This issue was occurring when the Role Template for the user was configured as Customer in the Show Only User's field under the REPORT SCREENS section.

Prerequisites:

1. Log into the Application.
2. Select Admin > Basic > Users > Role Template.
3. On the FILTERS pop-up page of ROLE TEMPLATE page, select a Domain and click SUBMIT.
4. Configure a new Role Template, refer to Configuring Role Templates.
   Alternatively, open an existing Role Template on the ROLE TEMPLATE LIST page.
5. Click OTHER CONFIGURATION on the ACTIONS panel of the ROLE TEMPLATE – MENU CONFIGURATION page.
6. On the ROLE TEMPLATE - OTHER CONFIGURATION page, select the Customer check box in the Show Only User's field under the REPORT SCREENS section and specify other details. Click SUBMIT.
7. Select Admin > Basic > Users > User List.
8. On the USER LIST page, click ADD NEW on the ACTIONS panel.
9. On the NEW USER page, specify GENERAL tab details.
10. On the NEW USER page, select ACCESS tab and enable the same Role Template that was created in steps 2-66. Click SUBMIT.

Bug Reproduction Steps:

1. Log into the Application as the same user that is configured in Prerequisites.
2. Select Reports > Service Request.
3. On the REPORTS drop-down, select Pending Service Request Report.
4. On the FILTERS pop-up page specify details. Click SUBMIT.
5. On the PENDING SERVICE REQUEST REPORT page, verify the Summary tab details. A count mismatch is found.

Now, the Summary tab on the PENDING SERVICE REQUEST REPORT page is showing the correct count.

64003

The Analyst details were not getting saved on the ANALYST page when the Analyst details were imported for a Workgroup for the first time. This issue was occurring for Analysts who were not part of any of the Workgroups before.

Prerequisites:

 Adding New User

1. Log into the Application.
2. Select Admin > Basic > Users > User List.
3. On the ACTIONS panel of the USER LIST PAGE, click ADD NEW.
4. On the NEW USER page, specify the details. Click SUBMIT.

Importing Analyst

1. Select Admin > Basic > Infrastructure > Workgroup.
2. On the WORKGROUP page, select a Tenant and click IMPORT MASTER on the ACTIONS panel.
3. On the ACTIONS panel, click DOWNLOAD MASTER IMPORT TEMPLATE. Fill in the Analyst details and save the Master Import Template.
4. On the MASTER IMPORT page, select Analyst in the Master Type drop-down list under the GENERAL tab. Specify other details and upload the Master Import Template file in the Source field. Under the GENERAL and MAPPING tab, specify other fields. Check PREVIEW.
5. Under the GENERAL Tab of the MASTER IMPORT page, click SUBMIT.

Bug Reproduction Steps:

1. Log into the Application.
2. Select Admin > Basic > Infrastructure > Analyst.
3. On the ANALYST page, select a Tenant and select By Workgroup in the Configure drop-down list under DETAILS section.
4. Under the CONFIGURE BY WORKGROUP section, select the same Workgroup that was selected while importing the Analyst in Prerequisites under the Workgroup drop-down list.
5. Verify the Analyst details. Details of Analyst that was added in the Prerequisites are not saved on the ANALYST page.

Now, the Analyst details are saved on the ANALYST page when the Analyst details are imported for a Workgroup (even for the first time).

64448

An error message was displayed when an Analyst was trying to open an Incident from the INCIDENT LIST page..

Bug Reproduction Steps:

1. Log into the Application as an Analyst.
2. Select Incident > User > Manage Incidents > Incident List. An error message, “Oops an Error Occurred.”, is displayed.

Now, the Analysts can open and view Incidents from the INCIDENT LIST page without any error.

62926

The newly added Asset Category fields were not displaying for the older Assets in the Asset Allocation e-mail notification to the End Users if the newly added Category field was empty.

Bug Reproduction Step:

Add New Asset Category Fields

1. Log into the Application.
2. Select Admin > Basic > Infrastructure > Form Builder.
3. On the FORM BUILDER page, select Asset Management from the Module list. Click ADD NEW on the ACTIONS panel.
4. Under the FORM DETAILS, and FORM BUILDER tab, specify the details. Click NEXT. Under the PREVIEW tab, view the Fields configured for the Asset Category. Click SAVE.

Add Assets

1. Select Asset > User > Manage Assets > Asset Inventory.
2. On the ASSET INVENTORY page, Click FIXED under the SELECT THE ASSET TYPE section and click ADD on the ACTIONS panel.
3. On the ADD ASSET page, add a Fixed Asset (Asset ID: 01).
4. Add one more Category Field. Add another Fixed Asset (Asset ID: 02).
5. Allocate both the Assets (Asset ID:1 and Asset ID:2) to an End User. The end-user receives Asset Allocation e-mails for both the Assets (Asset ID:1 and Asset ID:2) The Asset Allocation e-mail for the older Asset (Asset ID:01) does not display the Asset Category field that was added recently if the field was empty.

Now, all the Asset Category fields are displaying in the Asset Allocation e-mail notifications sent to the End User for both older and new Assets.

The Incident IDs that were getting generated while Monitoring for down Servers, Devices, or Links, were not in the continuous Incident ID series. This issue was occurring when the session was timed out before all the Incident IDs were generated for the down Servers, Devices, or Links.

Example: While Monitoring the Servers, if 20 Servers were down and only 10 Incidents were created as Incident ID 101, 102, and so on till Incident ID 110, and the session timed out. When the session was restored, all the data was rolled back and none of the Incidents were created. During the next Monitoring, when the next Incident ID was created for a down device, it was starting from Incident ID 111.

Now, Incident IDs that are generated for down Servers, Devices, or Links are not rolled back when session times out. After the session is restored, the Application creates Incident IDs in continuation with the last Incident ID logged. As per the example, all the Incidents are logged for down devices from Incident ID 101 - 120 even if session times out in between while generating the Incident IDs. Also, during the next Monitoring, when the next Incident ID is logged, it starts from Incident ID 121.

65343

64758

An error message, 'Cannot upload the attachment file', and , 'Attachments failed to upload', was displayed when an Incident was raised from the SummitAI Mobile App using SSO login. The Incident was getting created as expected but the attachments was not getting uploaded or downloaded.

Now, the attachments that are attached while raising the Incidents using the SummitAI Mobile App using SSO login can be uploaded and downloaded without any error message.