Page Comparison

95301 

Change Managers were not able to move the change records to draft unless they have access to the specific workgroup. 

Move to Draft button was disabled for the Change Manager even when the Change Manager had analyst access to other workgroups of the same tenant. 

Prerequisites: 

1. Configure a Change manager for any of the workgroup. 
2. Make sure that the Change Manager does not have analyst access to the desired workgroup but analyst has access to other workgroups of the same tenant. 

Steps: 

1. Navigate to Change > User > Change Record List. 
2. Click on any Change Record displayed. 

Move to Draft button is enabled for the Change Manager and the Change Manager can move the change records to draft successfully. 

95975 

Standard Dashboard report for incident module was displaying no data error in donut chart 

Procedure:  

Step 1: Click on Reports 

Step 2: Select the 'Incident Management' from the drop-down list or click on Incident Management 

Step 3: Select 'Incident Dashboard' from Reports drop down list 

Step 4:  Click on the 'Filters' under the actions panel. 

Step 5: Select Tenant and Month from the respective drop downs and click on submit. 

On clicking the subsequent donut chart, it is showing invalid data on popup page. 

Standard Dashboard report for incident module is displaying appropriate data in donut chart. 

95217 

Despite setting the configurations - Private Log & User Communication, to mandatory at the tenant level, validation for these mandatory fields were not working on Service Request Details page. 

Precondition:  

1. Configure 'Private Log’ as mandatory for Assigned Status & ‘User Communication’ as mandatory for Pending status under Mandatory Configuration for Private Log & User Communication section in SR Module on Tenant Level Configuration Page. 
2. Raise the SR. 

Procedure:  

1. Login to the application as Analyst. 
2. Navigate to Request > Service Request List. 
3. Click on above raised SR ID. 
4. Now click on Assigned status & enter mandatory fields 
5. Click Submit. 

Without filling the Private Log & User Communication, submission of details is possible on Service Request Details page. 

Private Log & User Communication mandatory validations are working on  Service Request Details page. 

1. In the Form Builder dropdown list, Release Management option was not available.
2. There were no Notification Templates available for the Release Management because the Release management option was not available in the Module dropdown list.

Prerequisites:

Issue 1:

1. Navigate to Admin > Basic > Infrastructure > Form Builder.
2. Select Tenant.
3. Click on Module dropdown.

Issue 2:

1. Navigate to Admin > Advanced > Notifications > Notification Template.
2. Select Tenant.
3. Click on Change dropdown option.

Release Management option is available in the Form Builder dropdown list and Notification Template > Change dropdown list.

Once the CR is referred back to the initiator, if the Change Initiator and the Change Manager are same, the system displayed the following message: 

“You cannot update this CR as it is referred back to the initiator.” 

Also, the SUBMIT button was greyed out and hence the end-user was unable to edit the CR and submit the CR again.

Prerequisites:

1. Navigate to Change > Configuration > Change Manager.Select the required Tenant. Click on Add New underThe DETAILS page is displayed.
2. Select the same user as Change Manager who is the change initiator. For Example: If Change Initiator is John, then select Change Manager as John. Select required Workgroup and click SUBMIT.
3. Navigate to Change > User > New Change Record. The NEW CHANGE RECORD page is displayed. Select the required Tenant, Owner Workgroup, Change Type, Category, Change Category and enter all the mandatory fields. Click SUBMIT. CR ID is generated.
4. Login as Approver. Click on Approval tab under ACTIONS. Select Referbackto initiator from the Status drop-down list. Click Submit.

Once the CR is referred back to the initiator, if the Change Initiator and the Change Manager are same, the SUBMIT button is not greyed out and hence the user is able to edit the CR. and submit the CR again.

Custom attribute that was a child of another custom attribute value was displaying an error while trying to filter.Using form builder parent and child in common master type with same fields were mapped.

There are no values for the selected Filter. Select different filter was displayed though values existed for child dropdown. This blocked the analyst from selecting a value for the Child dropdown on the filters. 

Pre-conditions: 

1.In Common Master Type configure two common master types in a way that one should be the Parent of another.Configure the values for both.E.g.: Parent Master type name is Country and value is India.Child master type name is State, and value is Karnataka.For Child master type, Parent master type must be configured.

2.Form Builder> Incident Management a tenant is configured for Incident Management module.Two dropdowns  should be configured in a way for first with, Options the source is selected as Common Master and the Type is selected as the Parent Master Type (Country).For second,  in Options field, the source is selected as Common Master and the Type is selected as the Child Master Type (State) .

3) An incident should be logged for the same tenant to which two dropdowns are configured with the source being Common Masters for both. 

Prerequisites: 

Login to application as an Analyst. 

1.Navigate to Incident > Incident List.

2.Expand the Filters dropdown.

3.In Tenant field, select the same tenant to which the incident was logged previously.

4.Add row.

5.In the new row select child dropdown

No error is displayed while selecting Child dropdown.  

Correct values are populated in the dropdown.

In Change Management, Change Workflow customer field was not working based on Requester user customer field value. 

Workflow was getting displayed based on initiator customer instead of requestor customer. 

Pre-condition: 

Different customers should be created for Initiator and Requestor. 

Workflow should be configured based on the desired customer providing If condition at desired tenant level. 

Prerequisites: 

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

2.Select desired Tenant and Requestor who belongs to different customer. 

Ex: Initiator - Priyanka belongs to customer A.Requestor - Manasa belongs to customer B. 

3. Select the desired Change Type, Change Category and workgroup configured for workflow. 

4. Enter all the mandatory field values and click SUBMIT. 

Prerequisites:

1. Click Asset > User > Manage Assets > Asset Inventory.
2. Click Fixed and select the Tenant.
3. Click on any hyperlink available under any column.
4. Click on any Asset ID hyperlink.
5. Click Remote Desktop button.
6. Fill the required information and click Request.

When the dropdown arrow next to the Excel icon was clicked in any report, none of the download format options were displayed but a console error was being displayed.

Prerequisites:

1. Navigate to Reports > Incident Management > New Report.
2. Create an Izenda 7 report.
3. In the Report section, open the created Izenda7 report.
4. Click on dropdown arrow present in Excel icon.

New dashboards like Change Management or CMDB any dashboards and Edited dashboards were not saved. 

The issue was observed with different dashboard edits and creations.

Prerequisites: 

• User A - Eastern Daylight Time (EDT)
• User B - Indian Standard time (IST)

Example:

If user A creates an SR and delegate the SR to user B from different time zone through Delegate functionality, when the user B try to view the delegated request an error message was occurred. 

93509 

When a Service Request was getting converted to an Incident, Description details from the Service Request did not carry over to the Description of the newly created incident.  

It was noted that the issue existed only if the configuration for allowing an Analyst to edit the description of the Service Request was enabled.  

Prerequisite: 

1. Enable the tenant level configuration ‘Allow Analyst to Edit Description’ in the Admin module. 

Steps:  

1. Raise a Service Request with Approval flow and enter Description.  
2. Approve the Service Request. 
3. Convert the Service Request to an Incident. 
4. Check the new incident and verify the Description details. 

The description details from the Service Request are carried over to the new incident while converting a service request to incident. The functionality works fine even if the configuration for allowing an analyst to edit the description is enabled for SR module.  

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.

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 Mobile 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# 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.

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