Customer Fixed Issues and Known Issues Tahoe SP3 HF11

Issue ID

Issue Description

Scenario

Resolution

Prerequisites:

1. Location based Workgroup routing should be configured for the catalog being used.
   
   
2. Enable Location and Select User Location checkbox should be enabled.
   
   
3. The logged-in user should be part of routing location configured for the catalog being used.

Steps:

1. Navigate to Request > User > New Service Request.  The New Service Request page is displayed. Select the Tenant and Catalog.
   
   
2. Under the Location Search bar Select the Location from routing table. Specify the mandatory fields and click SUBMIT.
   
   
3. Navigate to Request > Manage Service Requests > Service Request List. The Service Request List page is displayed.
   
   
4. Click the required SR ID on the list page. The Service Request ID Details page is displayed.  Verify the assigned Workgroup (Assignments > Workgroup).

Prerequisite:

Login to SummitAI application and raise an incident.

Steps: 

1. Navigate to Incident > Manage Incidents > Incident List. Select the above created incident and change the status of the Incident from New to In Progress. Specify some remarks in User Communication field under Communication Click Submit.
   
   
2. Resolve the above ticket by copy pasting the text mentioned in User Communication field to the Solution field under General tab.

Prerequisites: 

1. Navigate to Admin > Infrastructure > Form Builder. The Custom Attributes for Incident Management module page is displayed. Select the module as Incident Management.
   
   
2. Click Add New. Select the group. Select only one workgroup. Add any custom field. Click Next and Save.
   
   
3. Navigate to Incident > Others > Rules. The Rule page is displayed. Click Add New. Select any other Workgroup and save. 

Issue 1: 

The system was not displaying the filtered incidents on the Incident List page as expected if the filter was selected as Location which are imported during the Ad user import.

Issue 2: 

The system was not displaying the filtered incidents or Service Request List page as expected if the filter was selected as Location which are imported during the Ad user import.

Prerequisite:

While importing users the Location should be mapped. 

Steps (Scenario I): 

1. Navigate to Incident > Manage Incidents > Incident List. The Incident List page is displayed.
2. Click Filters. Select Filter (Field) as Location or Customer Location.

Steps (Scenario II):

1. Navigate to Requests > Manage Service Requests > Service Request List. The Service Request List page is displayed.
2. Click Filters. Select Filter (Field) as Location or Customer Location.

Resolution 1:

The system is displaying the filtered incidents as expected for selected filter as Location which are imported during the Ad user import.

Resolution 2:

Prerequisites:

• Delete the standard templates from the standard change template list.

Steps:

1. Navigate to Change > User > New change record.
   
   
2. Select the desired tenant, owner WG.
   
   
3. Select change type as standard. The standard import template pop-up gets displayed.
   
   
4. Fill in the standard templates with the desired fields.
   
   
5. Verify the standard templates.

Prerequisites:

•  Enable the Information Panel on the Incident/Service Request List checkbox in the Application settings.

Steps:

1. Log in to the Application as an Analyst.
2. Navigate to Request > Service Request List.
3. Now verify the Total Service Requests count in Information Panel.

Steps:

1. Create incidents with child category through web and API.
   
   
2. Navigate to the Incident List page and click the incident ID from the list.
   
   
3. Resolve the Incident by giving Category and closure Category values.
   
   
4. Navigate to the Incident List page and check the category value for resolved Incidents Incident List, Reports, and Incident details page.

Steps:

1.  Navigate to Reports.
   
   
2.  Select Incident Feedback Report.
   
   
3. Click Filters icon on the ACTIONS panel to specify the filter criteria to display records in the INCIDENT FEEDBACK REPORT page.
   
   
4. Click EXPORT ALL to export all the records to a Microsoft Excel sheet.

Incident Feedback Report generates with Export to all option and is displaying appropriately after the resolution.

Steps:  

1. Navigate to Request > Configuration > Service Request Masters > Classification.  
   
   
2. Create a New Node. Click Submit.  
   
   
3. Right-click on the newly create Node to set it as default. Click Submit.  
   
   
4. Or right-click on any existing node to set it as default. Click Submit.  
   
   
5. Right-click on the default node and remove it as default. Click Submit.  

Steps:  

1. Navigate to Incident > Manage Incidents > New Incident for Users.  
   
   
2. Create one parent incident and one child incident.  
   
   
3. Link the child incident to the parent incident.  
   
   
4. Click Submit. 
   
   
5. Update the fields such as Priority, Impact, and Urgency in the Parent Incident. 
   
   
6. Verify if the updated fields are updated in the child incident.  

If the “CUSTOMERSLA MATRIX” is configured, then the system will consider “CUSTOMERSLA MATRIX” configuration on priority when parent and child incidents are updated.  

If the “CUSTOMERSLA MATRIX” is not configured, only then the system will update details of the Parent incident to child incident.  

124832

End user log Incident page was taking time to get fully loaded.

Steps:

1.       Indexes were added for IM_Category_Customers                and IM_Category_Master tables.

2.       Updated the stored procedure i.e.                                          ‘UDFT_GetIMDefaultMasterData.sql’

The loading time of the page is normal after the resolution.

122614

Category Disable Option was Not Working for End User

Steps:

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

2.       Click on Category > Disable Category for End User.

3.       Login as End User and navigate to Incident > Users >           New Incident.

4.       Click on search icon (Category).

Category disable option not working for the End User gets solved after the resolution.

122722

While creating the Workflow in Service Catalog, user was able to select Technician Selectable at any level of Approval levels. But while editing the Workflow, the user was not allowed to select Technician Selectable at any level except the third Approval Level. 

Steps:

Creating Workflow:

1. Drag and drop the approval levels while configuring the Workflow.
   
   
2. Select 'Technician Selectable' at last Approval level.
   
   
3. Click on Submit.

Steps:

Editing Workflow:

Prerequisites: Workflow should be in maintenance status.

1. Log into application as end user.
   
   
2. Navigate to Catalog > Edit Service Catalogs.
   
   
3. Click Configured Catalog.
   
   
4. Click Workflow icon.
   
   
5. Edit the same Catalog Workflow.
   
   
6. Validation message will come.

While editing & creating the Workflow in Service Catalog, the user is able to select Technician Selectable at only last Approval Level.

122907

Unable to download the attachments in the Release Management Document tab.

Prerequisites:

1. Navigate to Release > Release Record List. 
    
2. Open a Record List. 
    
3. Navigate to Documents Tab. 
    
4. Upload the attachment. 
    
5. Click Add > Submit.

Steps:

1. Navigate to the Document tab. 
    
2. Click on the attachment to download it.
   
   

Successfully downloading the attachments in the Release Management Document tab. Download the attachment from the Document Detail table as well.

124999

Updated Time was not getting captured in the Ticket Master Table while creating an Incident through Mail to Ticket.

Prerequisites:

1. Mailbox should be configured.

Steps:

1. Create an Incident through Mail to Ticket.
   
   
2. Fetch the records using "IM_GetUpdatedIncidentDetails" payload.

Updated time is successfully getting captured in the Ticket Master Table while creating an Incident through Mail to Ticket.

124873

While converting the Problem Record to Knowledge Record, HTML codes were visible in the Question field of the Knowledge record page.

Prerequisites:

1.       Description of the problem record should contain bold, italics characters, line space, etc.

 Steps:

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

2.       Open any RCA approved/reviewed problem record.

3.       Click on Add to Known Error in the GENERAL Tab.

4.       Verify the Question field in New Knowledge Record            > General tab.

The HTML tags are removed from Question field of Knowledge Record page after the resolution.

122399

 The "Get previous version" option was taking to the new Release Record page. 

Steps:

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

2.       Open any deployed release.

3.       Select P.R. Review tab.

4.       Select Yes in the drop-down option in ‘Do you want              to revert the Release version to the previous version?’

5.       Click Submit.

6.       Go to the VERSION HISTORY tab and click Get the previous version.

The issue of “Get previous version” is solved after the resolution.

122906

Different attachments were getting downloaded in the Release Management Test tab.

Steps:

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

2.       Open any release and go to the TEST tab.

3.       Create two test completion with different attachments and submit.

The issue of different attachments getting downloaded is solved after the resolution.

124394

In the Change Management Module, a few TASKS show as DRAFT status in reports while they are in NEW status in the instance.   

Prerequisites: 

DN jobs should be running successfully. 

Steps:  

1. Navigate to Change > User > New change record. Create a new change record. 
   
   
2. Create a task either auto task or manual task for the create CR. 
   
   
3. Approve the created Change Request. 
   
   
4. The status of the Task is automatically changed from DRAFT to NEW.  
   

In the reports, TASKS are shown in NEW status and not in DRAFT status. The Tasks created are showing the same status in instance and reports.  

122659

While raising a Service Request, selecting the Catalog with Multivalued group in the Form Builder page, results in an Oops error. 

Prerequisite: 

The Catalog should be created with Multivalued group, under this group, file attribute and multivalued dropdown should be present, wherein the attachment limit is single and multiple, and you need to publish this Catalog. 

Steps: 

1. Log in to the application. 
    
2. Navigate to Request > New Service Request.  
    
3. Select the respective Tenant, where the Catalog is configured. 
    
4. Select the above configured Catalog. 

The Oops error message does not appear when the Catalog with Multivalued group which has file attribute and multivalued dropdown is present is selected.  

122313

Location-based routing option was not working in the SR module. The ticket was routed based on the Logged by User location instead of the Caller location.

Pre-requisite:

The user must belong to some location and the Catalog used for the SR should have Configured location-based Workgroup allocation.

Steps:

1. Navigate to Request > Manage Service Request > New Service Request for User.
   
   
2. Enter the required details and select Catalog.
   
   
3. Click Submit.
   
   
4. Navigate to Request > Manage Service Request > Service Request List.
   
   
5. Click SR ID and validate the Caller location.

Location-based routing option is working in the SR module. The ticket is routed based on the Caller’s location.

120749

Filters on the Task List page were not working as expected from the input provided by the user.

Steps:

1. Navigate to Change > User > Task List.
   
   
2. Click Filters.
   
   
3. Enter the values and click Submit.
   
   
4. Validate the result from Filters.

Filters option on the Task List page is working as expected from the input provided by the user.

121882

Upon changing the status of the Change Record from Draft to Cancelled, Task was linked to the cancelled CR automatically.

Steps:

1. Navigate to Change > User > New Change Record.
   
   
2. Enter the required details of CR matching to Task Template and click SAVE DRAFT.
   
   
3. Click Status and select Cancelled.
   
   
4. Click Submit.
   
   
5. Click the RELATIONSHIP tab and validate.

Upon changing the status of CR from Draft to Cancelled, Task is not linking to the CR.

124673

The Release Record's Status upon changing to Deploy, on the DEPLOYMENT tab the Deployment Status was set to Designed and not editable. However, upon changing the Status to Deploy it should be Ready to Deploy according to SummitAI manual.

Steps:

1. Navigate to Release > User > Release Record List.
   
   
2. Click RR ID having either Test or Build status.
   
   
3. Select Deploy from the Status dropdown list.
   
   
4. Click DEPLOYMENT.
   
   
5. Validate Deployment Status.

The Release Record's Status upon changing to Deploy, on the DEPLOYMENT tab the Deployment Status is Ready to Deploy.

123323

The Vendor SLA Matrix was not functioning as expected in the SR module.

Prerequisite:

1. Navigate to SLA > Underpinning Contract > New Underpinning Contract Specification.
   
   
2. Create an Underpinning Contract and approve.
   
   
3. Navigate to SLA > Underpinning Contract > Underpinning Contract Agreement List.
   
   
4. Select Agreement and Publish the Underpinning Contract.

Steps:

1. Navigate to Request > Manage Service Request > Service Request List.
   
   
2. Click SR ID.
   
   
3. Click VENDOR INFORMATION.
   
   
4. Select VENDOR and SERVICE NAME.
   
   
5. Enter the Vendor Incident Details.
   
   
6. Select Priority and Start Date.
   
   
7. Verify Resolution Deadline.

When deactivating assets in the asset inventory, the following field values

was not getting updated:

•    FAR Plant Code
•    Vendor Name for Deactivate
•    Disposed Date
•    Disposal Location
•    Email ID Detail

Even for custom attributes, the issue was reflected.

Prerequisites:

1. Log in to the application with admin module access with fixed assets from multiple categories present in the Asset Inventory with status as In-Store, Allocated and Inactive.
   
   
2. Maker-Checker should be enabled for Deactivate functionality.
   
   
3. Configure the Approver for the respective Approval level in the Approval matrix page.
   
   
4. Configure custom attributes for the ASSET DEACTIVE page through the ACTION ATTRIBUTE CONFIGURATION page.

Steps:

1. Navigate to Asset > User > Manage Assets > Asset Inventory.
   
   
2. Click the Fixed Asset Type and select the required Tenant.
   
   
3.  Filter in-store assets of the required category.
   
   
4. Select the asset and verify the present data in the custom attributes.
   
   
5. Click Asset Deactive on the ACTIONS panel. The Asset Deactive list is displayed.  In the ASSET DEACTIVE page, type the required details into the displayed custom attributes and static attributes.
   
   
6.  Click SUBMIT, verify the confirmation message, and click OK.
   
   
7. Navigate to Asset > User > Manage Assets > Approvals > Maker- Checker Approval.
   
   
8.  Select the tenant from the FILTERS popup.
   
   
9. In the FILTERS popup, Select Deactive Transaction Type and click SUBMIT.
   
   
10. Approve the assets under Deactive Transaction Type Approval.
    
    
11. Navigate to Asset Inventory and verify the updated asset details in the respective columns.

Field values for deactivated assets saves in the asset inventory and are displaying appropriately after the resolution.

Oops error was coming while creating a New Service Request in the Service Catalog page.

Prerequisites:

1. Navigate to Catalog > Create Service Catalog.
   
   
2. Fill in all the details.
   
   
3. Click Next. 
    
4. Click Submit.
   
   
5. Navigate to Catalog > Approve Service Catalog. 
    
6. Navigate to Approval Status. 
    
7. Change the status of the Catalog to Publish. 
    
8. Click Submit.

Steps:

1. Navigate to Request > New Service Request. 
    
2. Select a tenant. 
    
3. Open a Service Catalog. 
    
4. Fill in all the details. 
    
5. Click Submit.
   
   

Successfully creating a New Service Request in the Service Catalog page.

Registration Time was appearing in IST instead of JST in the APPROVE RELEASE RECORDS page. 

Prerequisite:

1. User should be logged in with JST time zone.

Steps:

1. Login to the Summit application as end user.
   
   
2. Navigate to Release > User > Release Record List.
   
   
3. Verify if the Registration Time is displayed in JST.

Prerequisite:

1. Create a Catalog with multivalued group (under this group file, Multivalued dropdown attributes should be present).
   
   
2. Publish the Catalog.

Steps:

1. Login to the Summit application. 
   
2. Navigate to Request > User Manage Service Requests > New Service Request for User.
   
   
3. Select the Catalog created which has a multivalued group (under this group file, Multivalued dropdown attributes should be present).

Movement details are not captured in the Audit Trail of ASSET DETAILS pop-up when the user directly performed the Store/Floor Movement. 

Steps: 

To perform the Store/Floor Movement for an asset, perform the following steps: 

1. Navigate to Asset > User > Manage Assets > Asset Inventory. 
    
2. Select the desired asset type on the Asset Inventory page. 
    
3. Select the desired Tenant from the drop-down, which is a mandatory field. 
    
4. Click the desired Allocated / In–Store asset count hyperlink. 
   Asset List page is displayed.  
    
5. In the FILTERS pop-up, select a Store/Floor and click SUBMIT. 
    
6. Select the desired asset checkbox and click Store/ Floor Movement. 
   Store/Floor Movement Details configuration page is displayed. 
    
7. Select the Destination Store/Floor Movement and click SUBMIT. 
    

To check the Movement History and Audit Trail details of the moved asset, perform the following steps: 

1. Navigate to Asset > User > Manage Assets > Asset Inventory. 
    
2. Select the desired asset type on the Asset Inventory page. 
    
3. Select the desired Tenant from the drop-down, which is a mandatory field. 
    
4. Click the Asset ID count hyperlink of the moved asset. 
   ASSET DETAILS pop-up is displayed. 
    
5. Check and verify the movement details in 
   Asset History > Audit Trail. 

Barcode was not available on Gate Pass for any movements after the Approver approved the movement. 

Steps:  

1. Navigate to Admin > Advanced > Notifications > Notification Template. 
    
2. Select the desired Tenant, which is a mandatory field. 
    
3. Select Asset Management module from the drop-down. 
    
4. In the GENERAL grid, navigate and click Print Gate Pass Form for Asset Movements hyperlink. 
    
5. Click Keywords hyperlink. 
   KEYWORDS - PRINT GATE PASS FORM FOR ASSET MOVEMENTS pop-up is displayed. 
    
6. Check *ASSETDETAILS_TABLE* 
   Click More hyperlink. 
    
7. Check and verify *BARCODE* keyword in the ASSET DETAILS - ADDITIONAL KEYWORDS table. 
    

To check the Barcode on Asset Gate Pass, perform the following steps: 

1. Navigate to Asset > User > Manage Assets > Approvals > Print Gate Pass. 
    
2. Click the desired Movement ID hyperlink. 
   Goods Movement Gate Pass is displayed. 
    
3. Check and verify Barcode column. 

The following timeout error was displayed on the Asset verification page (Verified Assets). 

“Oops! An error occurred”  

Steps: 

1. Navigate to Asset > User > Manage Assets > Variance > Asset Verification. 
    
2. Select the desired Tenant, Location, and other details in the FILTERS pop-up. 
   Click SUBMIT. 
   Asset Verification LIST page is displayed. 
    
3. Select the desired asset checkbox and click VERIFY ASSET from the right ACTIONS panel. 
   VERIFIED ASSETS List page is displayed. 
    

User was unable to download the Asset Dashboard data. 

The following error was displayed:  

Oops! An error occurred. 

Steps:  

1. Navigate to Reports > Asset Management > Dashboard. 
    
2. In FILTERS pop-up, select the desired Tenant and Location. 
   Click SUBMIT. 
    
3. On the Dashboard page, scroll down to see the list with asset count hyperlink. 
    
4. Click the desired asset count hyperlink.
   Asset List page is displayed.
   
   
5. Click the Export icon to download the Dashboard data. 

Data was not saved while deactivating the assets. The following issue was observed: 

*When the user entered values and clicked SUBMIT, the asset was saved successfully but the values were not updated in the below-mentioned fields for the deactivated assets in the Asset inventory: 

• FAR Plant Code 
• Vendor Name for Deactivate 
• Disposed Date 
• Disposal Location 
• Email ID Detail 

Steps: 

To deactivate assets, perform the following steps:  

1. Navigate to Asset > User > Manage Assets > Asset Inventory. 
    
2. Select Fixed Asset on the Asset Inventory page. 
    
3. Select the desired Tenant from the drop-down, which is a mandatory field. 
    
4. Select the desired In-Store asset count hyperlink. 
   Fixed Asset LIST page is displayed. 
    
5. Select the desired asset checkbox and click ASSET DEACTIVE from the right ACTIONS panel. 
    
6. In the Asset Deactive page, provide all the details and click SUBMIT.  
   
   

To check the newly deactivated asset details on Asset Inventory, perform the following steps: 

1. Navigate to Asset > User > Manage Assets > Asset Inventory. 
    
2. Select Fixed Asset on the Asset Inventory page. 
    
3. Select the desired Tenant from the drop-down, which is a mandatory field. 
    
4. In the Fixed Asset List page, check the mentioned columns of deactivated assets.  

Under Asset Management, dropdown values are not being updated by the standard API.  

Steps: 

1. Under the Postman, use the payload named: AM_UpdateAsset_Details. 
   
   
2. Enter the required parameters to update attributes for asset details (including dropdown). Click Send. 
   
   
3. Update the dropdown field value over API. 
   
   
4. Navigate to Asset > User > Manage Assets > Asset Inventory.  
   
   
5. Select the Fixed Asset type in the Inventory page. 
   
   
6. Select the tenant from the dropdown. 
   
   
7. Click Instore count hyperlink. 
   
   
8. Click Asset ID hyperlink. 
   
   
9. Verify Asset details which are updated by API.

Issue #

Issue Description

Scenario

Resolution

Unable to perform following tasks in the Change Record List page:

• Save CR as Template
• Edit Template
• Import Template

Steps:

1. Log in to the Summit Application.
   
   
2. Navigate to Change > User > Change Record List.
   
   
3. Click the CR NO hyperlink and click SAVE AS TEMPLATE from ACTIONS panel.
   
   
4. Enter the required Change Template Name and click SAVE TEMPLATE.
   A confirmation message is displayed.
   
   
5. Navigate to Change > Users > New Change Record.
   
   
6. Select the required Tenant for which CR Template is Saved.
   
   
7. Click IMPORT TEMPLATE from ACTIONS panel.
   The Import Template Pop-up is displayed.

The CR template is functioning as designed and without any issue.

In the Service Request Catalog page, the approvals were not getting skipped even if the Skip Approvals check box was not selected. 

Prerequisites: 

• Configure a workflow with different levels of approvals.
• Create a SR with required details.
• Approve a SR with first level of approval. 

Steps:

1. Log in to the Summit Application as an approver.
   
   
2. Navigate to Request > Approve Service Request.
   
   
3. Click SR ID hyperlink.
   
   
4. Approve the Service Request and verify the next level of approvals.

The Skip Approval functionality is working as designed and without any issues.

In Summit Mobile App, the Submit button was not displayed in the create new incident page. 

Prerequisites:  

• Add Location field in Log Incident page. 
   
• Do not map Location field for an end-user.  

Steps:  

1. Log in to the Summit Mobile App. 
    
2. Click Log Incident. 
    
3. Select a Tenant.

The Submit button is displayed on the New Incident page without any issue. 

The configured Validate Controls in FORM BUILDER was not working as expected in New Mobile App.

Prerequisites:  

• Create and Publish a Catalog with attributes such as Number, Text Area, Drop-down etc. 
   
• Configure rule or action in Validate Controls and Save it.  

Steps:  

1. Log in to the Summit Mobile App. 
    
2. Click the Service Request and Click the configured Catalog. 
    
3. Select the required option configured in Validate Controls and check if the rule and actions are performed appropriately. 

The configured Validate Control conditions are working as designed. 

Retrieve all the details of actively running major incidents.

Request Payload

Return Payload

The API fetches all the major incidents for the given payload request.

Instead of a text box for Description field on the Incident page, there was a HTML tag displaying. 

Steps:  

1. Open ‘Postman’ and use the payload named: IM_LogOrUpdateIncident.
    
2. Provide the details and click ‘Send’.

In the CMDB module, the Managed By field was capturing the Workgroup Display name instead of the workgroup name.  

Steps:  

1. Navigate to CMDB > User > Manage Configuration Items > Configuration Item List. 
   
   
2. Click any CI NO.  
   
   
3. Verify if the Managed By field is displaying the correct Workgroup name.

Issue ID

Issue Description

Scenario

Workaround

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

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.

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.

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.

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.

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

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.

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.