Customer Fixed Issues and Known Issues Tahoe SP3 HF18

Owned by Enterprise IT
May 08, 2024

 | 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

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

 

On this page: Customer Fixed Issues | Known Issues 

Merged Releases

Following are the merged releases in Tahoe SP3 HF18:

Customer Fixed Issues 

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

Service Management

136994 

In the Incident Description field, extra quotes (more than one) or characters were displayed. 

Prerequisite: 

 Schedule an Email Parser Job. 

Steps:  

  1. Send an email with single quote (eg I'll) to the configured mailbox to create an incident. 
     
  2. The Email Parser job is triggered as per the schedule.  
     
  3. Verify the newly created incident Description field. 

The Incident Description field displays the correct number of quotes and characters. 

131967 

An external tag was added to the Symptoms of Incident and Service Request when a user replied to the Notification Mail by including the [External] tag in the subject. 

Prerequisite: 

Schedule an Email Parser Job. 

Steps:

  1. Send an email to the configured mailbox to create an incident or a Service Request. 
     
  2. The Email Parser job is triggered as per the schedule.  
     
  3. Reply to the Notification Mail by including the [External] tag in the subject. 

The [External] tag does not display in the symptoms of an Incident and a Service Request when replying to the Notification Mail by including the [External] tag in the subject. 

137675 

Two emails were triggered for a workgroup when service requests were raised through the Mail to SR functionality. 

Prerequisites: 

  • Configure O365 API mailbox.
  • Configure Notification Parser and enable Create/Log Service Request Functionality.
  • Schedule an Email Parser Job. 

 Steps:  

  1. Send an email to the configured mailbox to create a SR. 
     
  2. The Email Parser job is triggered as per the schedule.  
     
  3. Verify the Email Notifications in Mail History. 

Email triggering for SRs created through Mail to SR is working as per the designed specifications. 

137038

While opening CMDB with Managed By dropdown other Tenant Workgroups were getting displayed.

Steps:

  1. Navigate to CMDB > New CI.

  2. Select the desired Tenant & Classification.

  3. Click Managed By dropdown and verify the Workgroups displayed.


The selected Tenant Workgroup dropdown values displays appropriately.

137095

Japanese value was not supported in the Bulk update functionality.

Steps: 

  1. Add Japanese characters in the Violation Reasons and Solutions Field while resolving incidents using Bulk update functionality.


Japanese value is supported in Bulk update functionality after the resolution.

137685

The keyword SERVICECATALOGDESC, and SERVICEREQUESTDESC was not getting updated with the value in SR assigned to the workgroup email.

Prerequisite:

  • Use the 2 keywords in the required email template.

Steps: 

  1.  Create a Catalog (Note: Catalog description should not be empty).

  2. Log an SR for the Catalog (Note: While logging the SR, fill in the remarks).

  3. Check the triggered mail.


The keyword SERVICECATALOGDESC, and SERVICEREQUESTDESC was getting updated with the value in SR assigned to the workgroup email after the resolution.

137493

The attachment function in the Diagnostic tab of the Problem Details page was not displaying anything when see/download was clicked.

Steps: 

  1. Navigate to Problem > Problem Record List.
  2. Edit any one problem record, add diagnostic details, and Submit.
  3. Go to the Diagnostic tab.

The attachments in the Diagnostic tab of the Problem Details page are displayed/downloaded after the resolution.

137019 

When exporting the Medium-Wise Incidents Report as a CSV file in the incident management module. Instead of incidents, service requests are displayed in the column header. 

Steps:  

  1.  Navigate to Reports > Incident Management.  

  2. Select the Medium Wise Incident report. 

  3. Export the report as CSV.    

The exported CSV file shows the column header as Incidents. The functionality is working as expected.  

137626 

When a Service request is cancelled by an analyst with cancellation remarks and images attached and the same SR is opened in end-user view, the attached images are not displaying.  

Prerequisites:  

  1. Enable Cancelled Status for SR in the Service Request details page.  

  2. A Service request should be created by an analyst. 

Steps:  

  1.  Login to the application as an Analyst. 

  2. Navigate to Request > Service Request List.   

  3. Open the created Service request from the SR list page.  

  4. Click Cancel. Enter the cancellation remarks.  

  5. Copy and paste any image in the cancellation remarks. Click Submit. 

  6. Login to the application as an End User.   

  7. Open the above cancelled Service request. 

The cancelled Service request, in the end-user view, shows the image copied in the cancellation remarks.  

132356 

The CI in the CMDB module can be edited to become operational even though it is status is retired. 

Steps:  

  1. Navigate to CMDB > Configuration Item List.   

  2. Select and open any CI.  

  3. Select Retired for both Life cycle status and Status dropdowns.

The status and the life cycle dropdowns are disabled if the status of the CI is retired.  

138299 

When searching for an SR ID, the global search does not show a header. 

Steps:  

  1. Navigate to Request > Service Request Details page.   

  2. Click the Global search.  

  3. Search for any SR ID.  

The header is displayed along with the SR ID search details in the global search. 

136371

When the SR was requested it went to the approver, when it was referred back to the requestor, the requested SR was not getting opened even though the requestor had access. However, the requestor was able to access the referred back SR.

Steps:

  1. Create a workflow with two-level approval.

  2. SR is requested, and it goes to approval.

  3. SR is referred back to the requestor.

  4. Login by requestor.

  5. Two notifications for one SR.

  6. Validate refer back request is showing inside the SR is referred back notifications.

Refer back request is only showing inside the SR is referred back notifications.

137829

while resolving incidents using the bulk update option, Japanese characters in the Column Solution were captured as '???' In both the Change History and the PDF. 

Steps:

  1. Navigate to Incident > User > Manage Incidents > Incident List.

  2. Select Incident IDs and click BULK UPDATE on the ACTION panel.

  3. Make the required changes and click Submit.

  4. Select Incident ID and click Export to PDF on the ACTION panel.

  5. Validate the column Solution in the Change History.


Japanese characters are displayed correctly for the Solution column in the Change History.

136747

Disabled users were not displayed in workgroups but still used analyst licenses.

Steps:


  1. Navigate to Admin > Basic > Users > Offboarding User Policy List.

  2. Add the policy.

  3. Enable the offboarding custom scheduler job.

  4. Disable analyst with dependency ticket.

  5. Run the offloading job.

  6. Reactivate the disabled analyst.

  7. Run the offloading and AD import jobs.

  8. Click on the Offboarding user icon in the top panel.

  9. Validate the user on the retrieved offloaded screen.

Only disabled users are displayed under the offboarding analyst list.

137394

When an incident was cancelled and converted to an SR, by two analysts at the same time(unintentionally), the Incident was cancelled but two SRs were created.

Steps:

  1. Log in to the application.

  2. Navigate to Incident > User > Manage Incidents > Incident list.

  3. Select Incident ID.

  4. From another browser, log in to the same application with other credentials.

  5. Navigate to the Incident list page and select the same Incident ID (as selected in step number 3).

  6. Click CONVERT TO REQUEST (perform the action at a time on both pages).

  7. Validate the RELATIONSHIP tab in the Incident.

When an incident is cancelled and converted to an SR, by two analysts at the same time(unintentionally), two SRs are not created.

136705

View other workgroup work orders option in application settings was not allowing analysts to see work order from other workgroups.

Pre-requisite:


  1. Analyst A should have Human Resources workgroup access.

  2. Analyst B should have Information Technology workgroup access.

  3. Analyst has created a workorder for Human Resources workgroup.

  4. In the application settings, View other workgroup workorders checkbox should be checked.

 

Steps:


  1. Navigate to Incident > User > Manage Incidents > Work Order List.

  2. Click Filters > Select the Workgroup as Information Technology and verify if the other workgroup workorder is visible.  

View other workgroup work orders option is working as desired.

136824

In the Incident Management module, while the analyst option incident is disabled, checklist values were displayed in the CHECKLIST tab.

Steps:

  1. Login to the Summit application as Analyst.

  2. Navigate to Incident > Configuration > Incident Masters > Checklist.
     
  3. Select the Tenant > click ADD NEW.

  4. Select the Status > Select the Workgroup and Category.

  5. In the Configure Task Status area select the Task Status.

  6. Click the edit icon beside Task Status and add Status Name in the CONFIGURE TASK STATUS Pop-up.

  7. Select any status and select the Show Inactive Click OK.

  8. Navigate to Incident > User > Manage Incidents > New Incident for User.

  9. Create an Incident with specific configured Category.

  10. Navigate to the Checklist tab and verify if you are able to see Inactive Checklist records. 

The disabled checklist values are not being displayed in the CHECKLIST tab while the analyst Incident option is disabled.

137537

On selecting the Work Order checkbox in the Global Search bar, users were getting “Violation of UNIQUE KEY constraint” error.

Steps:


  1. Search for a Work Order in the Global Search bar by selecting the Work Order.

  2. Click the Global Search icon. 

Users can search for Work Order in the Global Search bar.

138299 

Enhancement made in the external web service configuration: 

  1. A new workflow option is enabled. 

  2. An Additional Header(s) option is added.   

Prerequisites: 

  1. Navigate to Admin > Infrastructure > External Web Service Configuration.   

  2. Enable the “New Workflow” check box under the configuration tab. 

  3. The additional headers tab is enabled to add any customized headers. 
  4. Configure External Web Services with Source and Target Request.  

  5. Map the Source fields to Target fields.  

  6. Configure a job with frequency of 2 minutes. 

  7. Run the Job.  

Steps:  

  1. Connect to SQL Server. 

  2. Open the Database where External Webservice are configured. 

  3. Apply the SQL query in the database to display fetched records from source.  

  4. A Table is created with the name "ExternalwebserviceName_Transcation"

The records are fetched successfully. If the record is successful, it displays 1 and if the record has failed it displays 0.  The failed records will iterate for 5 times. 

134571

Issue 1:

For PIR reviewer the Closed status was not getting displayed.

Issue 2:

Actual PIR date and PI Review fields were not getting displayed as mandatory fields for PI review.


Prerequisites:

  1. Navigate to Admin > Tenant. Specify Auto Closing Days at Tenant level.
  2. Configure PIR reviewer in Change Module.
  3. Approve the CR.

Steps:

  1. Log in to Summit application as an Analyst and click on recently approved CR.
  2. Implement the CR and system displays the following validation message:
    “Only PIR reviewer can closer this CR.”
  3. Login as PIR reviewer and open the recently implemented CR.
  4. Click Status dropdown and verify the status.

Resolution 1:

For PIR reviewer the Closed status is getting displayed.

Resolution 2:

Actual PIR date and PI Review fields are getting displayed as mandatory fields for PI review.

Note:

Change Manager and configured PIR reviewer both can close CR when Auto Close is enabled.



136238

SMS notifications were not getting triggered for the ticket logged via email.

Prerequisites:

  1. Configure the SMS notification for In-Progress status.
  2. Enable Auto-Assignments of Incidents at Tenant level.
  3. Log an incident via e-mail.
  4. Verify SMS notifications.

SMS notifications are getting triggered for the ticket logged via email.

137507

The users were not able to see the record created on the resigned approver name in the Resigned approve list.


Prerequisites:

  1. Select individual as Mandatory Approver at Workflow level.
  2. Select any one of the added Approver from the user list as Inactive.

Steps:

  1. Navigate to Change > New change Record.
  2. Specify the mandatory fields and click Save.
  3. Authorize the first level of the Change Record.
  4. Click Approver and verify the added Approvers from workflow level.
  5. Try to approve the record.
  6. Navigate to Admin > Resigned Approver List. Select the resigned Approver and verify the record.

The users are able to see the record created on the resigned approver name in the Resigned approve list.


137507

Multiple CRs were getting created on the same day by Recurring CR job.

Prerequisites:

Configure the Recurring CR Job in Custom Scheduler. 

Multiple CRs are not created on the same day by Recurring CR job.

Asset Management

Issue ID

Issue Description

Scenario

Resolution

136480 

Currently, there were no checks to validate the Store Threshold Minimum to Maximum value for the Store Threshold value. 

Due to this, the user could define maximum value more than the minimum value. 

 

Steps: 

  1. Navigate to Asset > Configuration > Others > Store Threshold. 
     
  2. In the FILTERS pop-up, select the desired Tenant and Asset Type. 
    Click SUBMIT. 
     
  3. In the Store Threshold List page, select the Store Name hyperlink ( which is already configured) 
                   OR 
    Create a new configuration by clicking ADD NEW from Actions panel. 
     
  4. In the Details page, provide the required inputs for Asset Type, Store, Category, and Attributes field (for new configuration). 
     
  5. In the Asset Type- Fixed Asset grid segment, configure/check the values of Min.Value, Max.Value fields. 

The Store Threshold value is defined with a condition to have the maximum value to be more than 0.  

 
Due to this condition, the user can now define the minimum and maximum value successfully without any issues after the resolution. 

Platform

Issue ID

Issue Description

Scenario

Resolution

138003

Content added inside ‘<>’ characters in the symptom were not getting recorded in the Reporting table.

Steps:

  1. Navigate to Incident > Manage Incidents > New Incident for User.

  2. Create an incident with the symptom containing ‘<>’ characters.

  3. Navigate to Custom Scheduler. Check for "Load Denormalization IM Tables Data" in Running state.

  4. Navigate to Database. Check for IM_RPT_DN_TicketMaster.

The symptom is getting captured correctly without any error.

Known Issues 

This section describes the known issues detected by the Summit Dev and QA team in this Release.

Issue ID

Issue Description

Scenario

Workaround

101982

An approver encountered an error ‘Opps, Error Occurred’ message when opening an SR for approval. 

Prerequisites:

  • Create a Catalog with fields including an Attachment field.
  • Create an SR and attach an email with a symbol in the attached file name.
    For Example:

Steps:

  1. Log in to the SummitAI application as an Approver.

  2. Navigate to Request > Service Request List.

  3. Click the newly created SR ID hyperlink.

N/A

100922

An error ‘Opps! An error occurred’  or a Saved Successful message was displayed for all the modules, if the mandatory configuration fields were saved with a space (empty) value.

Scenario – I


1.       Navigate to Incident > SLA Configurations > Urgency.

2.       Select a Tenant.

3.       Click Add New from left panel.

4.       Press Space Key in Urgency Name field and click SUBMIT


Scenario – II


1.       Navigate to Problem Management > SLA Violation Reason.

2.       Select a Tenant.

3.       Click Add New from left panel.

4.       Select the Violation Type from the list.

5.       Press Space Key in SLA Violation Reason field and click SUBMIT.

N/A

105119

After submission, the text is getting converted to code for Question and Answer fields.

Prerequisites:


1.       Navigate to Knowledge > User > New Knowledge Record. The New Knowledge Record details page is displayed. Specify the mandatory fields. Make sure for Question field use keyboard Enter key. Click Submit.


2.       Navigate to Knowledge > User > Knowledge Record List. The Knowledge Record List page is displayed. Open any KB article with Status as Published. The Knowledge Record details page is displayed. Click COPY KNOWLEDGE RECORD link under Action panel. Check for the Answer field.

N/A

100352

When a Change Record (CR) is created with ‘special characters’ in status, it does not display any data in Change Record list page.

Prerequisites:


1.       Create a 'status' having special characters such as (*satus_test*).


2.       Create the CR.


Steps:


1.       Log in as approver.


2.       Navigate to Change > Change record list.


3.       Click on the Filters icon.


4.       Select the 'Tenant' field as ALL.


5.       Select the previously created 'status'.


6.       Click Apply.


7.       Verify the results, after applying the status filter with special characters.

N/A

100760

The ‘Category’ filters on the Change Record (CR) list page do not display any data results when you select ALL Tenant and Category.

Steps:

1.    Navigate to Change > User > Change Record list.

2.    Select the 'Tenant' field as ALL.

3.    Select the field as Category.

4.    Click Apply.

5.    Check the results displayed on the Change Record list page.

The Category filter works fine, when you select individual Tenant and Category.

100781When a ‘User Contact Number’ is used to filter records on the list page of IM/SR/PM, it does not fetch any data records.

Below is just an example from Incident Management list page. It also applies to SR and PM list pages too where User Contact Number is used. as filter:

Steps: Incident Management (IM)

1.    Navigate to Incident > Manage Incident > Incident List.

The Incident List page is displayed with list of incidents.

2.    From Filter options, select User Attributes
> User Contact Number. Select the operator as = and enter the Contact Number in the Value field of the respective User.

3.    Click Apply.

4.    Verify the results, after applying the User Contact Number filter.

N/A
100796The ‘Time Selection’ option is not displayed to an Analyst on the SR list page, when Equals (=) operator is selected for Time Filter.

Steps:

1.    Log in as an Analyst.

2.    Navigate to Request > Service Request List.

3.    Select the Time related Filter and choose Equals (=) operator.

4.    Click Calendar icon.

5. Check if you are getting the Time Selection option or not in Calendar popup.

N/A
100798The filter option ‘<=’ operator for Log Time Filter used by an Analyst on the SR list page, does not yield proper filter results.

Steps:

1.    Log in as an Analyst.

2.    Navigate to Request > Service Request List.

3.    Select the Log Time filter and choose operator (<=).

4.    Click Calendar icon.

5.    Select date and time for an already existing SR.

6.    Click Apply.

7.    Check if you are getting the filter results.

N/A
100808

The View names created by an Analyst for IM/SR/PM/CM

modules with long Japanese names are getting out of the container, unlike the English long names.

Steps:

1.    Log in to the Application as an Analyst.

2.    Navigate to Request > Service Request List and create a view with long Japanese name and apply view.

3.    Navigate to Incident > Incident List and create a view with long Japanese name and apply view.

4.    Navigate to Problem >
Problem Record List and create a view with long Japanese name and apply view.

5.    Navigate to Change > Change Record List and create a view with long Japanese name and apply view.

6.    Verify the view name in Japanese language text which goes out of the container.

N/A
100813The Assigned To drop-down does not display the User list.

Prerequisite:

The key

<add key="App:MultiLanguageEncodingEnabled" value="true" /> is set to True in webconfig file.


Steps:

1.  Navigate to Incident > User > Manage Incidents > Incident List. In the Incident List Click Incident ID hyperlink. The Incident ID details page is displayed.
        
2. Click RELATIONSHIP tab Click on the displayed Work Order ID. The Work Order ID page is displayed. Check Assigned To drop-down field under ASSIGNMENTS tab.


N/A

 



Download Release Notes | Previous Versions: << Sierra << Sierra HF01 << Sierra SP1 << Sierra SP1 HF01 << Sierra SP1 HF02 << Sierra SP1 HF03 << Denali << Denali HF01 << Denali HF02 << Denali HF03 << Denali SP1 << Denali SP1 HF01 << Tahoe

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

On this page: Customer Fixed Issues | Known Issues 

Hotfix Merges

The following Hotfix versions are merged with this release. Please refer to the respective Release Notes for details.

  • <Release Name> (Patch Release)

Known Issues 

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

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

  1. Enable Maker-checker approval for Asset Allocate transaction. (Admin> Basic > Infrastructure > Tenant > Click Filters on the ACTION panel and select the Domain and click SUMBIT > On the TENANT page under the LIST section, select the Tenant for which you want to enable Maker Checker > Click CONFIGURE DETAILS on the ACTIONS panel > Click Asset Management under the MODULES section > select the check box of Enable Maker-Checker > Select Actions for Maker-Checker to Approve as  Allocate > Select the End Time value and click SUBMIT).
  2. Configure No. of Approval level as 2 on the APPROVAL MATRIX page (Asset> Configuration > Others > Approval Matrix > On the ACTIONS panel, click ADD NEW > Specify the details > click SUBMIT).
  3. Send Assets for approval for Allocate action (Asset > User > Manage Asset > Asset Inventory > On the ASSET INVENTORY page, under the SELECT THE ASSET TYPE section, click FIXED > Select the same Tenant for which the Maker-checker is enabled >  Click the In-Store hyperlink of the required Asset Category > Select the check box corresponding to the Asset you want to allocate > On the ACTIONS panel, click ALLOCATE > Specify the mandatory details to allocate the Asset and click SUBMIT).

Bug Reproduction Steps:

  1. Login to the Application as Checker.
  2. Click Asset > User > Manage Asset > Approvals Maker-checker Approval > Click Filters on the ACTIONS panel.
  3. On the Filter pop-up page, select the Tenant and specify the required details.
  4. Select the Assets that you want to approve and click APPROVE icon on the ACTIONS The APPROVE pop-up page is displayed.
  5. On the APPROVE pop-up page, select the Approval Status as Approved to approve the Asset and click
  6. Click Asset > User > Manage Asset > Asset Inventory > Click FIXED under the SELECT THE ASSET TYPE section > Click Filters on the ACTIONS
  7. On the Filters pop-up page, select the Tenant, Select the Status as Allocated and specify required details.
  8. Click SUBMIT.
  9. Validate the data.
(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:

  1. Log into the Application as an Administrator.
  2. Configure a Bulletin Board. For more information, see Configuring Bulletins.
  3. Send a POST request for the GetBulletinBoard API. Pass Tenant Code, in the Instance parameter and User ID in the UserID parameter.
  4. Check API Response, instead of displaying the Bulletin Board information for the specific User ID and Tenant, the Bulletin Board information for all the Tenants is getting displayed.

On the ACTION DETAILS pop-up page, the Target ID is not showing in the Target column when Status of the Orchestration Workflow Script (other than the first Script) is In-Progress, and it is having Target Host Type mapped to From Previous Output value. However, the Target ID is displayed after the Script is executed successfully. (#73079)

Note: This issue is found in Incident Management, Work Order, and Service Request Management (SR) modules. Following bug reproduction steps are for the SR module:

Bug Reproduction Steps:

  1. Log into the Application as an Administrator.
  2. Select Admin > Advanced > Automation > Orchestration.
  3. On the WORKFLOW LIST page, click the NEW
  4. On the WORKFLOW CONFIGURATION pop-up page, select Module as Service Request, and specify other details to configure the Orchestration Workflow.
  5. Map the Target Host Type to From Previous Output value for the scripts of the Orchestration Workflow.
  6. Log out and log into the Application as an Administrator or as an Analyst.
  7. Select Request > Manage Service Requests > Service Request List.
  8. On the SERVICE REQUEST LIST page, specify the Filters and open an SR.
  9. On the SERVICE REQUEST DETAILS page, click the ORCHESTRATION tab.
  10. On the ORCHESTRATION tab, click the Script When the Script (other than the first Script) is in In Progress status, check the Target column details on the ACTION DETAILS pop-up page. The Target ID is not displaying in the Target column.
  11. After successful execution of the Script (other than the first Script), click the Script hyperlink. Check the Target column details on the ACTION DETAILS pop-up page. Now, the Target ID is displaying in the Target column.

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:

  1. Select Asset > User > Manage Asset > Import > Import Asset.
  2. On the IMPORT ASSET page, under GENERAL tab, select the required options and upload the updated Asset Import Template. Click SUBMIT.
  3. Select the sheet to import the Assets. Click the Mapping tab and select the required options if not already selected.  Click Next.
  4. Click the Preview tab and select the store where you want to import the Assets from the Store list.
  5. Click IMPORT ASSETS TO QUEUE on the ACTIONS panel.
  6. 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.
  7. Add two Assets with same Serial Number.
  8. The Application allows to import or add two Asset with same Serial Number.
  9. 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.
  10. 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).