Customer Fixed Issues and Known Issues Tahoe SP3 HF09

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

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 HF09:

Customer Fixed Issues 

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

Service Management

Issue ID

Issue Description

Scenario

Resolution

113457While creating a new SOP and the Department list were not loading in SOP list page and detail page. 

Prerequisite:

The Application Should not have AVM License.

Steps:

  1. Navigate to Admin > Advanced > SOP.  
  2. On the Actions Menu, Click Filters > Select the Department.  
  3. Click ADD NEW. Verify if the Department list is loading.   
The Department list is loading in SOP list page and detail page.  
121425

Service Request Approval routing was not happening properly via the SymphonyAI Mobile App .

Note

This issue is also addressed in the SymphonyAI Summit Old Mobile App.

Prerequisites:  

  1. Create a Service Request Catalog and enable ‘Enable Location’, 'Select User location' and add a few locations along with Workgroup in LogSR in User Location.
  2. Add a Workflow having approval level as Workgroup Owner.  
  3. Click SUBMIT and publish the Catalog. 

Steps:

  1. Log in to the SummitAI Mobile Application. 
  2. Click Log Service Request icon.  
  3. Select the configured Catalog.  
  4. Select the location & verify the approver.  
Service Request Approval routing is working as desired.  
116499

The Ticket List pop-up was displaying without records.

Prerequisites:

  1. Navigate to Reports > Select the Module as Service Request. Select the reports as SR SLA by Workgroup and SR SLA by Analyst
  2. Navigate to the Response tab section and click any Total SR Count hyperlink. The Ticket List pop-up is displayed. 
The Ticket List pop-up is displaying with records.

119057

The Release Record ID was not getting displayed after linking the Release Record with the Change Record. Instead, it was displaying the Release Record Type.   

Prerequisites:

  1. Create a Release Record for the required Tenant.
  2. Create a Change Record for the required Tenant.

Steps:

  1. Navigate to Change > User > Change Record List. The Change Record List page is displayed. Click on the required CR ID hyperlink. The CR ID details page is displayed.

  2. Navigate to the Relationship Select Release from the Link drop-down box.

  3. Filter the release records with required ID. Enable the checkbox for the required release record.

  4. Click on link. The Release record will be linked to the CR. Observe the title of linked release record.
The Release Record ID is getting displayed after linking the Release Record with the Change Record. 
118466Cancel and Submit buttons were getting disabled in CRs and Change Manager was not able to edit the approved CR.

Prerequisite:

Select All for Allow Change manager to Update CR for Specific Status in the Tenant Configuration.

Steps:


  1. Create a new user U1 and provide analyst access to WG1.

  2. Configure the same user as Change Manager for other few workgroups (WG2, WG3, WG4).

  3. Log in as U1 and open any CR with Approved Status and pending for Implementation stage.

  4. Open a CR with Approved status and pending for next approval.



Cancel and Submit button appears in CRs and Change Manager edits the approved CR.






118704

Users were experiencing Error loading OLA details on the newly added OLA page.

On the OLA page, SERVICE REQUEST details were not listed for the DEADLINE tab. However, it was functional.

Could not edit the mapped one on SR as it was not listed.

Prerequisite:

  1. Configure Service Level Approver from SLA > Configuration > Service Level Approver.

Steps:

  1. Navigate to SLA > User > Operation Level > New Operational Level Specification.

  2. Fill up all the required details.

  3. In the DEADLINE tab enter IM, SR, and PM SLA Time.

  4. To add the records, click ADD.

  5. To submit the OLS, click SUBMIT.
OLA page is loading without error.
116475The number of Tasks on the RELATIONSHIP tab of the CR ID was not matching with the list in the custom Report (RawData) for the CR ID. Task Numbers were incorrect.

Steps:

  1. Navigate to Change > Change Record List.

  2. Click RELATIONSHIP tab.

  3. Click Tasks.

  4. Validate the number of Tasks linked to a CR on the Custom Report.
Issue fixed by not allowing Task to be delinked.
118611CR status was different in Summit UI and BI reports.

Prerequisites:

  1. CR auto closer job should be set to running.

  2. At the Tenant level Change Request closing mode should be set to Auto.

  3. CR should be in Implemented status.

  4. Load denormalization CM job should be running.

Steps:

  1. Post CR Auto closer job completion, verify the CR status.

  2. CR will be auto closed.

  3. Check the CR status in the Change Request Master table and post-load denormalization CM job completion.
The CR status in Summit UI and BI report is the same after resolution. 
118787The Delegation Status was not getting updated. 

Prerequisite:

  1. Give Authorizer access to the reporting manager in the first level of workflow.

Steps:

  1. Navigate to Admin > Basic > User > User List.

  2. Fill the Manager field with any other account in the general details and submit.

  3. Create a CR by filling in all mandatory fields.

  4. Log in to the application by the given Manager account.

  5. Navigate to Change > User > Change Record List and select the created CR.

  6. Delegate another account than Manager and CR Initiator as Approver for Change Management.

  7. Log in to the application as an initiator account.
      Authorize the created CR.		The Delegation Status gets updated after the resolution. 
118597Registration Time was appearing in IST instead of JST on the Release Record List page. 

Steps:

  1. Log in to the application with the JST time zone.

  2. Navigate to Release > User > Release Record List.

  3. Open any release record and verify Registration Time on the List page and Detail page. 
Registration time is appearing in JST after the resolution. 
119457Analysts could link and delink the records post-release closure, but the same was not working in other modules. 

Steps:

  1. Navigate to Release > User > Release Record List.

  2. Open the Release Detail page which is in closed status.
Linking and delinking of records, post-release closure is solved after the resolution. 
118615When the Schedule Status was selected as ‘Failed’, the page was getting loaded without submitting and displayed two messages. 

Steps:

  1. Navigate to Release > User > Release Record List.

  2. Open any Release record.

  3. Click Schedule and select Schedule Status as Failed.  
The messages getting displayed while selecting the Schedule status as ‘Failed’ is fixed after the resolution. 
122369Support email ID functionality for PM Module was not working as expected.

Steps:

  1. Configure SMTP for General level and work group level configuration.

  2. Configure email for User records from the workgroup level to pick the SMTP.

  3. Create a PM by selecting the workgroup which we configured.


Email functionality for PM Module works properly after the resolution.
118238/ 116566  Emails are getting stuck in AM_AssetAllocation_Queue post sending email notifications to End Users.  

Steps: 

  1. Log in to Summit Application. 

  2. Navigate to Asset > Manage Asset > Asset Inventory > Fixed Asset > Instore. 

  3. Allocate, reallocate, and update any allocated asset.  

  4. Run the job related to Asset Allocation Email Alert.   
Emails are no longer stuck in AM_AssetAllocation_Queue and multiple email notifications are not triggered to End Users. The functionality is working as expected.  
119116 In Scheduler tab under Release records, unable to modify the Scheduler details without re-entering the Schedule Owner name.  

Steps: 

  1. Navigate to Release > Release Record List.  

  2. Select the Release which needs to be edited.  

  3. Create 2 scheduler details in the Schedule tab. Click Submit. 

  4. Edit the created Scheduler details such as change the scheduler status and click Submit.  
Without re-entering the Schedule owner name, the Scheduler details are editable. The functionality is working as expected.  
116625The list of Departments or Tenants dropdown is not listed in the SOP Configuration Page.  

Prerequisites:  

Admin should not have ITOM license.   

Steps:  

  1. Log in to Summit application as an Admin.  

  2. Navigate to Admin > Advanced > Standard Operating Procedure (SOP)
Departments or Tenants are visible in the dropdown without ITOM licence.   
117127 / 118132The newly created parsers were not working according to the mentioned conditions. However, it was picking another Parser.

Prerequisites:

In the SymphonyAI Summit application, configure a Mailbox.

Steps:

  1. Navigate to Admin > Notification > Mailbox.

  2. Select Mailbox from Filters.

  3. Create multiple Notification Parsers with conditions from the Actions Panel.

  4. Send Email to the respective mailbox as per the conditions specified in the notification parser page.

  5. In the Customer Scheduler, run the respective job.

  6. Navigate to Incident > Incident List.

  7. Validate the Incident created via Parser.
Newly created parsers are working according to the mentioned conditions.
120191On receiving Password Reset Notification Email, the hyperlink was not re-directing to the SaaS URL. Instead, it was directing to the Base URL.

Prerequisites:

  1. Re-directing URL to be configured in the SaaS URL.

  2. Map the customer to any one user.

Steps:

  1. Log in to the  Summit application.

  2. Navigate to Admin > Users > User List.

  3. Select Tenant from the Filter.

  4. Click SUBMIT.

  5. Click Access tab.

  6. Enable the Send Password Change Notification checkbox.

  7. Click SUBMIT.
The hyperlink in the Password Reset Notification Email is directing to the SaaS URL successfully.


Asset Management

Issue #

Issue Description

Scenario

Resolution

120265 Excel import assets were not getting displayed. However, the count was getting displayed correctly. 

Prerequisites:

  1. Navigate to Asset > Manage Assets > Import > Import Asset. The Import Asset page is displayed. Fill in the mandatory information. Click Submit and import the data.

  2. Navigate to Asset > Manage Assets > Import > Import Asset. The Import Asset Page is displayed.

  3. Fill in the required and mandatory information. Click Submit and import the data.

Excel import assets are getting displayed correctly as per the count.

On Import Asset page, the system displays a validation message if you attempt to map same attribute for more than one destination field.

A sample screenshot is shown below:

“You cannot map the same Hostname for more than one destination field. “

117509

Deactivation Approval

“Combination of IT and Approver Type already exists.”

Steps:

To Configure Approver, perform the following steps:

  1. Select Asset > Configuration > Others > Deactivation Approval Matrix. The DEACTIVATION APPROVAL MATRIX page is displayed.

  2. On the ACTIONS panel of the DEACTIVATION APPROVAL MATRIX page, click CONFIGURE APPROVER. The CONFIGURE APPROVER pop-up page is displayed.

  3. On the CONFIGURE APPROVER pop-up page, specify all the required information.

  4. Click SUBMIT.

To Configure the Deactivation Approval Matrix, perform the following steps:


  1. Select Asset > Configuration > Others > Deactivation Approval Matrix.

  2. On the FILTERS pop-up, select a Tenant and click SUBMIT. 

  3. Under the DETAILS section of the DEACTIVATION APPROVAL MATRIX page, specify all the required information.

  4. Select the number of approval levels to be added in the Deactivation Approval Matrix.

  5. Select the value from the drop-down list. The Master Type Value is configured on the COMMON MASTER page.

  6. Specify the receipt e-mail ids.

  7. Specify the e-mail ids of the users to be notified at each approval level.
The configured Approval Matrix displays successfully for inactive approver and the user changes approver to active user, to approve the assets. 
119887In the Asset Management module, in Tile View, the Asset HOST NAME was not showing when the browser zoom was at 100% and the HOST NAME was populating when browser zoom reduced to 75%. 

Prerequisite:  

  1. Fixed Assets should be allocated to User.  
     

Steps:   

  1. Navigate to Asset > Manage Asset > My Asset List.  
  2. Select Tile View  
  3. Verify if the HOST NAME is populating.  
The Asset HOST NAME along with other details is being displayed as desired.


Platform

Issue #

Issue Description

Scenario

Resolution

117029The Status of Authorization Details was displayed blank to the end-user for whom the approval was pending. 

Steps: 

  1.  Log in to the SymphonyAI Summit Application.
     
  2. Navigate to Reports > Problem Management module. 
     
  3. In the Search Report field, search for a report and click the searched report.  
     
  4. Click Problem ID. 
     
  5. On the left panel, click Approval Icon to view the Approval Details.  
In the Authorizer Details section, the Status of Approval is displayed as intended. 
118054Configured Notification Parser for General Conditions (Contains or Does Not Contains’ Operators) was not creating Incidents for the POP3 mailbox. 

Prerequisites:  

In the SymphonyAI Summit application, configure an Incident Notification Parser for the mailbox with General Conditions (Contains or Does Not Contains’ Operators)  

Steps:  

  1. Send Email to the respective mailbox as per the conditions specified in the notification parser page .  
     
  2. In the Customer Scheduler, run the respective job. 
     
  3. Navigate to Incident > Incident List. 
Creates Incident for configured Notification Parser using general conditions without any issue.  
115377

The offboarding icon list was displayed to all users, even if they were not configured for the respective domain.  

For Example:  

A user from a sub-domain who does not have access to domain APEX could view all the inactive users’ details. 

Prerequisites:  

Configure the Offboarding configuration for APEX Domain and offboarded users should consists of open records. 

 Steps: 

  1. Log in to the SymphonyAI Summit Application.
  2. Click the Offboarding icon from the Menu bar.
The Offboarding icon displays the list of users based on the configured domain. Global Domain users can view local domain offboarded records. 

120884/ 

122148/ 

120473/

120475

In the SymphonyAI Summit Mobile App, users can raise an incident, which is then assigned to a random workgroup.

Note

This issue is also addressed in the SymphonyAI Summit Old Mobile App.


Steps:  

  1. Log in to the SymphonyAI Summit Mobile App. 
     
  2. Navigate to Incident > Category. 
     
  3. Select a Category > Configure > Enable Location-wise workgroup routing. 
     
  4. Navigate to Incident > New Incident. 
     
  5. Select Category and Location as per the Category Configuration.  
     
  6. Click SUBMIT. 
Incident is assigned to appropriate workgroup as designed.
122735In the Service Request Details page, autofill attributes were displayed in grey.  

Steps:  

  1. Log in to the SymphonyAI Summit Mobile App. 
     
  2. Navigate to Request widget, click required SR from the list. 
     
  3. Click SR Details tab. 
Autofill Attributes in the Service Request Details page are displayed without any issue. 
122935

On the Approve Service Request page, the user was encountering the following issues:

  1. An error occurred while approving an SR.

  2. The Approve Service Request page was not rendered appropriately. It was displayed in grey. Displayed for On-hold, Rejected, and Referred Back statues.











Issue I

Steps:

  1. Log in to the SymphonyAI Summit Mobile App.

  2. Navigate to Request widget, click required SR from the list.

  3. Click 3dots from the button left of the page.

  4. Click Approve option from the list.

  5. Enter the Remarks and click OK.

Issue II

Steps:

  1. Log in to the SymphonyAI Summit Mobile App.

  2. Navigate to Approve Service Request widget, click required SR from the list.

  3. Click SR Details tab.
The user can approve an SR successfully, and the Approve Service Request page displays without any issue.
120191

On receiving Password Reset Notification Email, the hyperlink was not re-directing to the SaaS URL. Instead, it was directing to the Base URL. 

Prerequisites:

  • Re-directing URL to be configured in the SaaS URL. 
  • Map the customer to any one user.

Steps:

  1. Log in to the Summit application.

  2. Navigate to Admin > Users > User List.

  3. Select Tenant from the Filter.

  4. Click SUBMIT.

  5. Click Access tab.

  6. Enable the Send Password Change Notification checkbox.

  7. Click SUBMIT.
The hyperlink in the Password Reset Notification Email is directing to the SaaS URL successfully.


Known Issues 

This section describes the known issues detected by the SummitAI 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).