Professional Documents
Culture Documents
Verifies the
a. Changes to Work flow
b. Invoice spreadsheet Fields details
Test objective
c. Mapping for upload payments operations
d. Field Validations
Environment Requirements :
Test Pre-Conditions a. Dev instance will be used to execute the test cases
a. TATA Servicenow and Thomson reuters legal portal(3rd Party Tool) should be integrated
Sr No Step Detail
Verify that the following field values are mapped from Thomson legal portal to
servicenow.
(Column Name of in invoce spread sheet from Legal Portal > Fieldname in ServiceNow
Respectively)
a. Expense Frequency > Expense Frequency
b. Customer Success Based >Customer Success Based
c. Item Category > Item Category
d. Serengeti Invoice No > Serengeti Invoice No
e. Processed By >Requested By
2 f. Invoice Number > Invoice Number
g. Total > Approved Amount
h. Invoice Currency > Local Currency
i. GL Account #1 > GL Account
j. Cost Center #1 > Cost Code
k. Vendor Name > Office Vendor ID
l. Billing Period Start Date > Start Date
m. Billing Period End Date > End Date
n. Matter ID > Description of Request
o. Matter Short Name > Justification for the requisition
Validatio
Verify following fields are mandatory to raise the request (Line Item) in the TATA
Servicenow Instance:
1. Function- Will be auto populated from Approval Matrix Table using Cost Code
2. Sub Function- Will be auto populated from Approval Matrix Table using Cost Code
3. GL category- Will be auto populated from GL Account table using GL Account
3
4 Verify that Default value “NA” will be captured for customer success-based field.
Verify there will not be any existing request based on “Invoice Number” & “Office Vendor
5
ID”
Verify that GL Account will be valid/active and exist in ServiceNow (If it is inactive, then
6 request will be canceled, and the notification will be sent to the request by user with
appropriate comments.)
7 Verify that Start & End Date will fall in same financial year
8 Verify that Currency will be valid and exist in system
Approval Process Depends on the CC(Cost Code)
Once webservices consumed and Request is Generated
verify that if Cost Center belong to “Legal” department , There will not be any approval on
9
the Request. RITM and Demand gets created
Verify that If Cost Center not belong to “Legal” department, then approval process
10
follows Approval Matrix, then the RITM gets created
Once the request is created on Servicenow from the invoice attachment which is fetched
11 from serengeti,ServiceNow will pass Invoice Number, RITM & Demand Id if cc=Legal by
consuming upload payments operations
Once the request is created on Servicenow, from the invoice attachment whohc is fetched
12 from serengeti,ServiceNow will pass Invoice Number & RITM if cc!=Legal by consuming
upload payments operations
Verify that on the staging form, 'Response Status' and 'Status Code' is maintained to know
13
the status of the request update in the third party tool.
Input Expected results
If the Cost Center is not Legal then approval process should follow
the approval matrix, then the RITM gets created
User should be able to verify on the staging form that 'Response Status'
and 'Status Code'
Pass/Fail Additional information
Test Script
Reports for Error Handling
Name
Environment Requirements :
Test Pre- a. Dev instance will be used to execute the test cases
Conditions
a. Snow and Thomson reuters legal portal should be integrated
Verify that if there is any error while calling Legal Tracker Tool’s
2 API or getting response then notification will trigger to Legal
Tracker Portal tool support team.
Test objective Verifies the email Notifications triggeres for Error Handing
Environment Requirements :
Test Pre- a. Dev instance will be used to execute the test cases
Conditions
a. Snow and Thomson reuters legal portal should be integrated