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

Version 1 Current »

 | Previous Versions: << Sierra << Sierra HF01 << Sierra SP1 << Sierra SP1 HF01 << Sierra SP1 HF02 << Sierra SP1 HF03 << Denali << Denali HF01 << Denali HF02 << Denali HF03 << Denali SP1 << Denali SP1 HF01 << Tahoe << Tahoe SP1 << Tahoe SP3 HF01 << Tahoe SP3 HF01 (v1) << Tahoe SP3 HF02 << Tahoe SP3 HF03 << Tahoe SP3 HF04 << Tahoe SP3 HF05 << Tahoe SP3 HF06 << Tahoe SP3 HF07 << Tahoe SP3 HF08 << Tahoe SP3 HF09 << Tahoe SP3 HF10 << Tahoe SP3 HF11 << Tahoe SP3 HF12 << Tahoe SP3 HF13 << Tahoe SP3 HF14 << Tahoe SP3 HF15 << Tahoe SP3 HF16 << Tahoe SP1 HF17 << Tahoe SP3 HF18 << Tahoe SP3 HF19 << Tahoe SP3 HF20 << Tahoe SP3 HF21 << Tahoe SP3 HF22 << Tahoe SP3 HF23 << Tahoe SP3 HF24

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

  On this page:

Customer Fixed Issues | Known Issues 

Merged Releases

This release does not have any merged releases. 

Customer Fixed Issues 

This section describes the issues reported by the customers and their fixes in Tahoe SP3 HF25.

Service Management

Issue ID

Issue Description

Scenario

Resolution

149411/146572

In the Incident Feedback Report, after adding 1000 records, unable to fetch the details for all the fields under reports per page. From 1001 record, NA was displayed under all the fields.

Steps:

  1. Select Reports from the left navigation menu and navigate to Incident management scorecard.
  2. Navigate Reports > Incident Management.
  3. Under Reports tab, select Incident Feedback Report from the drop-down.
  4. The Incident Feedback Report preview pane is displayed. Click Filter icon, a pop-up window Filters is displayed.
  5. From the Filters page, select Tenant or Department and Workgroups from drop-down.
  6. Select From Date and To Date from which the reports are to be generated and displayed.
  7. Click Submit.  
  8. The details of all the fields, under records per page are displayed after 1000 records.

All the details for Incident Feedback Reports are generated and displayed under reports per page after 1000 records. From 1001 record, all the field details are displayed instead of NA. 

150235

While Assets are Assigned and Unassigned to Asset Group, after clicking Submit button, an error message ‘Oops, an error occurred’ was displayed.

Pre-requisite:

For the Patch Management, records must be present to assign and unassign Assets.

Steps:

To Assign Assets:

  1. Navigate to Asset > Configuration > Patch Management.
  2. Click Asset Group > Add New. Under Details tab, select Tenant and enter Group Name, click Next.
  3. Under Assets Assignment tab, click Assign Assets, a list of Asset list is displayed.
  4. Select the check box of Assets and click Assign to assign to Asset Group created.
  5. A confirmation message The Assets are added to the Asset Group (Asset name) appears.
  6. Click Submit.

 To Unassign Assets:

  1. Navigate to Asset > Configuration >Patch Management.
  2. Click Filter icon and specify filter criteria to view set of Asset Groups.
  3. Click Asset Group hyperlink.
  4. Navigate to Assets Assignment tab, a list of Asset list is displayed.
  5. Select the check box of Assets and click Unassign.
  6. Click Submit.

After Assigning and Unassigning Assets to Asset Group, the error message is not displayed when Submit button is clicked.


Work around: The SP usp_AM_MSPatches_Update_TargetGroup needs to be created in Job Scheduler every day recurring every 5 minutes.

149474

The Analyst's name was not appearing in the Assigned To field under the implemented tab of the closed CR.

Steps: 

  1.  Create a CR and complete the flow up to closed status.

  2. Go to the Analyst page and remove the Analyst assigned to the above-created CR.
  3. Check the CR to see whether the Analyst is displayed.

The Analyst’s name is available in the Assigned To field under the implemented tab of the closed CR after the resolution.

149475

There was an issue with the AD Import logs.

Steps: 

  1. Navigate to Admin > Basic > Infrastructure > Custom Scheduler.
  2. Schedule AD User Import job.

AD Import logs are working as expected after the resolution.            

150598

An error occurred when trying to move incident IDs from assigned and in-progress status to pending status.

Steps:

  1. Navigate to Reports > Incident Management > User.
  2. Click the Incident ID hyperlink.
  3. The Incident ID details are displayed.
  4. The tickets assigned are moved to Pending status when the incident is not resolved.

The incidents are moved from in progress status to pending status.

142173

In the Approve Service Request page, under the Approval Details tabular view, the Approver Details were not displayed in the Tabular view.

Pre-requisites:

Configure Tenant:

  1. Navigate to Admin > Tenant.
  2. In the Tenant configuration page, select the check box for the required fields from Configure Approver Details.

Create Catalog:  

  1. Navigate to Catalog > Create Service Catalog.
  2. Configure the workflow for the Catalog and enable the check box for UG1 and UG2.
  3. Raise New Service Request under the relevant Catalog created.

Approve Service Request:

  1. Navigate to Request > Approve Service Requests.
  2. Click SR ID hyperlink in Approve Service Requests page.
  3. Approval Details are displayed in Tabular View.

Under Approver Service Request page, the Approver Details are displayed in the Tabular view.

149323

Navigation arrows (left and right) are not functioning on the CMDB module.  

Steps:

  1. Login into the application.

  2. Navigate to CMDB > Configuration List Items.

  3. Open a CI record.

  4. Click on the Navigation arrows of the tab.

The navigation arrows are working on the CMDB module.

143449

Unable to make changes to CAB members on the Change Advisors board page. Error message “CAB member already exists”

Steps:

  1. Login into the application.

  2. Navigate to Change > Change Advisory Board.

  3. Select the member’s name to be updated.

  4. Click Submit.

If the CAB member is already present, no error message is displayed.

147692An error message occurred when changing the analyst of a service request that was in-progress status.

Prerequisite:

Enables ‘Notify Workgroup Owner(s) for SR Reassignment’ check box in Tenant configuration.

Steps:

  1.  Navigate to Request > User > Manage Service Requests >  Service Request List.

  2. Click SR ID hyperlink of in-progress SR from the list page.

  3. In the Assignments section of the Service Request Detail page, select a Workgroup and an Analyst from the list and click Submit.
The analyst of a service request in progress can be changed successfully without any errors.
148589An error occurred when the user attempted to import a template into the CR.

Prerequisites:

  •  Create a CR with a Template and assigned a user.

  • Save the template by clicking SAVE AS TEMPLATE from Action button.

  • Remove the selected user from the Workgroup from Analyst feature (Admin > Infrastructure > Analyst). 

Steps:


  1. Navigate to Change > New Change Record.

  2. Enter the required details and click IMPORT TEMPLATE from Action button.

  3. Search and select the previously created template.
You can import the templates without any errors.
150869An error message ‘Maximum length is 500’ occurred when a user tried to approve a Change Record through the Summit Mobile App.

Steps: 

  1. In Summit Mobile App Dashboard, navigate to Approve CR List > In CR detail page, click three dot > Select Authorize/Approve.

  2. Click the CR tile from the list.

  3. Swipe left on the CR tile and click green tick mark.
The user can approve a CR in Summit Mobile App without any issues.
147047In the Summit Mobile App, when the end user updated an incident with additional information, the status changed from "Pending" to "In-progress." Later, if more information was provided, the status reverted to "Pending," affecting the SLA calculation.

Prerequisites:

  • Enable the check box ‘Enable Pending Status Change on End User Update’ in Tenant Configuration.
  • Log an Incident in Summit Application and move the incident status to Pending.

 Steps: 

  1. In Summit Mobile App, update the Additional Info the created Incident.
    The incident status changes from Pending to In-progress.

  2. Update the incident with the additional information again.
The incident status does not change when the incident is updated multiple times.
143617

SLA was displaying incorrectly in DB while creating ticket in UI and through API.

Steps:

Following scenarios needs to be tested in New Incident Page and Email to incident creation.

  1. SLA Service Window screen to be configured with a Default value.

  2. If Workgroup SLA Window is not configured, then the system will consider the Default as SLA Service Window value.

  3. Workgroup SLA Window screen to be configured and Restrict SLA Windows to:” having Four values.
    Example: That contains default value which is configured in the SLA Service Window. In this case system considers the Default as a top priority and create the incident with default SLA values.

  4. Workgroup SLA Window configured and "Restrict SLA Windows to:” having Four values
    Example: That which does not contain the default value, and which is configured in the SLA Service Window. In this case system will find the highest bandwidth SLA (Maximum duration) and create an incident with that value.
SLA window is captured correctly.
142350

Users were facing an issue while fetching detailed report under incident management - open incident report.

Steps:

  1. Log in to Application.
  2. Navigate to Report > Incident Management > Open Incident Report.

Users can obtain detailed report under incident management - open incident report.

150458

Updating the User Communication via API changes the Incident Caller name if the user has 2 NT ID and same email ID.

Steps:

Refer to the API below to understand the changes to the API.

Sample Request 
{
    "ServiceName": "IM_LogOrUpdateIncident",
    "objCommonParameters": {
        "_ProxyDetails": {
            "AuthType": "APIKey",
            "APIKey": "F5MJWDOPQ8QSGMzNZfdkCytY9mLqrRVxrhQuCJfw4Gg=",
            "ProxyID": 0,
            "ReturnType": "JSON"
        },
        "incidentParamsJSON": {
            "IncidentContainerJsonObj": {
                "Updater": "Executive",
                "CI_ID": "",
                "CI_Key": "",
                "CI_Value": "",
                "Ticket": {
                    "IsFromWebService": true,
                    "Ticket_No": "49850",
                    "Priority_Name": "P One",
                    "Classification_Name": "Test",
                    "Sup_Function": "Info",
                    "Caller": "765",
                    "Status": "In-Progress",
                    "Urgency_Name": "IT Urgency 1",
                    "Assigned_WorkGroup_Name": "\"IT Additional Owner\"",
                    "Medium": "Application",
                    "Impact_Name": "IT Impact 1",
                    "Category_Name": "TestParentChild",
                    "SLA_Name": "8 to20",
                    "OpenCategory_Name": "TestParentChild",
                    "Source": "",
                    "Assigned_Engineer_Email": "abc.efg@symphonysummit.com",
                    "Description": "Logging a ticket as an Analyst",
                    "PageName": "TicketDetail"
                },
                "TicketInformation": {
                    "Information": "Logging a ticket as an Analyst test 1",
                    "InternalLog": "testing update",
                    "UserLog": ""
                },
                "CustomFields": []
            }
        },
        "RequestType": "RemoteCall"
    }
Sample Response 
{ 

    "Errors": "", 

    "Input": null, 

    "Message": "Ticket details are updated successfully", 

    "OrgID": 0, 

    "Output": null, 

    "OutputID": 0, 

    "OutputObject": null, 

    "TokenID": null, 

    "Priority": null, 

    "ResolutionDeadLine": null, 

    "Resolution_DeadLine": null, 

    "SLA": null, 

    "TicketID_Encrypted": "lw1QszEOjJ4fK5vY9GiiEQ%3d%3d", 

    "TicketID_Internal": 114571, 

    "TicketNo": 114572 

}

The incident caller name does not change while updating the User Communication via API.

149432It was determined that the SMTP password should accept 125 characters.

Steps:

  1. Log in to Summit application.
  2. Navigate to Admin > SMTP configuration.
  3. Create/Update SMTP password with 125 characters.
  4. Click Save.
SMTP password is accepting 125 characters.

150487 and 148607

Workorder with the same ID was generated. This was not a duplicate WO, only WO ID was duplicate.
Example: WO124568

Steps:

Manual WO creation for IM and SR: Analysts can create Work Orders for Incidents, Service Requests, and Change Records from the RELATIONSHIP tab.

IM Auto Workorder:
The Administrators can create Work Orders for Incidents on the WORK ORDER CREATION page for the Incident Management module.

  1. Select Incident > Configuration > Others > Auto Work Order Configuration.
  2. On the AUTO WORK ORDER CONFIGURATION page, click ADD NEW on the ACTIONS panel.
  3. Select the Tenant, type in the new Work Order details.
  4. Click SUBMIT.
  5. A new Work Order will create.

SR Auto Workorder:
The Administrators can configure Work Orders for Service Catalogs on the WORK ORDER CREATION FOR SERVICE CATALOG page for the Request Fulfilment module.

To configure Work Orders for Service Catalogs:

  1. Select Request > Configuration > Service Request Masters > Work Order - Catalog Mapping.
  2. Select Tenant from Filters.
  3. On the WORK ORDER - CATALOG MAPPING page, click ADD NEW on the ACTIONS
  4. Select Tenant, Service Catalog, and type in the new Work Order details.
  5. Click SUBMIT.
  6. A new Work Order for the Service Catalog will be configured.

SR Auto Workorder by Creation Date Job:
Admin needs to create a Custom Scheduler job using Auto Work Order Creation for
SR Job Option to create Work Order automatically based on the selected date.

It is Based on Work Order Creation Time in configure Work Orders for Service Catalogs.
Select the Workorder creation time Based on Date Field from the dropdown.

Note: Need to create multiple WO's During the same time.

Workorder with unique ID is generated.

148939

In the Incident Management module, when there was an Incident created through the UI with a certain Tenant Configuration, the mail to ticket notification was being triggered for In Progress status.

Prerequisite:

 

1.      In the TENANT Configuration page for Incident Management module, Notification for Selected Status Updates for Caller should be selected only for New Status.

 

Steps:


1.      Navigate to Incident > Configuration > Incident Masters > Category.

2.      Right click a Category > click Configure > Enable Location & Customer Wise Workgroup Routing.

3.      Select a Location > Select the Customer > Select a Workgroup > Select a Default Analyst > click ADD and then click SUBMIT.

4.      Create a New Incident using the Category which we have edited above.  

UI Issue is fixed and there is no mail triggered for a New Incident that is routed to In Progress status automatically.

Asset Management

Issue ID

Issue Description

Scenario

Resolution

139453 

Issue in CI Hardware Variance data update. 

 

CMDB Discovery Mapping was enabled between  

CMDB Server\DC Servers\Physical Servers and Asset Server Category. 

 

Upon performing field mapping in CMDB Discovery Mapping page, the variance was visible in CI, but updating hardware variance asset data into CI was not happening. 

 

 

 

 

Steps: 

  1. Navigate to CMDB > User > Manage Configuration Items > Configuration Item List. 

  2. Click the desired CI No hyperlink on the Configuration Item List page. 
    CI Details page is displayed. 
     
  3. Click Hardware Variance option from the right panel. 
    Hardware Variance Details pop-up is displayed. 
     
  4. Perform the required actions and click Save. 
    On the main details page, click SUBMIT. 
     

The CI Hardware Variance asset data updates made are successfully saved and displayed without any issues after the resolution. 

149668

At the time of Asset Allocation Accept/Reject through email not working. The user Accepting the asset over email, but it still shows as pending for acceptance.

Steps:


  1. Login to the application > Navigate to Asset > User > Manage Assets > Asset Inventory > Assign an accessory to a user.

  2. User gets an application generated mail with option to Accept/Reject the assigned accessory.

  3. Click on Accept button on the email.

  4. Login as User > Navigate to Asset > User > Manage Assets > My Asset List.

  5. Verify the status of the asset.

  6. Verify the Pending Acceptance status on My Asset List page.

The status of the Asset is Accepted/Rejected on the My Asset List page. The Pending Acceptance status is Accepted/Rejected on the My Asset List page. 

148485

Hostname field was configured as a unique field, however, while updating the Assets from Excel bulk update it was allowing to update duplicate names against the different assets. There was no validation message regarding duplicate Hostname in the PREVIOUS IMPORT DETAILS section.

Prerequisites:

 

1.      Hostname should be configured as a unique field in the Form Builder.

2.      The Asset Import Template sheet should contain a duplicate Hostnames.

 

Steps:

  1. Navigate to Asset > User > Manage Asset > Import > Import Asset.

  2. On the IMPORT ASSET page, under GENERAL tab, select the required options and upload the Asset Import Template with duplicate host names > Select Update in the Import Type field.

  3. Click SUBMIT. A table displaying the uploaded Asset Import Template sheet is displayed. Select the sheet to import the Assets.

  4. Navigate to Asset > User > Manage Assets > Import Asset.

  5. Select the Tenant and click PREVIOUS IMPORT DETAILS in the section > Select the UPDATE transaction ACTIONS and verify if the message is getting displayed.

The PREVIOUS IMPORT DETAILS section shows a validation message in the Remarks field when there is a duplicate field value while updating Assets.



Known Issues 

Issue

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

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

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

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

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

Note

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

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

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

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

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

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

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

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

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

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

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

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

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

(Bug# 84047)

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

(Bug# 85770)

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

When the RCA Approver refers back the PR, the RCA Approver Name and RCA Approve Date are not captured.

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

When the Reviewer rejects the PR, the Reviewer/Approver Name and Reviewer/Approver Date are not captured.

(Bug# 86000/ 85946)

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

When in the search text field, a relational operator i.e., <, >, <=, or >= is specified to search Assets.

When the user tries to search Non-Fixed Asset.

(Bug# 73532)

For the Custom Attribute (Drop-down), if any value is set as default on the Form Builder page (Admin > Basic > Infrastructure > FORM BUILDER > Select a Tenant > Select Module as Incident Management > Click Add on Actions panel> Select Display At as Additional Information or General Area or TFS Area > Click Next > Drag and drop the Drop-down Custom Attribute > Type in the Label for the Custom Attribute > Select Options (data source) as Manual > Type in the Drop-down Values and Make one value as default), then the default value is not automatically set for that Custom Attribute (Drop-down) across the Incident Management module

(Bug# 71703).

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

Note: 

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

Example:

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

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

If the RCA completed at 9:30 AM (RCA Actual Time), where RCA Deadline is 10:00 AM.

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

The Expected Resolution Deadline should be:

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

When the Maker-Checker configuration is enabled for the Allocate action and Maker-Checker approval matrix is configured with two levels of approval, on sending the Allocated Assets for Checker’s approval, the following issues are observed:

On the FIXED ASSET page (Asset > User > Manage Asset > Asset Inventory > Click the FIXED icon under the SELECT THE ASSET TYPE section > Click FILTERS on the ACTIONS panel > Select Status as Allocated and provide data in all the other fields > click SUBMIT), duplicate Assets are displayed after the Checker approves the Assets sent for approval.

The Assets do not move to the second level of approval after the Assets are approved by the first level of Approver.

Prerequisites

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

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

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:

Login to the Application as Checker.

Click Asset > User > Manage Asset > Approvals Maker-checker Approval > Click Filters on the ACTIONS panel.

On the Filter pop-up page, select the Tenant and specify the required details.

Select the Assets that you want to approve and click APPROVE icon on the ACTIONS The APPROVE pop-up page is displayed.

On the APPROVE pop-up page, select the Approval Status as Approved to approve the Asset and click

Click Asset > User > Manage Asset > Asset Inventory > Click FIXED under the SELECT THE ASSET TYPE section > Click Filters on the ACTIONS

On the Filters pop-up page, select the Tenant, Select the Status as Allocated and specify required details.

Click SUBMIT.

Validate the data.

(Bug# 72171)

The GetBulletinBoard Mobile API request is used to retrieve Bulletin Board information. The User ID and Tenant Code are passed as the Request Parameters. In the API Response, instead of displaying the Bulletin Board information for the specific User ID and Tenant, the Bulletin Board information for all the Tenants is displayed. (#73031)

Prerequisites:

Configure Bulletin Boards for multiple Tenants.

Bug Reproduction Steps:

Log into the Application as an Administrator.

Configure a Bulletin Board. For more information, see Configuring Bulletins.

Send a POST request for the GetBulletinBoard API. Pass Tenant Code, in the Instance parameter and User ID in the UserID parameter.

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:

Log into the Application as an Administrator.

Select Admin > Advanced > Automation > Orchestration.

On the WORKFLOW LIST page, click the NEW

On the WORKFLOW CONFIGURATION pop-up page, select Module as Service Request, and specify other details to configure the Orchestration Workflow.

Map the Target Host Type to From Previous Output value for the scripts of the Orchestration Workflow.

Log out and log into the Application as an Administrator or as an Analyst.

Select Request > Manage Service Requests > Service Request List.

On the SERVICE REQUEST LIST page, specify the Filters and open an SR.

On the SERVICE REQUEST DETAILS page, click the ORCHESTRATION tab.

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.

After successful execution of the Script (other than the first Script), click the Script hyperlink. Check the Target column details on the ACTION DETAILS pop-up page. Now, the Target ID is displaying in the Target column.

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

Bug Reproduction Steps:

Select Asset > User > Manage Asset > Import > Import Asset.

On the IMPORT ASSET page, under GENERAL tab, select the required options and upload the updated Asset Import Template. Click SUBMIT.

Select the sheet to import the Assets. Click the Mapping tab and select the required options if not already selected.  Click Next.

Click the Preview tab and select the store where you want to import the Assets from the Store list.

Click IMPORT ASSETS TO QUEUE on the ACTIONS panel.

Alternatively (Steps 1-5), select Asset > User > Manage Assets > Asset Inventory.  On the ASSET INVENTORY page, click FIXED.  On the ACTIONS panel, click ADD. On the ADD ASSET page, specify the required information and click SUBMIT.

Add two Assets with same Serial Number.

The Application allows to import or add two Asset with same Serial Number.

Select Asset > User > Manage Assets > Approvals > Maker Checker Approval . On the MAKER-CHECKER ASSET-APPROVAL page, click Filters  on the ACTIONS panel. Select the Tenant. Select the Transaction Type as Add to view the list of requests from the Maker.

The Assets with duplicate Serial Number are displayed. Click APPROVE on the ACTIONS panel. On the APPROVE pop-up page, select the  Approval Status as Approved.

(Bug#67236)

The previous Asset transaction details are not displayed under the Previous Transaction drop-down list on the PREVIOUS IMPORT DETAILS page (Asset > User > Manage Assets > Import > Import Asset > Specify all the details > Click SUBMIT), even though the Assets are approved by the Checker on the MAKER-CHECKER ASSET-APPROVAL page (Asset > User > Manage Assets > Approvals > Maker Checker Approval > Click Filters  on the ACTIONS panel > Specify the filter criteria to view the list of requests from the Maker > Select the Assets that you want to approve under the LIST section > Click APPROVE on the ACTIONS panel > Select the  Approval Status as Approved.) This issue is found when the Asset Maker Checker Configurations is enabled.

(Bug#67240)

On the ADMIN DETAILS page (Admin > Advanced > Password Management > Administrator > Click ADD NEW on the ACTIONS panel > Specify all the details > Click SUBMIT > Select the Domain Name on the LIST page), the Password field is not displaying the GUID or Encrypted ID of the password and the field is empty. This issue is found when the user is logging into the SummitAI application using Microsoft Internet Explorer browser.

On the Incident Management FORM BUILDER page (Admin > FORM BUILDER > Select a Tenant > Select Module as Incident Management > Click Add on Actions panel> Select Display At as Additional Information or General Area or TFS Area > Click Next), when a user configures single Parent and multiple Child using Common Master, the collective values of both Child 1 and Child 2 are displayed in Child 1 and Child 2 drop-down lists.

On the Service Request Management FORM BUILDER page (Admin > FORM BUILDER > Select a Tenant > Select Module as Service Request > Click Add on Actions panel> Select Display At as Additional Information or General Area or TFS Area > Click Next), when a user configures single Parent and Multiple Child using Common Master, the collective values of both Child 1 and Child 2 are displayed in Child 1 and Child 2 drop-down lists.

The configured Bulletin Board (Admin > Advanced > Notifications > Bulletin Board > Select the Tenant > Click ADD NEW to configure the Bulletin details > Click SUBMIT) is displayed on the END USER DASHBOARD page even if the user does not have access to the selected Tenant and Domain.

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

Broken image of the logo is displayed in the application when the logo image is deleted from the APPLICATION SETTINGS page (Admin > Basic > Infrastructure > Application Settings).

Workaround: The users need to re-login to the SummitAI application after deleting the logo.

On the AUTO-RESOLUTION SERVICE REQUEST CONFIGURATION and AUTO-RESOLUTION INCIDENT CONFIGURATION page (Admin > Basic > Infrastructure > Tenant > Select Domain > Select Tenant which is configured with Service Request/ Incident Management module > Click CONFIGURE DETAILS on the ACTIONS panel > Under the For End Users tab, select a reason form the Enable Reminder to Callers for Pending Reasons drop-down list > Enable Auto-Resolve Service Requests/ Auto-Resolve Incidents check box > Click Set Fields for Auto-Resolving Service Requests/ Set Fields for Auto-Resolving Incidents link), the users can set the auto-resolution criteria by specifying only white space (not numbers and alphabets) in the Response SLA Reason, Resolution SLA Reason, and Solution fields.

The following issues are observed in BI Custom Reports:

When a user downloads the report (in any format), the data is displayed with hyperlinks.

When a user places the mouse cursor on the count link, the tooltip is displayed as [Object Object].

In the exported report, report name is displayed with '+' instead of space.

The Change Record is not created when the CR Requester and Customer Approver are same. This issue occurs even though Do Not allow Customer Approval of CR check box is selected on the Change Management TENANT configuration page. This issue occurs only for the first time when the Tenant is configured.

Workaround: The Administrator needs to unselect and again select the Do Not allow Customer Approval of CR on the Change Management TENANT configuration page (Admin > Basic > Infrastructure > Tenant > Select the respective Tenant for which this issue is occurring > Click CONFIGURE DETAILS on the ACTIONS panel > Enable Do Not allow Customer Approval of CR check box and click SUBMIT > Clear Do Not allow Customer Approval of CR check box and then click SUBMIT, again).

The new SLA Value of an Incident is not displayed on the CHANGE HISTORY pop-up page (Incident > User > Manage Incidents > Incident List > Select the required Incident ID from the list > Click CHANGE HISTORY on the ACTIONS to view the change history of the selected Incident) when an incident is moved from New status to In-Progress using Notification Services.

The Pending Reason of an incident is still displayed on the CHANGE HISTORY pop-up page (Incident > User > Manage Incidents > Incident List > Select the required Incident ID from the list > Click CHANGE HISTORY on the ACTIONS to view the change history of the selected Incident), when an Orchestration Script fails and the respective Incident is moved back from Pending to In-Progress.

The notification e-mails related to escalation and jobs are triggered only in English language irrespective of the configured language on the NOTIFICATION TEMPLATE page for all the modules (Admin> Advanced> Notification> Notification Template> Select a Tenant > Click ADD NEW > Specify all the required fields > Click SUBMIT).

  • No labels