| 23003 |
3:-SRC |
1 :-Number Type. New a MSISDN Type |
AS per requirenements |
WCT |
P |
|
|
| 23003 |
3:-IM |
2 :-Number Type. Modify a MSISDN Type |
AS per requirenements |
WCT |
P |
|
|
| 23003 |
3:-SRC |
3 :-Number Type. Delete a MSISDN Type |
AS per requirenements |
WCT |
P |
|
|
| 23003 |
3:-SRC |
4 :-Number segment. New a MSISDN Segment Rule |
AS per requirenements |
WCT |
P |
|
|
| 23003 |
3:-SRC |
5 :-Number segment. Modify a MSISDN Segment Rule |
AS per requirenements |
WCT |
P |
|
|
| 23003 |
3:-SRC |
6 :-Number segment. Delete a MSISDN Segment Rule |
AS per requirenements |
WCT |
P |
|
|
| 23003 |
3:-SRC |
7 :-Number Grade. New a MSISDN Grade |
AS per requirenements |
WCT |
P |
|
|
| 23003 |
3:-SRC |
8 :-Number Grade. Modify a MSISDN Grade |
AS per requirenements |
WCT |
P |
|
|
| 23003 |
3:-SRC |
9 :-Number Grade. Delete a MSISDN Grade |
AS per requirenements |
WCT |
P |
|
|
| 23003 |
3:-SRC |
10 :-MSISDN Batch Creation By Service Number |
AS per requirenements |
WCT |
P |
|
|
| 23003 |
3:-SRC |
11 :-MSISDN Batch Creation By File |
AS per requirenements |
WCT |
N |
|
|
| 23003 |
3:-SRC |
12 :-MSISDN Recycle Rule GUI. New a recycle rule fields display |
AS per requirenements |
WCT |
N |
|
|
| 23003 |
3:-SRC |
13 :-Recycle MSISDN to the original organization by condition |
AS per requirenements |
WCT |
N |
|
|
| 23003 |
3:-SRC |
14 :-Goods Specification .
New a CPE Terminal |
AS per requirenements |
WCT |
N |
|
|
| 23003 |
3:-SRC |
15 :-Goods Specification .
Modify a CPE Terminal |
AS per requirenements |
WCT |
N |
|
|
| 23003 |
3:-SRC |
16 :-Goods Specification .
Delete a CPE Terminal |
AS per requirenements |
WCT |
N |
|
|
| 23003 |
3:-SRC |
17 :-Goods Model Specification- View the SKU mune in Goods Specification GUI |
AS per requirenements |
WCT |
N |
|
|
| 23003 |
3:-SRC |
18 :-Goods Stock In |
AS per requirenements |
WCT |
N |
|
|
| 23003 |
3:-SRC |
19 :-Query Goods Stock In records |
AS per requirenements |
WCT |
N |
|
|
| 23003 |
3:-SRC |
20 :-Goods Instance Query for Stock in |
AS per requirenements |
WCT |
N |
|
|
| 23003 |
3:-SRC |
21 :-New Goods Stock Allocation |
AS per requirenements |
WCT |
N |
|
|
| 23003 |
3:-SRC |
22 :-Warehouse management.
New a Warehouse |
AS per requirenements |
WCT |
N |
|
|
| 23003 |
3:-SRC |
23 :-Warehouse management.
Modify a Warehouse |
AS per requirenements |
WCT |
N |
|
|
| 23003 |
3:-SRC |
24 :-Warehouse management.
Delete a Warehouse |
AS per requirenements |
WCT |
N |
|
|
| 23003 |
3:-SRC |
25 :-Warehouse management.
New a Location |
AS per requirenements |
WCT |
N |
|
|
| 23003 |
3:-SRC |
26 :-Warehouse management.
Modify a Location |
AS per requirenements |
WCT |
N |
|
|
| 23003 |
3:-SRC |
27 :-Goods Receive (SAP to SRC) |
AS per requirenements |
WCT |
N |
|
|
| 23003 |
3:-SRC |
28 :-Goods Receive(Reversal)(SAP to SRC) |
AS per requirenements |
WCT |
N |
|
|
| 23003 |
3:-SRC |
29 :-SKU SYNC(SAP to SRC) |
AS per requirenements |
WCT |
N |
|
|
| 23003 |
3:-SRC |
30 :-Goods Transfer(SAP to SRC) |
AS per requirenements |
WCT |
N |
|
|
| 23003 |
3:-SRC |
31 :-Good Disposal (SAP to SRC) |
AS per requirenements |
WCT |
N |
|
|
| 23003 |
3:-SRC |
32 :-Stock transfer (SRC to SAP) |
AS per requirenements |
WCT |
N |
|
|
| 23003 |
3:-SRC |
33 :-Goods Installation (SRC to SAP) |
AS per requirenements |
WCT |
N |
|
|
| 22935 |
1:-Complaint Registration & Tracking on Ufone Website |
1 :-Complaint Registration & Tracking on Ufone Website |
Complaint should be registered |
PTCL |
P |
|
|
| 23003 |
1:-IT |
1 :-Portal Management |
|
WCT |
P |
|
|
| 23003 |
2:-IM |
1 :-SOL-IM-FC-Resource Specification Management |
|
WCT |
N |
5.2.1. SOL-IM-FC-Resource Specification Management |
|
| 23003 |
1:-IM |
2 :-Directory Menu Management |
|
WCT |
P |
|
|
| 23003 |
2:-IM |
2 :-SOL-IM-FC-Model Management |
|
WCT |
N |
5.2.2. SOL-IM-FC-Model and Template Management |
|
| 23003 |
1:-IT |
4 :-Area Management |
|
WCT |
P |
|
|
| 23003 |
2:-IM |
4 :-SOL-IM-FC-Model and Template Management (Active Device) |
|
WCT |
N |
5.2.2. SOL-IM-FC-Model and Template Management |
|
| 23003 |
1:-IT |
5 :-Role Management |
|
WCT |
P |
|
|
| 23003 |
2:-IM |
5 :-SOL-IM-FC-Model and Template Management (Passive Device) |
|
WCT |
N |
5.2.2. SOL-IM-FC-Model and Template Management |
|
| 23003 |
1:-IT |
3 :-System Parameter Management |
|
WCT |
P |
|
|
| 23003 |
2:-IM |
3 :-Model Management (Dynamic values for DSL and PON network device modeling) |
|
WCT |
N |
5.2. Model Management |
|
| 23003 |
2:-IM |
13 :-SOL-IM-FC-Device Management-UC-EIC |
|
WCT |
N |
5.3.3.2.4. SOL-IM-FC-Device Management-UC-EIC |
|
| 23003 |
1:-IT |
11 :-Log Management |
|
WCT |
P |
|
|
| 23003 |
2:-IM |
11 :-SOL-IM-FC-Location Resource Management-UC-Room |
|
WCT |
N |
5.3.3.1.4. SOL-IM-FC-Location Resource Management- |
|
| 23003 |
1:-IT |
12 :-Interface Log |
|
WCT |
P |
|
|
| 23003 |
2:-IM |
12 :-SOL-IM-FC-Device Management-UC-Device Creation/Edition/Deletion/ Export |
|
WCT |
N |
5.3.3.2.1. SOL-IM-FC-Device Management-UC-Device C |
|
| 23003 |
1:-IT |
9 :-Data Privilege Definition |
|
WCT |
P |
|
|
| 23003 |
2:-IM |
9 :-SOL-IM-FC-Location Resource Management-UC-Site |
|
WCT |
N |
5.3.3.1.2. SOL-IM-FC-Location Resource Management- |
|
| 23003 |
1:-IT |
10 :-Data Privilege Configuration |
|
WCT |
P |
|
|
| 23003 |
2:-IM |
10 :-FLC |
|
WCT |
N |
5.3.3.1.2.1. FLC |
|
| 23003 |
1:-IT |
8 :-Organization & Staff Management |
|
WCT |
P |
|
|
| 23003 |
2:-IM |
8 :-SOL-IM-FC-Model and Template Management (Fiber Cable) |
|
WCT |
N |
5.2.2. SOL-IM-FC-Model and Template Management |
|
| 23003 |
1:-IT |
7 :-Job Management |
|
WCT |
P |
|
|
| 23003 |
2:-IM |
7 :-SOL-IM-FC-Model and Template Management (Tube) |
|
WCT |
N |
5.2.2. SOL-IM-FC-Model and Template Management |
|
| 23003 |
1:-IT |
6 :-User Management |
|
WCT |
P |
|
|
| 23003 |
2:-IM |
6 :-SOL-IM-FC-Model and Template Management (Copper Cable) |
|
WCT |
N |
5.2.2. SOL-IM-FC-Model and Template Management |
|
| 23003 |
2:-IM |
32 :-SOL-IM-BS-PON Access Network Instance-UC-OLT |
|
WCT |
N |
6.2.3.1. SOL-IM-BS-PON Access Network Instance-UC- |
|
| 23003 |
2:-IM |
33 :-SOL-IM-BS-PON Access Network Instance-UC-ONT |
|
WCT |
N |
6.2.3.2. SOL-IM-BS-PON Access Network Instance-UC- |
|
| 23003 |
2:-IM |
30 :-Discovery & Synchronization (Pipe instance) |
|
WCT |
P |
5.7. Discovery & Synchronization |
|
| 23003 |
2:-IM |
31 :-Discovery & Synchronization (Data Synchronization) |
|
WCT |
F |
5.7. Discovery & Synchronization |
|
| 23003 |
2:-IM |
28 :-SOL-IM-FC-Impact Analysis |
|
WCT |
F |
5.5.3. SOL-IM-FC-Impact Analysis |
|
| 23003 |
2:-IM |
29 :-Discovery & Synchronization (Collection) |
|
WCT |
P |
5.7. Discovery & Synchronization |
|
| 23003 |
2:-IM |
34 :-SOL-IM-BS-Copper Network Instance-UC-MDF |
|
WCT |
N |
6.2.7.1. SOL-IM-BS-Copper Network Instance-UC-MDF |
|
| 23003 |
2:-IM |
35 :-SOL-IM-BS-Copper Network Instance-UC-DC |
|
WCT |
N |
6.2.7.2. SOL-IM-BS-Copper Network Instance-UC-DC |
|
| 23003 |
2:-IM |
26 :-Resource Order Management |
|
WCT |
F |
5.4. Resource Order Management |
|
| 23003 |
2:-IM |
27 :-Service Inventory Management |
|
WCT |
F |
5.5. Service Inventory Management |
|
| 23003 |
2:-IM |
24 :-SOL-IM-FC-IP Address Management |
|
WCT |
N |
5.3.3.5.1. SOL-IM-FC-IP Address Management |
|
| 23003 |
2:-IM |
25 :-SOL-IM-FC-Resource Log Management |
|
WCT |
F |
5.3.6. SOL-IM-FC-Resource Log Management |
|
| 23003 |
2:-IM |
22 :-SOL-IM-FC-Cable Management |
|
WCT |
N |
5.3.3.3. SOL-IM-FC-Cable Management |
|
| 23003 |
2:-IM |
23 :-SOL-IM-FC-Cable Management-UC-LIC |
|
WCT |
N |
5.3.3.3.4. SOL-IM-FC-Cable Management-UC-LIC, 5.3. |
|
| 23003 |
2:-IM |
20 :-SOL-IM-FC-Device Management-UC-Resource Replacement (Active Device (Card) Replace) |
|
WCT |
N |
5.3.3.2.9. SOL-IM-FC-Device Management-UC-Resource |
|
| 23003 |
2:-IM |
21 :-SOL-IM-FC-Device Management-UC-Resource Replacement (DSLAM) |
|
WCT |
P |
5.3.3.2.9. SOL-IM-FC-Device Management-UC-Resource |
|
| 23003 |
2:-IM |
18 :-SOL-IM-FC-Device Management-UC-Resource Replacement (Standalone Device (Device) Replace) |
|
WCT |
N |
5.3.3.2.9. SOL-IM-FC-Device Management-UC-Resource |
|
| 23003 |
2:-IM |
19 :-SOL-IM-FC-Device Management-UC-Resource Replacement (Active Device (Chassis) Replace) |
|
WCT |
N |
5.3.3.2.9. SOL-IM-FC-Device Management-UC-Resource |
|
| 23003 |
2:-IM |
16 :-SOL-IM-FC-Device Management-UC-Resource Replacement (Active Devie (Device) Replace) |
|
WCT |
N |
5.3.3.2.9. SOL-IM-FC-Device Management-UC-Resource |
|
| 23003 |
2:-IM |
17 :-SOL-IM-FC-Device Management-UC-Resource Replacement (Passive Device (Panel) Replace) |
|
WCT |
N |
5.3.3.2.9. SOL-IM-FC-Device Management-UC-Resource |
|
| 23003 |
2:-IM |
14 :-SOL-IM-FC-Device Management-UC-Import and Export (Bulk Modify) |
|
WCT |
N |
5.3.3.2.5. SOL-IM-FC-Device Management-UC-Import a |
|
| 23003 |
2:-IM |
15 :-SOL-IM-FC-Device Management-UC-Multidirectional Information View |
|
WCT |
N |
5.3.3.2.8. SOL-IM-FC-Device Management-UC-Multidir |
|
| 22307 |
1:-POMS to COPS |
1 :-Verify modify order flows to COPS for KYC |
Order should automatically land in COPS for verification |
PTCL |
P |
|
|
| 22307 |
2:-POMS to COPS |
1 :-Verify restore order flows to COPS for KYC |
Restore order should automatically land in COPS for verification |
PTCL |
P |
|
|
| 22307 |
3:-COPS Portal |
1 :-Verify new flag to differentiate order types |
System should display flag showing New Sale / Modify Order / Restore Order |
PTCL |
P |
|
|
| 22307 |
4:-COPS Portal |
1 :-Verify MRC field visibility |
MRC field should be visible and populated correctly |
PTCL |
N |
|
|
| 22307 |
5:-POMS Portal |
1 :-Verify service type field for modify/restore order |
Field should allow selection of Broadband or Smart TV |
PTCL |
N |
|
|
| 22307 |
6:-POMS Portal |
1 :-Verify no document upload required for modify/restore orders |
System should not require additional document upload |
PTCL |
N |
|
|
| 22307 |
7:-KYC Process |
1 :-Verify only KYC fields are editable in modify orders |
Only KYC related fields should be editable |
PTCL |
N |
|
|
| 20999 |
1:-Create Traffic Routing Rule – PTCL 1218 |
1 :-Verify user can create routing rule for PTCL 1218 |
Routing rule saved successfully |
ExpertFlow |
P |
|
|
| 20999 |
2:-Destination Zone Validation |
1 :-Verify source and destination zones cannot be same |
Source zone excluded from destination list |
ExpertFlow |
N |
|
|
| 20999 |
3:-Test Routing Logic by Calls |
1 :-Verify routing by making calls |
Calls routed based on defined percentage |
ExpertFlow |
N |
|
|
| 20999 |
4:-Traffic Routing Rule – Ufone 333 |
1 :-Verify routing rule for Ufone 333 |
Calls routed as per rule |
ExpertFlow |
N |
|
|
| 20999 |
5:-Test Logic for 333 Helpline |
1 :-Verify routing by making calls |
Calls routed based on defined percentage |
ExpertFlow |
N |
|
|
| 20999 |
6:-Zone-wise Routing – 0800 / 1217 / SME |
1 :-Verify zone-wise routing without region |
Zone-wise routing applied successfully |
ExpertFlow |
N |
|
|
| 22409 |
1:-Quality of Installation Survey through WhatsApp |
2 :-Verify Survey button visibility |
Survey button is visible |
PTCL |
P |
|
|
| 22409 |
1:-Quality of Installation Survey through WhatsApp |
1 :-CSR login with valid credentials |
Login successful, Dashboard displayed |
PTCL |
P |
|
|
| 22409 |
1:-Quality of Installation Survey through WhatsApp |
3 :-Select Quality of Installation survey |
Quality of Installation screen opens |
PTCL |
P |
|
|
| 22409 |
1:-Quality of Installation Survey through WhatsApp |
5 :-Enter mobile when PSTN not found |
Mobile field editable & accepted |
PTCL |
P |
|
|
| 22409 |
1:-Quality of Installation Survey through WhatsApp |
4 :-Fetch customer data with valid PSTN |
Customer name & mobile fetched |
PTCL |
P |
|
|
| 22409 |
1:-Quality of Installation Survey through WhatsApp |
7 :-Send survey via WhatsApp |
Survey sent successfully |
PTCL |
P |
|
|
| 22409 |
1:-Quality of Installation Survey through WhatsApp |
6 :-Verify WhatsApp default selection |
WhatsApp selected by default |
PTCL |
P |
|
|
| 22409 |
1:-Quality of Installation Survey through WhatsApp |
8 :-Send survey via SMS |
Survey sent via SMS |
PTCL |
P |
|
|
| 22409 |
1:-Quality of Installation Survey through WhatsApp |
9 :-Submit Quality of Installation survey |
Survey submitted successfully |
PTCL |
P |
|
|
| 22409 |
1:-Quality of Installation Survey through WhatsApp |
11 :-Prevent duplicate survey submission |
Survey not allowed again |
PTCL |
P |
|
|
| 22409 |
1:-Quality of Installation Survey through WhatsApp |
10 :-Remarks mandatory when No selected |
Error message shown |
PTCL |
P |
|
|
| 1212 |
1:-ss |
1 :-ss |
sss |
ExperFlow |
P |
|
|
| 22191 |
1:-Changes in e-Payment user management |
1 :-Login with valid credentials and OTP |
Login successful |
PTCL |
P |
Audit Requiremnt |
|
| 22191 |
1:-Changes in e-Payment user management |
2 :-Enter incorrect OTP |
Error: Invalid OTP |
PTCL |
P |
|
|
| 22191 |
1:-Changes in e-Payment user management |
4 :-Resend OTP within 60 seconds |
Resend blocked |
PTCL |
P |
|
|
| 22191 |
1:-Changes in e-Payment user management |
5 :-Resend OTP after 60 seconds |
New OTP sent |
PTCL |
P |
|
|
| 22191 |
1:-Changes in e-Payment user management |
3 :-OTP expired |
OTP expired message displayed |
PTCL |
P |
|
|
| 22191 |
1:-Changes in e-Payment user management |
9 :-OTP stored securely |
OTP hashed, not plain text |
PTCL |
P |
|
|
| 22191 |
1:-Changes in e-Payment user management |
10 :-OTP events logged |
OTP_SENT, SUCCESS, FAILURE recorded |
PTCL |
P |
|
|
| 22191 |
1:-Changes in e-Payment user management |
8 :-Successful login |
Email/SMS alert sent |
PTCL |
P |
|
|
| 22191 |
1:-Changes in e-Payment user management |
6 :-Enter wrong OTP 5 times |
OTP blocked |
PTCL |
P |
|
|
| 22191 |
1:-Changes in e-Payment user management |
7 :-Login from two devices |
Session A invalidated |
PTCL |
P |
|
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
61 :-xDSL to GPON migration Order > GPON > Create an order with promo, where ports are available and move order till WFRA in Maximo. Revise the order in Siebel with promo, where spare ports are available in Maximo and Auto Eligibility shall return FDH value and shall call the backend system for Promo Eligibility check. |
|
IBM |
P |
|
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
48 :-New Order > GPON > Create an order with promo, where no spare ports for available FAT/NAP are available. Eligibility process should not return the FDH and display updated error prompt |
|
IBM |
P |
|
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
49 :-New Order > GPON > Create an order with promo, where spare ports are available. Auto Eligibility shall return FDH value and shall call the backend system for Promo Eligibility check and shall follow the feasibility process and so on accordingly. |
|
IBM |
P |
|
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
50 :-Restore Order > GPON > Create an order with promo, where no spare ports for available FAT/NAP are available. Eligibility process should not return the FDH and display updated error prompt |
|
IBM |
P |
|
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
51 :-Restore Order > GPON > Create an order with promo, where spare ports are available. Auto Eligibility shall return FDH value and shall call the backend system for Promo Eligibility check and shall follow the feasibility process and so on accordingly. |
|
IBM |
P |
|
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
52 :-New Migration Order > xDSL to GPON > Create a New Order with promo, where no spare ports for available FAT/NAP are available. Eligibility process should not return the FDH and display updated error prompt |
|
IBM |
P |
|
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
53 :-New Migration Order > xDSL to GPON > Create a New Order with promo, where spare ports are available. Auto Eligibility shall return FDH value and shall call the backend system for Promo Eligibility check and shall follow the feasibility process and so on accordingly. |
|
IBM |
P |
|
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
54 :-New Order > GPON > Create an order with promo, where ports are available and move order till WFRA in Maximo. Mark order as Not Feasible in Maximo, and then “Proceed” from Siebel with promo, where no spare ports for available FAT/NAP are available. Eligibility process should not return the FDH and display updated error prompt. |
|
IBM |
F |
|
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
55 :-New Order > GPON > Create an order with promo, where ports are available and move order till WFRA in Maximo. Mark order as Not Feasible in Maximo, and then “Proceed” from Siebel with promo, where spare ports of FAT/NAP are available in Maximo. Auto Eligibility shall return FDH value and shall call the backend system for Promo Eligibility check. |
|
IBM |
P |
|
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
56 :-New Order > GPON > Create an order with promo, where ports are available and move order till WFRA in Maximo. Revise the order in Siebel with promo, where no spare ports for available FAT/NAP are available. Eligibility process should not return the FDH and display updated error prompt |
|
IBM |
P |
|
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
57 :-New Order > GPON > Create an order with promo, where ports are available and move order till WFRA in Maximo. Revise the order in Siebel with promo, where spare ports are available in Maximo. Auto Eligibility shall return FDH value and shall call the backend system for Promo Eligibility check |
|
IBM |
P |
|
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
58 :-Restore Order > GPON > Create a Restore order with promo, where ports are available and move order till WFRA in Maximo. Revise the order in Siebel with promo, where no spare ports for available FAT/NAP are available. Eligibility process should not return the FDH and display updated error prompt |
|
IBM |
P |
|
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
59 :-Restore Order > GPON > Create a Restore order with promo, where ports are available and move order till WFRA in Maximo. Revise the order in Siebel with promo, where spare ports are available in Maximo and Auto Eligibility shall return FDH value and shall call the backend system for Promo Eligibility check. |
|
IBM |
P |
|
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
60 :-xDSL to GPON migration Order > GPON > Create an order with promo, where ports are available and move order till WFRA in Maximo. Revise the order in Siebel with promo, where no spare ports for available FAT/NAP are available. Eligibility process should not return the FDH and display updated error prompt |
|
IBM |
N |
|
|
| 15942 |
1:-Advance Billling 2 |
61 :-Same Above |
display |
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
60 :-Check message sent by creating Migration xDSL to GPON Conversion (GPON New Connection)
? Order Type: New Order
? Sub Type / Detail: xDSL to GPON Conversion Order
? Nature of Billing: Postpaid
? Migration Flag: Y
? Order Status: Completed |
|
IBM |
P |
3.3.1.2 Migration xDSL to GPON Conversion (GPON Ne |
|
| 15942 |
1:-Advance Billing2 |
48 :-Email on order completion: Dear Customer, we would like to inform you that starting from #DATE#, we will be implementing an advance billing cycle. Your upcoming bill will now include charges for next month, plus complete bill of the current month. If you have any questions or require further assistance, please call at 1218. |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
59 :-Same Above |
|
IBM |
P |
3.3.1.2 Migration xDSL to GPON Conversion (GPON Ne |
|
| 15942 |
1:-Advance Billing2 |
58 :-Check message sent by creating Migration xDSL to GPON Conversion (GPON New Connection)
? Order Type: New Order
? Sub Type / Detail: xDSL to GPON Conversion Order
? Nature of Billing: Postpaid
? Migration Flag: Y
? Order Status: Completed |
|
IBM |
P |
3.3.1.2 Migration xDSL to GPON Conversion (GPON Ne |
|
| 15942 |
1:-Advance Billing2 |
57 :-Same Above |
|
IBM |
P |
3.3.1.2 Migration xDSL to GPON Conversion (GPON Ne |
|
| 15942 |
1:-Advance Billing2 |
56 :-Check message sent by creating Migration xDSL to GPON Conversion (GPON New Connection)
? Order Type: New Order
? Sub Type / Detail: xDSL to GPON Conversion Order
? Nature of Billing: Postpaid
? Migration Flag: Y
? Order Status: Created |
|
IBM |
P |
3.3.1.2 Migration xDSL to GPON Conversion (GPON Ne |
|
| 15942 |
1:-Advance Billing2 |
55 :-Same Above |
|
IBM |
P |
3.3.1.2 Migration xDSL to GPON Conversion (GPON Ne |
|
| 15942 |
1:-Advance Billing2 |
54 :-Check message sent by creating Migration xDSL to GPON Conversion (GPON New Connection)
? Order Type: New Order
? Sub Type / Detail: xDSL to GPON Conversion Order
? Nature of Billing: Advance
? Migration Flag: Y
? Order Status: Created |
|
IBM |
P |
3.3.1.2 Migration xDSL to GPON Conversion (GPON Ne |
|
| 15942 |
1:-Advance Billing2 |
53 :-Dear Customer, we’ve received your request against Order no. (Order #) for migration from DSL to Fiber. Your existing DSL connection will soon be deactivated.
All pending dues will be carried forward to the upcoming bill. For any support or assistance, please contact us at 1218. |
|
IBM |
P |
3.3.1.1 Migration xDSL to GPON Conversion (xDSL Te |
|
| 15942 |
1:-Advance Billing2 |
52 :-Check message sent by creating Migration xDSL to GPON Conversion (xDSL Termination)
? Order Type: Terminate Order
? Sub Type / Detail: xDSL to GPON Conversion Order
? Nature of Billing: postpaid
? Migration Flag: Y
? Order Status: Complete
use linked order as above to complete the flow
Dear [Customer Name], your DSL to Flash Fiber migration request against [Order #] is received. Flash Fiber will activate soon after your DSL connection is deactivated. All pending dues will be carried forward to the upcoming bill. Call 1218 for more details! |
|
IBM |
P |
3.3.1.1 Migration xDSL to GPON Conversion (xDSL Te |
|
| 15942 |
1:-Advance Billing2 |
51 :-Dear Customer, we’ve received your request against Order no. (Order #) for migration from DSL to Fiber. Your existing DSL connection will soon be deactivated.
All pending dues will be carried forward to the upcoming bill. For any support or assistance, please contact us at 1218. |
|
IBM |
P |
3.3.1.1 Migration xDSL to GPON Conversion (xDSL Te |
|
| 15942 |
1:-Advance Billing2 |
50 :-Check message sent by creating Migration xDSL to GPON Conversion (xDSL Termination)
? Order Type: Terminate Order
? Sub Type / Detail: xDSL to GPON Conversion Order
? Nature of Billing: Advance
? Migration Flag: Y
? Order Status: Complete
use linked order as above to complete the flow
Dear [Customer Name], your DSL to Flash Fiber migration request against [Order #] is received. Flash Fiber will activate soon after your DSL connection is deactivated. All pending dues will be carried forward to the upcoming bill. Call 1218 for more details! |
|
IBM |
P |
3.3.1.1 Migration xDSL to GPON Conversion (xDSL Te |
|
| 15942 |
1:-Advance Billing2 |
49 :-Nature of billing is changed but Advance billing packages/VAS and DS are not selected.
When User change the nature of Billing from Post to Adv then only ADV Pakcaged should be slectable |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
47 :-SMS on order completion: Dear #CUSTNAME#, starting #DATE#, we’re shifting to an advance billing cycle. Your next bill will include charges for next month, plus complete bill of the current month. |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
43 :-Instant |
|
IBM |
P |
3.3.1 Changing the Nature of Billing |
|
| 15942 |
1:-Advance Billing2 |
44 :-First of Next month |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
45 :-First of next month is role base function. |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
46 :-System shall force to change the billing |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
36 :-One by One SR is locked or not
In case of Multiple TV Devices , separate SR should be creatd |
|
IBM |
P |
Multi IPTV BOX Return Case |
|
| 15942 |
1:-Advance Billing2 |
35 :-Retry API case |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
37 :-Configurable Charges for all above use cases of Return STB/ATV |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
38 :-Verify if it is allowed to Set the Commercial Name for a Package (for IT Ops team) |
|
IBM |
P |
3.3 Event Base Communication |
|
| 15942 |
1:-Advance Billing2 |
39 :-SMS text is configurable (Static text) |
|
IBM |
P |
Configurable SMS/Email/WhatsApp for postpaid and A |
|
| 15942 |
1:-Advance Billing2 |
40 :-Email text is configurable (Static text) |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
41 :-WhatsApp text is configurable (Static text) |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
42 :-WhatsApp Communication Enable/Disable |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
30 :-Create Admin SR |
|
IBM |
P |
General Data validity |
|
| 15942 |
1:-Advance Billing2 |
31 :-Drop down menu options available |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
34 :-SR is Open/Pending
SR will keep open once CBS API send failure |
|
IBM |
P |
API Un-successful Response |
|
| 15942 |
1:-Advance Billing2 |
33 :-SR is closed
SR will be created in Siebel
CBS will send Response via API with charges
Once successful response received from CBS , SR will be closed on Siebel |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
32 :-Amount to be adjusted in Next bill |
|
IBM |
P |
API successful Response |
|
| 15942 |
1:-Advance Billing2 |
17 :-Create an SR to verify Return ATV (Return STB/ATV with remote and charger) for GPON. Verify response and charges |
|
IBM |
P |
Customer status Active- Advance Billing- GPON- ATV |
|
| 15942 |
1:-Advance Billing2 |
18 :-Create an SR to verify Return STB (Return STB/ATV without any accessories) for GPON. Verify response and charges |
|
IBM |
P |
Customer status Active- Postpaid- STB returned wit |
|
| 15942 |
1:-Advance Billing2 |
19 :-Create an SR to verify Return STB (Return STB/ATV without any accessories) for GPON. Verify response and charges |
|
IBM |
P |
Customer status Active- Advance Billing- STB retur |
|
| 15942 |
1:-Advance Billing2 |
22 :-Create an SR to verify Return ATV (Return STB/ATV with remote and charger) for Copper. Verify response and charges |
|
IBM |
P |
Customer status Active- Postpaid- Copper- STB-retu |
|
| 15942 |
1:-Advance Billing2 |
23 :-Create an SR to verify Return ATV (Return STB/ATV with remote and charger) for Copper. Verify response and charges |
|
IBM |
P |
Customer status Active- Advance Billing- Copper- A |
|
| 15942 |
1:-Advance Billing2 |
21 :-Create an SR to verify Return STB (Return STB/ATV with all accessories) for Copper. Verify response and charges |
|
IBM |
P |
Customer status Active- Advance Billing- Copper - |
|
| 15942 |
1:-Advance Billing2 |
20 :-Create an SR to verify Return STB (Return STB/ATV with all accessories) for Copper. Verify response and charges |
|
IBM |
P |
Customer status Active- Postpaid- Copper- STB retu |
|
| 15942 |
1:-Advance Billing2 |
26 :-Create an SR to verify Return STB (Return STB/ATV with all accessories) for Inactive GPON. Verify response and charges |
|
IBM |
P |
Customer status In-Active- Postpaid- GPON- STB ret |
|
| 15942 |
1:-Advance Billing2 |
25 :-Create an SR to verify Return STB (Return STB/ATV without any accessories) for Copper. Verify response and charges |
|
IBM |
P |
Customer status Active- Advance Billing- Copper- S |
|
| 15942 |
1:-Advance Billing2 |
24 :-Create an SR to verify Return STB (Return STB/ATV without any accessories) for Copper. Verify response and charges |
|
IBM |
P |
Customer status Active- Postpaid- Copper - STB ret |
|
| 15942 |
1:-Advance Billing2 |
27 :-Create an SR to verify Return STB (Return STB/ATV with all accessories) for Inactive GPON. Verify response and charges |
|
IBM |
P |
Customer status In-Active- Advance Billing- GPON - |
|
| 15942 |
1:-Advance Billing2 |
29 :-Create an SR to verify Return STB (Return STB/ATV with all accessories) for Inactive Copper. Verify response and charges |
|
IBM |
P |
Customer status In-Active- Advance Billing- Copper |
|
| 15942 |
1:-Advance Billing2 |
28 :-Create an SR to verify Return STB (Return STB/ATV with all accessories) for Inactive Copper. Verify response and charges |
|
IBM |
P |
Customer status In-Active- Postpaid- Copper- STB r |
|
| 15942 |
1:-Advance Billing2 |
62 :-Check message sent by creating Postpaid Change of Internet Price Plan (Upgrade)
? Order Type: Modify Order
? Sub Type / Detail: Change of Internet Price Plan (upgrade)
? Nature of Billing: Postpaid
? Order Status: Complete |
|
IBM |
P |
3.3.1.3.1 For Postpaid Change of Internet Price Pl |
|
| 15942 |
1:-Advance Billing2 |
63 :-Same Above |
|
IBM |
P |
3.3.1.3.1 For Postpaid Change of Internet Price Pl |
|
| 15942 |
1:-Advance Billing2 |
64 :-Check message sent by creating Postpaid Change of Internet Price Plan (Downgrade)
? Order Type: Modify Order
? Sub Type / Detail: Change of Internet Price Plan (downgrade)
? Nature of Billing: Postpaid
? Order Status: Complete |
|
IBM |
P |
3.3.1.3.1 For Postpaid Change of Internet Price Pl |
|
| 15942 |
1:-Advance Billing2 |
65 :-Same Above |
|
IBM |
P |
3.3.1.3.1 For Postpaid Change of Internet Price Pl |
|
| 15942 |
1:-Advance Billing2 |
66 :-Check message sent by creating Advance Change of Internet Price Plan (Upgrade)
? Order Type: Modify Order
? Sub Type / Detail: Change of Internet Price Plan (upgrade)
? Nature of Billing: Advance
? Order Status: Complete |
|
IBM |
P |
3.3.1.3.2 For Advance Change of Internet Price Pla |
|
| 15942 |
1:-Advance Billing2 |
67 :-Same Above |
|
IBM |
P |
3.3.1.3.2 For Advance Change of Internet Price Pla |
|
| 15942 |
1:-Advance Billing2 |
68 :-Check message sent by creating Advance Change of Internet Price Plan (Downgrade)
? Order Type: Modify Order
? Sub Type / Detail: Change of Internet Price Plan (Downgrade)
? Nature of Billing: Advance
? Order Status: Complete |
|
IBM |
P |
3.3.1.3.2 For Advance Change of Internet Price Pla |
|
| 15942 |
1:-Advance Billing2 |
69 :-Same Above |
|
IBM |
P |
3.3.1.3.2 For Advance Change of Internet Price Pla |
|
| 15942 |
1:-Advance Billing2 |
70 :-Check message sent by creating New Order for Bolt-On Activation - Advance
? Order Type : New Order
? Sub Type / Detail: Bolt-On Addition (Action-Add)
? Nature of Billing: Advance
? Order Status: Complete |
|
IBM |
P |
3.3.1.4.1 Bolt-On Activation with New Order - Adva |
|
| 15942 |
1:-Advance Billing2 |
71 :-Same Above |
|
IBM |
P |
3.3.1.4.1 Bolt-On Activation with New Order - Adva |
|
| 15942 |
1:-Advance Billing2 |
72 :-Check message sent by creating New Order for Bolt-On Activation - Postpaid
? Order Type : New Order
? Sub Type / Detail: Bolt-On Addition (Action-Add)
? Nature of Billing: Postpaid
? Order Status: Complete |
|
IBM |
P |
3.3.1.4.1 Bolt-On Activation with New Order - Post |
|
| 15942 |
1:-Advance Billing2 |
73 :-Same Above |
|
IBM |
P |
3.3.1.4.1 Bolt-On Activation with New Order - Post |
|
| 15942 |
1:-Advance Billing2 |
74 :-Check message sent by creating Modify Order for Bolt-On Activation - Advance
? Order Type : Modify Order
? Sub Type / Detail: Bolt-On Addition (Action-Add)
? Nature of Billing: Advance
? Order Status: Complete |
|
IBM |
P |
3.3.1.4.1 Bolt-On Activation with Modify Order - A |
|
| 15942 |
1:-Advance Billing2 |
75 :-Same Above |
|
IBM |
P |
3.3.1.4.1 Bolt-On Activation with Modify Order - A |
|
| 15942 |
1:-Advance Billing2 |
76 :-Check message sent by creating Modify Order for Bolt-On Activation - Postpaid
? Order Type : Modify Order
? Sub Type / Detail: Bolt-On Addition (Action-Add)
? Nature of Billing: Postpaid
? Order Status: Complete |
|
IBM |
P |
3.3.1.4.1 Bolt-On Activation with Modify Order - P |
|
| 15942 |
1:-Advance Billing2 |
77 :-Same Above |
|
IBM |
P |
3.3.1.4.1 Bolt-On Activation with Modify Order - P |
|
| 15942 |
1:-Advance Billing2 |
78 :-Check message sent by creating Restore Order for Bolt-On Activation - Advance
? Order Type : Restore Order
? Sub Type / Detail: Bolt-On Addition (Action-Add)
? Nature of Billing: Advance
? Order Status: Complete |
|
IBM |
P |
3.3.1.4.1 Bolt-On Activation with Restore Order - |
|
| 15942 |
1:-Advance Billing2 |
79 :-Same Above |
|
IBM |
P |
3.3.1.4.1 Bolt-On Activation with Restore Order - |
|
| 15942 |
1:-Advance Billing2 |
80 :-Check message sent by creating Restore Order for Bolt-On Activation - Postpaid
? Order Type : Restore Order
? Sub Type / Detail: Bolt-On Addition (Action-Add)
? Nature of Billing: Postpaid
? Order Status: Complete |
|
IBM |
P |
3.3.1.4.1 Bolt-On Activation with Restore Order - |
|
| 15942 |
1:-Advance Billing2 |
81 :-Same Above |
|
IBM |
P |
3.3.1.4.1 Bolt-On Activation with Restore Order - |
|
| 15942 |
1:-Advance Billing2 |
82 :-Check message sent by creating New Order for Bolt-On Deactivation - Advance
? Order Type : New Order
? Sub Type / Detail: Bolt-On Deletion (Action-Delete)
? Nature of Billing: Advance
? Order Status: Complete |
|
IBM |
P |
3.3.1.4.2 Bolt-On Deactivation |
|
| 15942 |
1:-Advance Billing2 |
83 :-Check message sent by creating New Order for Bolt-On Deactivation - Postpaid
? Order Type : New Order
? Sub Type / Detail: Bolt-On Deletion (Action-Delete)
? Nature of Billing: Postpaid
? Order Status: Complete |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
84 :-Check message sent by creating Modify Order for Bolt-On Deactivation - Advance
? Order Type : Modify Order
? Sub Type / Detail: Bolt-On Deletion (Action-Delete)
? Nature of Billing: Advance
? Order Status: Complete |
|
IBM |
P |
3.3.1.4.2 Bolt-On Deactivation - Modify Order- Adv |
|
| 15942 |
1:-Advance Billing2 |
85 :-Same Above |
|
IBM |
P |
3.3.1.4.2 Bolt-On Deactivation - Modify Order- Adv |
|
| 15942 |
1:-Advance Billing2 |
86 :-Check message sent by creating Modify Order for Bolt-On Deactivation - Postpaid
? Order Type : Modify Order
? Sub Type / Detail: Bolt-On Deletion (Action-Delete)
? Nature of Billing: Postpaid
? Order Status: Complete |
|
IBM |
P |
3.3.1.4.2 Bolt-On Deactivation - Modify Order- Pos |
|
| 15942 |
1:-Advance Billing2 |
87 :-Same Above |
|
IBM |
P |
3.3.1.4.2 Bolt-On Deactivation - Modify Order- Pos |
|
| 15942 |
1:-Advance Billing2 |
88 :-Check message sent by creating Restore Order for Bolt-On Deactivation - Advance
? Order Type : Restore Order
? Sub Type / Detail: Bolt-On Deletion (Action-Delete)
? Nature of Billing: Advance
? Order Status: Complete |
|
IBM |
P |
3.3.1.4.2 Bolt-On Deactivation - Restore Order- Ad |
|
| 15942 |
1:-Advance Billing2 |
89 :-Same Above |
|
IBM |
P |
3.3.1.4.2 Bolt-On Deactivation - Restore Order- Ad |
|
| 15942 |
1:-Advance Billing2 |
90 :-Check message sent by creating Restore Order for Bolt-On Deactivation - Postpaid
? Order Type : Restore Order
? Sub Type / Detail: Bolt-On Deletion (Action-Delete)
? Nature of Billing: Postpaid
? Order Status: Complete |
|
IBM |
P |
3.3.1.4.2 Bolt-On Deactivation - Restore Order- Po |
|
| 15942 |
1:-Advance Billing2 |
91 :-Same Above |
|
IBM |
P |
3.3.1.4.2 Bolt-On Deactivation - Restore Order- Po |
|
| 15942 |
1:-Advance Billing2 |
92 :-Bolt-on Activation SMS for FOC and Limited validity (validity less than 10 years) |
|
IBM |
P |
Bolt-on variations SMS testing (FOC, Paid, Tempora |
|
| 15942 |
1:-Advance Billing2 |
93 :-Bolt-on Activation SMS for FOC and Un-Limited validity (10 years) |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
94 :-Bolt-on Activation SMS for Paid and Limited validity (validity less than 10 years) |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
95 :-Bolt-on Activation SMS for Paid and Un-Limited validity (10 years) |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
96 :-Bolt-on Deactivation SMS for FOC and Limited validity (validity less than 10 years) |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
97 :-Bolt-on Deactivation SMS for FOC and Un-Limited validity (10 years) |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
98 :-Bolt-on Deactivation SMS for Paid and Limited validity (validity less than 10 years) |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
99 :-Bolt-on Deactivation SMS for Paid and Un-Limited validity (10 years) |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
100 :-Bolt-on Expiry SMS for FOC and Limited validity (validity less than 10 years) |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
101 :-Bolt-on Expiry SMS for FOC and Un-Limited validity (10 years) |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
102 :-Bolt-on Expiry SMS for Paid and Limited validity (validity less than 10 years) |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
103 :-Bolt-on Expiry SMS for Paid and Un-Limited validity (10 years) |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
104 :-Check message sent by creating New Order for VAS Activation - Advance
? Order Type : New Order
? Sub Type / Detail: VAS Addition (Action-Add)
? Nature of Billing: Advance
? Order Status: Complete |
|
IBM |
P |
3.3.1.5 VAS Activation- New Order - Advance Billin |
|
| 15942 |
1:-Advance Billing2 |
105 :-Same Above |
|
IBM |
P |
3.3.1.5 VAS Activation- New Order - Advance Billin |
|
| 15942 |
1:-Advance Billing2 |
106 :-Check message sent by creating New Order for VAS Activation - Postpaid
? Order Type : New Order
? Sub Type / Detail: VAS Addition (Action-Add)
? Nature of Billing: Postpaid
? Order Status: Complete |
|
IBM |
P |
3.3.1.5 VAS Activation- New Order - Postpaid- SMS |
|
| 15942 |
1:-Advance Billing2 |
107 :-Same Above |
|
IBM |
P |
3.3.1.5 VAS Activation- New Order - Postpaid- Emai |
|
| 15942 |
1:-Advance Billing2 |
108 :-Check message sent by creating Modify Order for VAS Activation - Advance
? Order Type : Modify Order
? Sub Type / Detail: VAS Addition (Action-Add)
? Nature of Billing: Advance
? Order Status: Complete |
|
IBM |
P |
3.3.1.5 VAS Activation- Modify Order - Advance Bil |
|
| 15942 |
1:-Advance Billing2 |
109 :-Same Above |
|
IBM |
P |
3.3.1.5 VAS Activation- Modify Order - Advance Bil |
|
| 15942 |
1:-Advance Billing2 |
110 :-Check message sent by creating Modify Order for VAS Activation - Postpaid
? Order Type : Modify Order
? Sub Type / Detail: VAS Addition (Action-Add)
? Nature of Billing: Postpaid
? Order Status: Complete |
|
IBM |
P |
3.3.1.5 VAS Activation- Modify Order - Postpaid- S |
|
| 15942 |
1:-Advance Billing2 |
111 :-Same Above |
|
IBM |
P |
3.3.1.5 VAS Activation- Modify Order - Postpaid- E |
|
| 15942 |
1:-Advance Billing2 |
112 :-Check message sent by creating Restore Order for VAS Activation - Advance
? Order Type : Restore Order
? Sub Type / Detail: VAS Addition (Action-Add)
? Nature of Billing: Advance
? Order Status: Complete |
|
IBM |
P |
3.3.1.5 VAS Activation- Restore Order - Advance Bi |
|
| 15942 |
1:-Advance Billing2 |
113 :-Same Above |
|
IBM |
P |
3.3.1.5 VAS Activation- Restore Order - Advance Bi |
|
| 15942 |
1:-Advance Billing2 |
114 :-Check message sent by creating Restore Order for VAS Activation - Postpaid
? Order Type : Restore Order
? Sub Type / Detail: VAS Addition (Action-Add)
? Nature of Billing: Postpaid
? Order Status: Complete |
|
IBM |
P |
3.3.1.5 VAS Activation- Restore Order - Postpaid- |
|
| 15942 |
1:-Advance Billing2 |
115 :-Same Above |
|
IBM |
P |
3.3.1.5 VAS Activation- Restore Order - Postpaid- |
|
| 15942 |
1:-Advance Billing2 |
116 :-Create Restore Order with Copper triple play where at least one of the IPTV is restored, check if application enforces user to select CPE Type (Equipment) and Payment Mode(onetime / installment) for restored IPTV. Set the Payment mode as One Time and process the order. Verify if Siebel sends IPTV Charges to CBS using existing CRM-CBS integration. |
|
IBM |
P |
3.4 STB Charges on Restoration - Postpaid - Copper |
|
| 15942 |
1:-Advance Billling 2 |
117 :-Create Restore Order with Copper triple play where at least one of the IPTV is restored, check if application enforces user to select CPE Type (Equipment) and Payment Mode(onetime / installment) for restored IPTV. Set the Payment mode as One Time and process the order. Verify if Siebel sends IPTV Charges to CBS using existing CRM-CBS integration. |
display |
IBM |
P |
3.4 ATV Charges on Restoration - Advance Billing - |
|
| 15942 |
1:-Advance Billing2 |
118 :-Create Restore Order with Copper triple play where at least one of the IPTV is restored, check if application enforces user to select CPE Type (Equipment) and Payment Mode(onetime / installment) for restored IPTV. Set the Payment mode as Installment and process the order. Verify if Siebel sends IPTV Charges to CBS using existing CRM-CBS integration. |
|
IBM |
P |
3.4 ATV Charges on Restoration - Postpaid - Copper |
|
| 15942 |
1:-Advance Billing2 |
119 :-Create Restore Order with Copper triple play where at least one of the IPTV is restored, check if application enforces user to select CPE Type (Equipment) and Payment Mode(onetime / installment) for restored IPTV. Set the Payment mode as Installment and process the order. Verify if Siebel sends IPTV Charges to CBS using existing CRM-CBS integration. |
|
IBM |
P |
3.4 STB Charges on Restoration - Advance Billing - |
|
| 15942 |
1:-Advance Billing2 |
120 :-Create Restore Order with GPON triple play where at least one of the IPTV is restored, check if application enforces user to select CPE Type (Equipment) and Payment Mode(onetime / installment) for restored IPTV. Set the Payment mode as One Time and process the order. Verify if Siebel sends IPTV Charges to CBS using existing CRM-CBS integration. |
|
IBM |
P |
3.4 ATV Charges on Restoration - Postpaid - GPON- |
|
| 15942 |
1:-Advance Billing2 |
121 :-Create Restore Order with GPON triple play where at least one of the IPTV is restored, check if application enforces user to select CPE Type (Equipment) and Payment Mode(onetime / installment) for restored IPTV. Set the Payment mode as One Time and process the order. Verify if Siebel sends IPTV Charges to CBS using existing CRM-CBS integration. |
|
IBM |
P |
3.4 STB Charges on Restoration - Advance Billing - |
|
| 15942 |
1:-Advance Billing2 |
122 :-Create Restore Order with GPON triple play where at least one of the IPTV is restored, check if application enforces user to select CPE Type (Equipment) and Payment Mode(onetime / installment) for restored IPTV. Set the Payment mode as Installment and process the order. Verify if Siebel sends IPTV Charges to CBS using existing CRM-CBS integration. |
|
IBM |
P |
3.4 STB Charges on Restoration - Postpaid - GPON- |
|
| 15942 |
1:-Advance Billing2 |
123 :-Create Restore Order with GPON triple play where at least one of the IPTV is restored, check if application enforces user to select CPE Type (Equipment) and Payment Mode(onetime / installment) for restored IPTV. Set the Payment mode as Installment and process the order. Verify if Siebel sends IPTV Charges to CBS using existing CRM-CBS integration. |
|
IBM |
P |
3.4 ATV Charges on Restoration - Advance Billing - |
|
| 15942 |
1:-Advance Billing2 |
124 :-Create a GPON triple play order with multiple IPTV STBs and paymet mode is one time and verify the tax calculator service. It should be able to calculate the prices and tax for STB products along with existing products. Verify the Payment step. |
|
IBM |
P |
3.5 Upfront Payment for STB |
|
| 15942 |
1:-Advance Billing2 |
125 :-Create a Copper triple play order with STB and payment mode is installment and verify the tax calculator service. It should be able to calculate the prices and tax for STB products along with existing products. Verify the Payment step. |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
126 :-Create a GPON triple play order with multiple IPTVs (1 with One time charges and Other with installment) with ATVs and verify the tax calculator service. It should be able to calculate the prices and tax for ATV products along with existing products. Verify the Payment step. |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
127 :-Create a Copper triple play order with ATV and verify the tax calculator service. It should be able to calculate the prices and tax for ATV products along with existing products. Verify the Payment step. |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
128 :-New order - triple play with multi IPTVs installed (payment mode is installment) 2 months STB installement charges should be charged |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
129 :-Process the migration using a billing account ID while ensuring that package mapping is defined for source and target products. Execute the procuedure and verify the changes in the assets and Nature of Billing from Siebel UI. |
|
IBM |
N |
3.6 Bulk migration from Postpaid to Advance |
|
| 15942 |
1:-Advance Billing2 |
130 :-Format alignment with BI
For Bulk Migration , share the Format that will be shared with Business to fill for bulk migration |
|
IBM |
P |
|
|
| 15942 |
1:- |
131 :-Few Services shall be migrated and few shall not be migratedCustomer has PP, DS, VAS Role base change from Pot to AdvCC user , will select the same VAS, DS, PP If CC agent do not select the same service Report will be extracted by Ops to differenciate it |
display user and vas |
IBM |
P |
Seemless MIigration Postpaid to Advance |
|
| 15942 |
1:- |
132 :-Validate IT procedure for applying remaining VASes services through jobOnce Siebel user shift customer from Postpaid to Advance and in case agent mitsakenly do not add any VAS that was previously enabled in postpaid.In this case there must be some Job to run and find out the missed VAS also and enable it on Advance customer |
display user and vas |
IBM |
P |
Seemless MIigration Postpaid to Advance |
|
| 15942 |
1:-Advance Billing2 |
133 :-For a Customer Owned IPTV STB Equipment Asset, click on "Get IPTV Equipment Info" and verify the status of IPTV Equipment |
|
IBM |
P |
3.7 Get IPTV Equipment Info |
|
| 15942 |
1:-Advance Billing2 |
134 :-For a PTCL Owned ATV Equipment Asset, click on "Get IPTV Equipment Info" and verify the status of IPTV Equipment |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
135 :-Create a Modify Order for shifting from Postpaid to Advance with user that has rights. Select "First of Next Month" as the option and submit the order. Verify if order is going to the new step and it is locked with no changes allowed. |
|
IBM |
P |
3.8 Postpaid to Advance Shift (Effective Date 1st |
|
| 15942 |
1:-Advance Billing2 |
136 :-Verify the Siebel job (backend) if the order is moved to next step once the effective date is achieved. |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
137 :-Create a Modify Order for shifting from Postpaid to Advance with user that has rights. Select "Immediate" as the option and complete Order till Billing. Verify from Billing if the status is set properly for Billing execution. |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
138 :-Create a Modify Order for shifting from Postpaid to Advance with user that does not have rights. Ensure that the default value "Immediate" is selected and not allowed to change. |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
139 :-SR shall be generated |
|
IBM |
P |
POSTPAID TO ADVANCE VIA SELF-CARE
WhatsApp |
|
| 15942 |
1:-Advance Billing2 |
140 :-SR shall be routed to correct ID |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
141 :-SR shall be generated |
|
IBM |
P |
POSTPAID TO ADVANCE VIA SELF-CARE - Website |
|
| 15942 |
1:-Advance Billing2 |
142 :-SR shall be routed to correct ID |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
143 :-SR shall be generated |
|
IBM |
P |
POSTPAID TO ADVANCE VIA SELF-CARE - UPTCL App |
|
| 15942 |
1:-Advance Billing2 |
144 :-SR shall be routed to correct ID |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
145 :-Purchase of Hardware, package upgrade, Bolt-on and Static IP |
|
IBM |
P |
UNBILLED SECTION EXTEND TO EXTERNAL CHANNELS (Post |
|
| 15942 |
1:-Advance Billing2 |
146 :-User is able to view Unbilled amount summary in agreed format |
|
IBM |
P |
UNBILLED SECTION EXTEND TO EXTERNAL CHANNELS (Post |
|
| 15942 |
1:-Advance Billing2 |
147 :-API Respnse time |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
148 :-User is able to Pay |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
149 :-User is able to view Unbilled amount summary in agreed format |
|
IBM |
P |
UNBILLED SECTION EXTEND TO EXTERNAL CHANNELS (Post |
|
| 15942 |
1:-Advance Billing2 |
150 :-API Respnse time |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
151 :-User is able to Pay |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
152 :-User is able to view Unbilled amount summary in agreed format |
|
IBM |
N |
UNBILLED SECTION EXTEND TO EXTERNAL CHANNELS (Post |
|
| 15942 |
1:-Advance Billing2 |
153 :-API Respnse time |
|
IBM |
N |
|
|
| 15942 |
1:-Advance Billing2 |
154 :-User is able to Pay |
|
IBM |
N |
|
|
| 15942 |
1:-Advance Billing2 |
155 :-User is able to view Unbilled amount summary in agreed format
CBS UI for Unbilled is required
IT P will share the screenshot of of CBS UI |
|
IBM |
P |
UNBILLED SECTION EXTEND TO EXTERNAL CHANNELS (Post |
|
| 15942 |
1:-Advance Billing2 |
156 :-Purchase of SHOQ, package downgrade, Bolt-on and Mobile Lite |
|
IBM |
P |
UNBILLED SECTION EXTEND TO EXTERNAL CHANNELS (Adva |
|
| 15942 |
1:-Advance Billing2 |
157 :-User is able to view Unbilled amount summary in agreed format |
|
IBM |
P |
WhatsApp |
|
| 15942 |
1:-Advance Billing2 |
158 :-API Respnse time |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
159 :-User is able to Pay |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
160 :-User is able to view Unbilled amount summary in agreed format |
|
IBM |
P |
Website |
|
| 15942 |
1:-Advance Billing2 |
161 :-API Respnse time |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
162 :-User is able to Pay |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
163 :-User is able to view Unbilled amount summary in agreed format |
|
IBM |
N |
UPTCL App |
|
| 15942 |
1:-Advance Billing2 |
164 :-API Respnse time |
|
IBM |
N |
|
|
| 15942 |
1:-Advance Billing2 |
165 :-User is able to Pay |
|
IBM |
N |
|
|
| 15942 |
1:-Advance Billing2 |
166 :-User is able to view Unbilled amount summary in agreed format |
|
IBM |
P |
CRM operator |
|
| 15942 |
1:-Advance Billing2 |
167 :-Bifurcation for advance/postpaid billing |
|
IBM |
P |
IVR |
|
| 15942 |
1:-Advance Billing2 |
168 :-portfolio update for bolt-ons and other redemption awards |
|
IBM |
P |
Loyalty App |
|
| 15942 |
1:-Advance Billing2 |
169 :-Shadow Portfolio replica packages |
|
IBM |
P |
One Window |
|
| 15942 |
1:-Advance Billing2 |
170 :-App Visibility / Flows and bills verfication, usage and CDRs, Package |
|
IBM |
P |
UPTCL |
|
| 15942 |
1:-Advance Billing2 |
171 :-Usage reflection on UPTCL App + Website |
|
IBM |
P |
UPTCL |
|
| 15942 |
1:-Advance Billing2 |
172 :-Shop display / order placement |
|
IBM |
P |
Website |
|
| 15942 |
1:-Advance Billing2 |
173 :-lead generation |
|
IBM |
P |
WhatsApp Flow |
|
| 15942 |
1:-Advance Billing2 |
174 :-All whatsapp flows to ensure customer type i.e postpaid or advance are identified at the start of their journeys and relevant offerings shown accordingly |
|
IBM |
P |
WhatsApp Flow |
|
| 15942 |
1:-Advance Billing2 |
175 :-If incorrect mapped product is being selected on whatsapp example advance user attempting to subscribe postpaid vas, then error should be returned to user |
|
IBM |
P |
WhatsApp Flow |
|
| 15942 |
1:-Advance Billing2 |
176 :-Billing month |
|
IBM |
P |
Bill Templete verifircation |
|
| 15942 |
1:-Advance Billing2 |
177 :-Due Date |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
178 :-Due Amount |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
179 :-Merged items (will be verified according to the agreement in email) |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
180 :-QR Code |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
181 :-QR Code lable |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
182 :-Front bill Ad left links |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
183 :-Front bill Ad right links |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
184 :-Backside bill Ad left links |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
185 :-Backside bill Ad right links |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
186 :-Payment channels clickable |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
187 :-Click here box pushed by Prism |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
188 :-Bill Line |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
189 :-Pro rated calculations |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
190 :-Segregation of months of all ine items in each quadrant (month shuld be visible agaonst the line items) |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
191 :-Migration from Copper (Postpaid) to Fiber (Advance) with installation charges and package change within same month on Fiber after 15 days of migration, along with FUP charges, Hardware Purchase, Bolt-on. Pro rate charges calculation and advance billing along with bill line items will be verified |
|
IBM |
P |
1 bill |
|
| 15942 |
1:-Advance Billing2 |
192 :-Migration from Copper (Advance) to Fiber (Advance) with installation charges and package change within same month on Fiber after 15 days of migration, along with Variable charges, Hardware Purchase, Static IP. Pro rate charges calculation and advance billing along with bill line items will be verified |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
193 :-New installation on Copper (Advance) with installation and Migrate to Fiber (Advance) with installation charges within same month, Charge extra Drop wire, IPTV Remote Control. Merged line items will be verified in this case. |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
194 :-New order - triple play with multi IPTVs installed (payment mode is installment) 2 months STB installement charges should be visible on invoice Summary Page |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
195 :-Segregation of months of all ine items in each quadrant (month shuld be visible agaonst the line items) |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
196 :-Extra Usage-FUP need add billing month as the prefix value, like <Apr Extra Usage-FUP > |
|
IBM |
P |
FUP Charges verificaiton on invoice |
|
| 15942 |
1:-Advance Billing2 |
197 :-Check 2 months FUP value on invice in case of xDSL to FTTH and potpaid to Advance shifting. |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
198 :-New Billing cycle is created for Advance billing |
|
IBM |
P |
Billing Cycle Creation |
|
| 15942 |
1:-Advance Billing2 |
199 :-Bill Run date is same as postpaid |
|
IBM |
P |
Bill Run Date |
|
| 15942 |
1:-Advance Billing2 |
200 :-Due date is different from postpaid |
|
IBM |
P |
Due Date |
|
| 15942 |
1:-Advance Billing2 |
201 :-TOS date is different from postpaid |
|
IBM |
P |
TOS |
|
| 15942 |
1:-Advance Billing2 |
202 :-Customer is Tos automatically upon the configured date |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
203 :-TOS notification to customer |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
204 :-Customer Notification on TOS |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
205 :-Resume from TOS on payment |
|
IBM |
P |
Resume |
|
| 15942 |
1:-Advance Billing2 |
206 :-All payment rules are same as postpaid |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
207 :-Customet Notification on Resume |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
208 :-POS date is different from postpaid |
|
IBM |
P |
POS |
|
| 15942 |
1:-Advance Billing2 |
209 :-Customer is Pos (CMP) automatically upon the configured date |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
210 :-OCR Notifications |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
211 :-CMP Notifications |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
212 :-advance billing to remain on one new bill cycle |
|
IBM |
P |
Rules validation for new/ restore orders to limit |
|
| 15942 |
1:-Advance Billing2 |
213 :-postpaid customer will remain on old bill cycle |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
214 :-Tagging of bill cycle based on “nature of billing” will be automatic. |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
215 :-Without changing billing cycle, nature of billing change is not allowed. |
|
IBM |
P |
For Migration and modify order: postpaid to advanc |
|
| 15942 |
1:-Advance Billing2 |
216 :-Tagging of bill cycle shall be automated for migration and modify order (postpaid to Advance migration) |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
217 :-Any other order type which triggers change of “nature of billing”, bill cycle should automatically be converted. |
|
IBM |
P |
Any other order type which triggers change of “nat |
|
| 15942 |
1:-Advance Billing2 |
218 :-One bill Capability |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
219 :-Creation of new Campaigns in CMS |
|
IBM |
P |
The CVM SMS triggers for advance billing |
|
| 15942 |
1:-Advance Billing2 |
220 :-Integration with BI |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
221 :-Triggering Confirmation |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
222 :-SMS |
|
IBM |
P |
Bill intimation and Due Amount |
|
| 15942 |
1:-Advance Billling 2 |
223 :-Email |
display |
IBM |
P |
3.4 ATV Charges on Restoration - Advance Billing - |
|
| 15942 |
1:-Advance Billing2 |
224 :-WhatsApp |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
225 :-UPTCL App |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
226 :-Dbill |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
227 :-Customer Portal (website) |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
228 :-Test Case |
|
IBM |
P |
Payment Reminder 1 |
|
| 15942 |
1:-Advance Billing2 |
229 :-Test Case |
|
IBM |
P |
Payment Reminder 2 |
|
| 15942 |
1:-Advance Billing2 |
230 :-Test Case |
|
IBM |
P |
Payment Reminder 3 |
|
| 15942 |
1:-Advance Billing2 |
231 :-Upfront Charges report |
|
IBM |
N |
Reports Verifircation |
|
| 15942 |
1:-Advance Billing2 |
232 :-Commission report |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
233 :-Pre and post bill registers |
|
IBM |
N |
|
|
| 15942 |
1:-Advance Billing2 |
234 :-finance reports |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
235 :-Speed |
|
IBM |
P |
Bolt-on rules to be verified |
|
| 15942 |
1:-Advance Billing2 |
236 :-Removal on Expiry |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
237 :-Speed Revert After removal of Speed Bolt-on |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
238 :-Base PPID Speed 20Mbps, Bolt-on is 50Mbps and upgraded Base speed to 50Mbps, Bolt-on should be removed. |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
239 :-Base PPID Speed 20Mbps, Bolt-on is 50Mbps and upgrade Bolt-on to 100Mbops , 50Mbps Bolt-on should be removed. |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
240 :-Postpaid customer shall get postpaid bolt-on |
|
IBM |
P |
Bolt-on Subscription through external channel |
|
| 15942 |
1:-Advance Billing2 |
241 :-Advance Billing customer shall get Advance billing bolt-on |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
242 :-Nature of billing shall be checked by system (no human intervention) |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
243 :-Prorate/Full month |
|
IBM |
P |
Charging rule verification |
|
| 15942 |
1:-Advance Billing2 |
244 :-Instant/Next month |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
245 :-Separate rules for separate services |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
246 :-DS is not included because it is charged on monthly basis |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
247 :-2.1.3 RPC/upgrade/downgrade/activation/deletion Rules: |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
248 :-Shoq : To be charged for complete month or pro-rated regardless of activation or deactivation date |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
249 :-IPTV : To be charged for complete month or pro-rated regardless of activation or deactivation date |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
250 :-VAS / Static IP : To be charged for complete month or pro-rated regardless of activation or deactivation date |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
251 :-Voice only: Line rent to be charged for complete month or pro-rated regardless of activation or deactivation date |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
252 :-Internal shifting Separate charges
Copper Advance Customer , internal shift charges example Rs. 500 will be validated |
|
IBM |
P |
Internal and External Shifting - Copper |
|
| 15942 |
1:-Advance Billing2 |
253 :-External shifting Separate charges
Copper Advance Customer , external shift charges example Rs. 1000 will be validated |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
254 :-Rename Arrears as 'Arrears / Advance |
|
IBM |
P |
Upfront Amount visibility on bill summary page |
|
| 15942 |
1:-Advance Billing2 |
255 :-Upfront visibility in Arrear/Advance head |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
256 :-Detail page |
|
IBM |
P |
vas details Visibility on bottom of the billing pa |
|
| 15942 |
1:-Advance Billing2 |
257 :-Validate Package name is visible on invoice |
|
IBM |
P |
IsNull displayed in place of Package Name |
|
| 15942 |
1:-Advance Billing2 |
258 :-PTCL Owned
If Device is PTCL property |
|
IBM |
P |
Check the ownership of the Device |
|
| 15942 |
1:-Advance Billing2 |
259 :-Customer Owned
If Device is Customer property |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
260 :-Availability of Button on siebel UI
Press button to get the response either PTCL Property or Customer Property |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
261 :-To be tested for ATV
IPTV devices will be ATV for this test case |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
262 :-To be tested for STB
IPTV devices will be STB for this test case |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
263 :-1P |
|
IBM |
P |
Different installation charges for Different Play |
|
| 15942 |
1:-Advance Billing2 |
264 :-2P |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
265 :-3P |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
266 :-QP |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
267 :-1P |
|
IBM |
P |
Different installation charges for Different Play |
|
| 15942 |
1:-Advance Billing2 |
268 :-2P |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
269 :-3P |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
270 :-QP |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
271 :-Format shall be validated
Due to any unforseen reason , quick process should exisit to revert back on normal postpaid process
Ops teams should be alligned on format to run it |
|
IBM |
P |
Advance Billing Roll Back feature for New Customer |
|
| 15942 |
1:-Advance Billing2 |
272 :-Time to Rollback (shoud not be greater than 1 hour)
Due to any unforseen reason , quick backend process should exisit to revert back within 1 hour
Ops teams should be alligned to do this. |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
273 :-Role is mandatory to move the customer from Postpaid to Advance |
|
IBM |
P |
Postpay-to-Advance Movement role-base function if |
|
| 15942 |
1:-Advance Billing2 |
274 :-Changing customer bill nature in bulk in case of any unforseen reason
Customers are on Advance and in case of any unforeseen reason the urgent Script should be run to stop the process within 1 hour. |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
275 :-In advance billing, only Advance products are visible and selectable |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
276 :-New Order for 3 monthly Advance payments Boost Package verification. |
|
IBM |
P |
Advance payments of Boost Package verification |
|
| 15942 |
1:-Advance Billing2 |
277 :-Place New Order for standard subscription. Select BB PKG whose flag is anabled for Area base, system shall validate Eligibility and Feasibility and e2e life cycle of order. |
|
IBM |
P |
Area based grid to be updated (Area Specific Advan |
|
| 15942 |
1:-Advance Billing2 |
278 :-FF customer is on advance billing single play to advance billing 2P/3P - |
|
IBM |
P |
Modify Order |
|
| 15942 |
1:-Advance Billing2 |
279 :-FF customer is on postpaid single play billing, to advance billing 2P/3P |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
280 :-FF customer is on postpaid TV Only billing, to advance billing 2P/3P |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
281 :-FF customer is on advance billing TV Only to advance billing 2P/3P - |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
282 :-xDSL customer is on postpaid TV Only billing, to advance billing 2P/3P |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
283 :-xDSL customer is on advance billing TV Only to advance billing 2P/3P - |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
284 :-Customers TV was on installments and in 3rd month customer is TOS , verify installment behaviour? |
|
IBM |
N |
TOS |
|
| 15942 |
1:-Advance Billing2 |
285 :-Waada Subscription Testing
WADA is DS
Need to enable/subscribe for Advance customer |
|
IBM |
P |
VAS |
|
| 15942 |
1:-Advance Billing2 |
286 :-Waada De-activation Testing
WADA is DS
Need to disbale/Un-subscribe for Advance customer |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
287 :-Shoq to be active on QP packages and billing to be validated. |
|
IBM |
P |
|
|
| 15942 |
1:- |
288 :-Flash Eye Camera package to be validated |
display |
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
289 :-Pro rate all configurations verification |
|
IBM |
P |
Billing |
|
| 15942 |
1:-Advance Billing2 |
290 :-Verify if it is allowed to Set the Commercial Name for a Package (for CBS Ops team)
WCT Part |
|
IBM |
P |
3.3 Event Base Communication |
|
| 15942 |
1:-Advance Billing2 |
291 :-WCT will verify Bulk Migartion Part |
|
IBM |
P |
3.6 Bulk migration from Postpaid to Advance |
|
| 15942 |
1:-Advance Billing2 |
292 :-Whats App Text will be snet same as SMS |
|
IBM |
P |
3.3 Event Base Communication |
|
| 15942 |
1:-Advance Billing2 |
293 :-Email Will be sent |
|
IBM |
P |
3.3 Event Base Communication |
|
| 15942 |
1:-Advance Billing2 |
294 :-Configure Due_date offset value |
|
IBM |
P |
1/4/5. Postpaid shift to advance |
|
| 15942 |
1:-Advance Billing2 |
295 :-STB/ATV Virtual offer code & Price configuration |
|
IBM |
P |
2. Upfront Payment Tax API |
|
| 15942 |
1:-Advance Billing2 |
296 :-PSTN (New connection month) |
|
IBM |
P |
8. Prorate charge calculation for different produc |
|
| 15942 |
1:- |
297 :-Broadbankd (New Connection month) |
display |
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
298 :-IPTV (New connection Month) |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
299 :-VAS/Add-on/Shoq/Static IP/Bolt-On (New connection month) |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
300 :-PSTN (Termination month) |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
301 :-Broadbankd (Termination month) |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
302 :-IPTV (Termination Month) |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
303 :-VAS/Add-on/Shoq/Static IP/Bolt-On (Termination month) |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
304 :-Campiagn with Postpaid Flag |
|
IBM |
P |
Due Date Reminder - POSTPAID |
|
| 15942 |
1:-Advance Billing2 |
305 :-Campiagn with Postpaid Flag |
|
IBM |
P |
After Due date reminder - POSTPAID |
|
| 15942 |
1:-Advance Billing2 |
306 :-Campiagn with Postpaid Flag |
|
IBM |
P |
Pre-TOS reminder 1- POSTPAID |
|
| 15942 |
1:-Advance Billing2 |
307 :-Campiagn with Postpaid Flag |
|
IBM |
P |
Pre-TOS reminder 1 - POSTPAID |
|
| 15942 |
1:-Advance Billing2 |
308 :-Campiagn with Postpaid Flag |
|
IBM |
P |
Batch1 - Postpaid |
|
| 15942 |
1:-Advance Billing2 |
309 :-Campiagn with Postpaid Flag |
|
IBM |
P |
Batch2 - Postpaid |
|
| 15942 |
1:-Advance Billing2 |
310 :-Campiagn with Advance Flag |
|
IBM |
P |
Batch3 - Postpaid |
|
| 15942 |
1:-Advance Billing2 |
311 :-Campiagn with Advance Flag |
|
IBM |
P |
Suspension reminder 1 - Postpaid |
|
| 15942 |
1:-Advance Billing2 |
312 :-Campiagn with Advance Flag |
|
IBM |
P |
Suspension reminder 2 - Postpaid |
|
| 15942 |
1:-Advance Billing2 |
313 :-Campiagn with Advance Flag |
|
IBM |
P |
Bill payment reminder 1 - ADVANCE FLAG |
|
| 15942 |
1:-Advance Billing2 |
314 :-Campiagn with Advance Flag |
|
IBM |
P |
Bill payment reminder 3 - ADVANCE FLAG |
|
| 15942 |
1:-Advance Billing2 |
315 :-Campiagn with Advance Flag |
|
IBM |
P |
Due date reminder - ADVANCE FLAG |
|
| 15942 |
1:-Advance Billing2 |
316 :-Campiagn with Advance Flag |
|
IBM |
P |
After Due date reminder - ADVANCE FLAG |
|
| 15942 |
1:-Advance Billing2 |
317 :-Campiagn with Advance Flag |
|
IBM |
P |
Pre-TOS reminder 1 - ADVANCE FLAG |
|
| 15942 |
1:-Advance Billing2 |
318 :-Campiagn with Advance Flag |
|
IBM |
P |
Pre-TOS reminder 2 - ADVANCE FLAG |
|
| 15942 |
1:-Advance Billing2 |
319 :-Campiagn with Advance Flag |
|
IBM |
P |
TOS reminder - ADVANCE FLAG |
|
| 15942 |
1:-Advance Billing2 |
320 :-Campiagn with Advance Flag |
|
IBM |
P |
Batch1 |
|
| 15942 |
1:-Advance Billing2 |
321 :-Campiagn with Advance Flag |
|
IBM |
P |
Batch2 |
|
| 15942 |
1:-Advance Billing2 |
322 :-Campiagn with Advance Flag |
|
IBM |
P |
Suspension Reminder 1 - ADVANCE FLAG |
|
| 15942 |
1:-Advance Billing2 |
323 :-WhatsApp will be valited with Same SMS text |
|
IBM |
P |
3.3.1.1 Migration xDSL to GPON Conversion (xDSL Te |
|
| 15942 |
1:-Advance Billing2 |
324 :-WhatsApp will be valited with Same SMS text |
|
IBM |
P |
3.3.1.2 Migration xDSL to GPON Conversion (GPON Ne |
|
| 15942 |
1:-Advance Billing2 |
325 :-WhatsApp will be valited with Same SMS text |
|
IBM |
P |
3.3.1.2 Migration xDSL to GPON Conversion (GPON Ne |
|
| 15942 |
1:-Advance Billing2 |
326 :-WhatsApp will be valited with Same SMS text |
|
IBM |
P |
3.3.1.3.1 For Postpaid Change of Internet Price Pl |
|
| 15942 |
1:-Advance Billing2 |
327 :-WhatsApp will be valited with Same SMS text |
|
IBM |
P |
3.3.1.3.1 For Postpaid Change of Internet Price Pl |
|
| 15942 |
1:-Advance Billing2 |
328 :-WhatsApp will be valited with Same SMS text |
|
IBM |
P |
3.3.1.3.2 For Advance Change of Internet Price Pla |
|
| 15942 |
1:-Advance Billing2 |
329 :-WhatsApp will be valited with Same SMS text |
|
IBM |
P |
3.3.1.4.1 Bolt-On Activation with New Order - Adva |
|
| 15942 |
1:-Advance Billing2 |
330 :-WhatsApp will be valited with Same SMS text |
|
IBM |
P |
3.3.1.4.1 Bolt-On Activation with New Order - Post |
|
| 15942 |
1:-Advance Billing2 |
331 :-WhatsApp will be valited with Same SMS text |
|
IBM |
P |
3.3.1.5 VAS Activation- New Order - Advance Billin |
|
| 15942 |
1:-Advance Billing2 |
332 :-WhatsApp will be valited with Same SMS text |
|
IBM |
P |
3.3.1.5 VAS Activation- New Order - Postpaid- What |
|
| 15942 |
1:-Advance Billing2 |
333 :-Button is not enable untill user read T&C |
|
IBM |
P |
POSTPAID TO ADVANCE VIA SELF-CARE - Website |
|
| 15942 |
1:-Advance Billing2 |
334 :-Nature of Billing Identification |
|
IBM |
P |
POSTPAID TO ADVANCE VIA SELF-CARE - Website |
|
| 15942 |
1:-Advance Billing2 |
335 :-Button Enable/Disbale for Advance billing customer |
|
IBM |
P |
POSTPAID TO ADVANCE VIA SELF-CARE - Website |
|
| 15942 |
1:-Advance Billing2 |
336 :-Error Message if SR is already submitted |
|
IBM |
P |
POSTPAID TO ADVANCE VIA SELF-CARE - Website |
|
| 15942 |
1:-Advance Billing2 |
337 :-WhatsApp |
|
IBM |
P |
3.3.1.1 Migration xDSL to GPON Conversion (xDSL Te |
|
| 15942 |
1:-Advance Billing2 |
338 :-WhatsApp Text |
|
IBM |
P |
3.3.1.2 Migration xDSL to GPON Conversion (GPON Ne |
|
| 15942 |
1:-Advance Billing2 |
339 :-WhatsApp Text |
|
IBM |
P |
3.3.1.2 Migration xDSL to GPON Conversion (GPON Ne |
|
| 15942 |
1:-Advance Billing2 |
340 :-WhatsApp Text |
|
IBM |
P |
3.3.1.3.2 For Advance Change of Internet Price Pla |
|
| 15942 |
1:-Advance Billing2 |
341 :-Bolton Deactivation- WhatsApp on Advance Customer |
|
IBM |
P |
3.3.1.4.2 Bolt-On Deactivation |
|
| 15942 |
1:-Advance Billing2 |
342 :-Bolton Deactivation -WhatsApp on Postpaid Customer |
|
IBM |
P |
3.3.1.4.2 Bolt-On Deactivation |
|
| 15942 |
1:-Advance Billing2 |
343 :-Advance SMS channel by OCR |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
344 :-Postpaid SMS channel by OCR |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
345 :-Advance SMS channel by CMP |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
346 :-Postpaid SMS channel by CMP |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
347 :-Advance Email Channel by OCR |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
348 :-Postpaid Email Channel by OCR |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
349 :-Advance Email Channel by CMP |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
350 :-Postpaid Email Channel by CMP |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
351 :-Advance Whatsapp Channel by OCR |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
352 :-Postpaid Whatsapp Channel by OCR |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
353 :-Advance Whatsapp Channel by CMP |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
354 :-Postpaid Whatsapp Channel by CMP |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
355 :-Advance SMS channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
356 :-Postpaid SMS channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billling 2 |
357 :-Advance Email channel |
display |
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
358 :-Postpaid Email channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
359 :-PSTN Advance Whatsapp channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
360 :-PSTN Postpaid Whatsapp channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
361 :-Advance SMS channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
362 :-Postpaid SMS channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
363 :-Advance Email channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billling 2 |
364 :-Postpaid Email channel |
display |
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
365 :-Advance Whatsapp channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
366 :-Postpaid Whatsapp channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
367 :-Advance SMS channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
368 :-Postpaid SMS channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
369 :-Advance Email Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
370 :-Postpaid Email Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
371 :-Advance Whatsapp Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
372 :-Postpaid Whatsapp Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
373 :-Advance SMS channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
374 :-Postpaid SMS channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
375 :-Advance Email Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billling 2 |
376 :-Postpaid Email Channel |
display |
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
377 :-Advance Whatsapp Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
378 :-Postpaid Whatsapp Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
379 :-Advance SMS channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
380 :-Postpaid SMS channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
381 :-Advance Email Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
382 :-Postpaid Email Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
383 :-Advance Whatsapp Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
384 :-Postpaid Whatsapp Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
385 :-Advance SMS channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
386 :-Postpaid SMS channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
387 :-Advance Email Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
388 :-Postpaid Email Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
389 :-Advance Whatsapp Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
390 :-Postpaid Whatsapp Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
391 :-Advance SMS channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
392 :-Postpaid SMS channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
393 :-Advance Email Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
394 :-Postpaid Email Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
395 :-Advance Whatsapp Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
396 :-Postpaid Whatsapp Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
397 :-Advance SMS channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
398 :-Postpaid SMS channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
399 :-Advance Email Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
400 :-Postpaid Email Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
401 :-Advance Whatsapp Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
402 :-Postpaid Whatsapp Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
403 :-Advance SMS channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
404 :-Postpaid SMS channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
405 :-Advance Email Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
406 :-Postpaid Email Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
407 :-Advance Whatsapp Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
408 :-Postpaid Whatsapp Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
409 :-Advance SMS channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
410 :-Postpaid SMS channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
411 :-Advance Email Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
412 :-Postpaid Email Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
413 :-Advance Whatsapp Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
414 :-Postpaid Whatsapp Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
415 :-Advance SMS channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
416 :-Postpaid SMS channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
417 :-Advance Email Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
418 :-Postpaid Email Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
419 :-Advance Whatsapp Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
420 :-Postpaid Whatsapp Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
421 :-Advance SMS channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
422 :-Advance Email Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
423 :-Advance Whatsapp Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
424 :-Postpaid Whatsapp Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
425 :-Advance SMS channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
426 :-Postpaid SMS channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
427 :-Advance Email Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
428 :-Postpaid Email Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
429 :-Advance Whatsapp Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
430 :-Postpaid Whatsapp Channel |
|
WCT |
P |
|
|
| 15942 |
1:-Advance Billing2 |
7 :-Create a Migration Order and check if Nature of Billing is set to Advance based on Division that is included in the criteria list. |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
6 :-Create a Modify Order and check if Nature of Billing is set to Postpaid based on Division that is not included in the criteria list. |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
8 :-Create a Migration Order and check if Nature of Billing is set to Advance based on Division that is not included in the criteria list.
Example :
F8 Division is not set for advance
XDSL closed and migrate to GPON
in this case Advance billing feature will not be given to customer. |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
9 :-Create a Migration Order and check if Nature of Billing is set to Postpaid based on Division that is not included in the criteria list. |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billling 2 |
10 :-Create a Restoration Order and check if Nature of Billing is set to Advance based on Division that is included in the criteria list. |
display |
IBM |
P |
|
|
| 15942 |
1:-Advance Billling 2 |
11 :-Create a Restoration Order and check if Nature of Billing is set to Advance based on Division that is not included in the criteria list. |
display |
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
13 :-Verify if it is allowed to Configure Division in the matrix (for IT Ops team) |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billling 2 |
12 :-Create a Restoration Order and check if Nature of Billing is set to Postpaid based on Division that is not included in the criteria list. |
display |
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
14 :-Create an SR to verify Return STB (Return STB/ATV with all accessories) for GPON. Verify response and charges |
|
IBM |
P |
3.2Customer is billed and wants to return STB
C |
|
| 15942 |
1:-Advance Billing2 |
16 :-Create an SR to verify Return ATV (Return STB/ATV with remote and charger) for GPON. Verify response and charges |
|
IBM |
P |
Customer status Active- Postpaid- GPON- ATV-return |
|
| 15942 |
1:-Advance Billing2 |
15 :-Create an SR to verify Return STB (Return STB/ATV with all accessories) for GPON. Verify response and charges |
|
IBM |
P |
Customer status Active- Advance Billing- GPON - ST |
|
| 15942 |
1:-Advance Billing2 |
3 :-Create a New Order and check if Nature of Billing is set to Postpaid based on Division that is not included in the criteria list. |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
5 :-Create a Modify Order and check if Nature of Billing is set to Advance based on Division that is not included in the criteria list.
Example :
F8 Division is not set for advance so in this case Advance billing feature will not be given to customer. |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
4 :-Create a Modify Order and check if Nature of Billing is set to Advance based on Division that is included in the criteria list. |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
2 :-Create a New Order and check if Nature of Billing is set to Advance based on Division that is not included in the criteria list.
Example :
F8 Division is not set for advance so in this case Advance billing feature will not be given to customer. |
|
IBM |
P |
|
|
| 15942 |
1:-Advance Billing2 |
1 :-Create a New Order and check if Nature of Billing is set to Advance based on Division that is included in the criteria list. |
|
IBM |
P |
3.1 Advance Billing on Division Level |
|
| 22667 |
1:-POMS Enhancements for Devices Vendor Partnerships |
2 :-Verify Sales Staff ID shows in PCRM |
Sales Staff ID/Referral ID displayed in PCRM |
PTCL |
P |
|
|
| 22667 |
1:-POMS Enhancements for Devices Vendor Partnerships |
1 :-Verify Devices Portfolio is Available in POMS |
All vendor portfolios and products load correctly |
PTCL |
P |
|
|
| 22667 |
1:- |
4 :-Bulk Cancel Orders Before July-2025 |
All orders before July-2025 are cancelled |
PTCL |
P |
|
|
| 22667 |
1:-POMS Enhancements for Devices Vendor Partnerships |
5 :-Verify Filters Do Not Reset After Vendor Action |
Filters remain applied |
PTCL |
P |
|
|
| 22667 |
1:- |
3 :-Verify Last Updated Date exists in PCRM backend |
Column exists and shows correct date/time |
PTCL |
P |
|
|
| 22667 |
1:- |
14 :-Verify Bulk Reject Orders |
Selected orders rejected |
PTCL |
N |
|
|
| 22667 |
1:-POMS Enhancements for Devices Vendor Partnerships |
12 :-Verify Vendor Edit Order Error Fix |
Order edits save without error |
PTCL |
P |
|
|
| 22667 |
1:- |
13 :-Vendor Sees Only Own Orders with Status |
Vendor sees only own orders + statuses |
PTCL |
P |
|
|
| 22667 |
1:-POMS Enhancements for Devices Vendor Partnerships |
10 :-Verify SR Generation in Siebel for Extender |
SR 'Additional Access Point Required' is created |
PTCL |
P |
|
|
| 22667 |
1:- |
11 :-Verify Separate BI Report for Devices |
Devices report available |
PTCL |
N |
|
|
| 22667 |
1:-POMS Enhancements for Devices Vendor Partnerships |
9 :-Verify New Sale Type 'PTCL Owner Extender' |
'PTCL Owner Extender' appears |
PTCL |
P |
|
|
| 22667 |
1:-POMS Enhancements for Devices Vendor Partnerships |
8 :-Verify Single Page Workflow for Processing & Dispatch |
Single page supports both actions |
PTCL |
P |
|
|
| 22667 |
1:-POMS Enhancements for Devices Vendor Partnerships |
6 :-Verify Vendors Only See Their Own Orders |
Vendor only sees their own orders |
PTCL |
P |
|
|
| 22667 |
1:-POMS Enhancements for Devices Vendor Partnerships |
7 :-Fix Date Filter Issue |
Orders for correct date appear |
PTCL |
P |
|
|
| 22667 |
1:- |
18 :-Validate One-Row Summary Report |
Order appears single row with full fields |
PTCL |
N |
|
|
| 22667 |
1:-POMS Enhancements for Devices Vendor Partnerships |
17 :-Validate Completed Orders Monthly Report |
Each product appears as separate row with full detail |
PTCL |
P |
|
|
| 22667 |
1:-POMS Enhancements for Devices Vendor Partnerships |
16 :-Verify Excel/CSV Export |
File exports correctly |
PTCL |
P |
|
|
| 22667 |
1:-POMS Enhancements for Devices Vendor Partnerships |
15 :-Verify Order Tagging by Sales Channel |
Correct channel tags applied |
PTCL |
P |
|
|
| 22339 |
2:-SR Creation English Android |
17 :-Service Request screen shows SR details (ID, Date, Speed Boost, Track, Back). |
|
EVAM |
P |
|
|
| 22339 |
3:-SR Creation English IOS |
17 :-Service Request screen shows SR details (ID, Date, Speed Boost, Track, Back). |
|
EVAM |
P |
|
|
| 22339 |
4:-SR Creation Urdu Android |
17 :-Service Request screen shows SR details (ID, Date, Speed Boost, Track, Back). |
|
EVAM |
P |
|
|
| 22339 |
5:-SR Creation Urdu IOS |
17 :-Service Request screen shows SR details (ID, Date, Speed Boost, Track, Back). |
|
EVAM |
P |
|
|
| 22339 |
2:-SR Creation English Android |
18 :-Track Request navigates to My Orders screen. |
|
EVAM |
P |
|
|
| 22339 |
3:-SR Creation English IOS |
18 :-Track Request navigates to My Orders screen. |
|
EVAM |
P |
|
|
| 22339 |
4:-SR Creation Urdu Android |
18 :-Track Request navigates to My Orders screen. |
|
EVAM |
P |
|
|
| 22339 |
5:-SR Creation Urdu IOS |
18 :-Track Request navigates to My Orders screen. |
|
EVAM |
P |
|
|
| 22339 |
2:-SR Creation English Android |
19 :-If existing SR exists, show appropriate message. |
|
EVAM |
P |
|
|
| 22339 |
3:-SR Creation English IOS |
19 :-If existing SR exists, show appropriate message. |
|
EVAM |
P |
|
|
| 22339 |
4:-SR Creation Urdu Android |
19 :-If existing SR exists, show appropriate message. |
|
EVAM |
P |
|
|
| 22339 |
5:-SR Creation Urdu IOS |
19 :-If existing SR exists, show appropriate message. |
|
EVAM |
P |
|
|
| 22339 |
2:-SR Creation English Android |
20 :-Advanced billing option should be enabled/disabled via configuration. |
|
EVAM |
P |
|
|
| 22339 |
3:-SR Creation English IOS |
20 :-Advanced billing option should be enabled/disabled via configuration. |
|
EVAM |
P |
|
|
| 22339 |
4:-SR Creation Urdu Android |
20 :-Advanced billing option should be enabled/disabled via configuration. |
|
EVAM |
P |
|
|
| 22339 |
5:-SR Creation Urdu IOS |
20 :-Advanced billing option should be enabled/disabled via configuration. |
|
EVAM |
P |
|
|
| 22339 |
2:-SR Creation English Android |
7 :-User should be able to view Terms & Conditions by clicking the link. |
|
EVAM |
P |
|
|
| 22339 |
3:-SR Creation English IOS |
7 :-User should be able to view Terms & Conditions by clicking the link. |
|
EVAM |
P |
|
|
| 22339 |
4:-SR Creation Urdu Android |
7 :-User should be able to view Terms & Conditions by clicking the link. |
|
EVAM |
P |
|
|
| 22339 |
5:-SR Creation Urdu IOS |
7 :-User should be able to view Terms & Conditions by clicking the link. |
|
EVAM |
P |
|
|
| 22339 |
2:-SR Creation English Android |
6 :-Next button should be enabled only after selecting Terms & Conditions. |
|
EVAM |
P |
|
|
| 22339 |
3:-SR Creation English IOS |
6 :-Next button should be enabled only after selecting Terms & Conditions. |
|
EVAM |
P |
|
|
| 22339 |
4:-SR Creation Urdu Android |
6 :-Next button should be enabled only after selecting Terms & Conditions. |
|
EVAM |
P |
|
|
| 22339 |
5:-SR Creation Urdu IOS |
6 :-Next button should be enabled only after selecting Terms & Conditions. |
|
EVAM |
P |
|
|
| 22339 |
2:-SR Creation English Android |
8 :-Terms & Conditions bottom sheet should appear and can be closed using X icon. |
|
EVAM |
P |
|
|
| 22339 |
3:-SR Creation English IOS |
8 :-Terms & Conditions bottom sheet should appear and can be closed using X icon. |
|
EVAM |
P |
|
|
| 22339 |
4:-SR Creation Urdu Android |
8 :-Terms & Conditions bottom sheet should appear and can be closed using X icon. |
|
EVAM |
P |
|
|
| 22339 |
5:-SR Creation Urdu IOS |
8 :-Terms & Conditions bottom sheet should appear and can be closed using X icon. |
|
EVAM |
P |
|
|
| 22339 |
2:-SR Creation English Android |
9 :-Confirmation bottom sheet should appear with Cancel & Confirm after clicking Next. |
|
EVAM |
P |
|
|
| 22339 |
3:-SR Creation English IOS |
9 :-Confirmation bottom sheet should appear with Cancel & Confirm after clicking Next. |
|
EVAM |
P |
|
|
| 22339 |
4:-SR Creation Urdu Android |
9 :-Confirmation bottom sheet should appear with Cancel & Confirm after clicking Next. |
|
EVAM |
P |
|
|
| 22339 |
5:-SR Creation Urdu IOS |
9 :-Confirmation bottom sheet should appear with Cancel & Confirm after clicking Next. |
|
EVAM |
P |
|
|
| 22339 |
2:-SR Creation English Android |
10 :-Displayed description: First advance bill includes current month + next month rental. |
|
EVAM |
P |
|
|
| 22339 |
3:-SR Creation English IOS |
10 :-Displayed description: First advance bill includes current month + next month rental. |
|
EVAM |
P |
|
|
| 22339 |
4:-SR Creation Urdu Android |
10 :-Displayed description: First advance bill includes current month + next month rental. |
|
EVAM |
P |
|
|
| 22339 |
5:-SR Creation Urdu IOS |
10 :-Displayed description: First advance bill includes current month + next month rental. |
|
EVAM |
P |
|
|
| 22339 |
2:-SR Creation English Android |
11 :-Cancel closes bottom sheet without changes. |
|
EVAM |
P |
|
|
| 22339 |
3:-SR Creation English IOS |
11 :-Cancel closes bottom sheet without changes. |
|
EVAM |
P |
|
|
| 22339 |
4:-SR Creation Urdu Android |
11 :-Cancel closes bottom sheet without changes. |
|
EVAM |
P |
|
|
| 22339 |
5:-SR Creation Urdu IOS |
11 :-Cancel closes bottom sheet without changes. |
|
EVAM |
P |
|
|
| 22339 |
2:-SR Creation English Android |
12 :-If user type = Advance, an error message should appear. |
|
EVAM |
P |
|
|
| 22339 |
3:-SR Creation English IOS |
12 :-If user type = Advance, an error message should appear. |
|
EVAM |
P |
|
|
| 22339 |
4:-SR Creation Urdu Android |
12 :-If user type = Advance, an error message should appear. |
|
EVAM |
P |
|
|
| 22339 |
5:-SR Creation Urdu IOS |
12 :-If user type = Advance, an error message should appear. |
|
EVAM |
P |
|
|
| 22339 |
2:-SR Creation English Android |
14 :-Try Again reopens confirmation sheet. |
|
EVAM |
P |
|
|
| 22339 |
3:-SR Creation English IOS |
14 :-Try Again reopens confirmation sheet. |
|
EVAM |
P |
|
|
| 22339 |
4:-SR Creation Urdu Android |
14 :-Try Again reopens confirmation sheet. |
|
EVAM |
P |
|
|
| 22339 |
5:-SR Creation Urdu IOS |
14 :-Try Again reopens confirmation sheet. |
|
EVAM |
N |
|
|
| 22339 |
2:-SR Creation English Android |
13 :-Error bottom sheet shows Try Again & Back. |
|
EVAM |
P |
|
|
| 22339 |
3:-SR Creation English IOS |
13 :-Error bottom sheet shows Try Again & Back. |
|
EVAM |
P |
|
|
| 22339 |
4:-SR Creation Urdu Android |
13 :-Error bottom sheet shows Try Again & Back. |
|
EVAM |
P |
|
|
| 22339 |
5:-SR Creation Urdu IOS |
13 :-Error bottom sheet shows Try Again & Back. |
|
EVAM |
P |
|
|
| 22339 |
2:-SR Creation English Android |
15 :-Back redirects user to Home screen. |
|
EVAM |
P |
|
|
| 22339 |
3:-SR Creation English IOS |
15 :-Back redirects user to Home screen. |
|
EVAM |
N |
|
|
| 22339 |
4:-SR Creation Urdu Android |
15 :-Back redirects user to Home screen. |
|
EVAM |
P |
|
|
| 22339 |
5:-SR Creation Urdu IOS |
15 :-Back redirects user to Home screen. |
|
EVAM |
P |
|
|
| 22339 |
2:-SR Creation English Android |
16 :-If user is not advanced, redirect to Service Request screen. |
|
EVAM |
P |
|
|
| 22339 |
3:-SR Creation English IOS |
16 :-If user is not advanced, redirect to Service Request screen. |
|
EVAM |
P |
|
|
| 22339 |
4:-SR Creation Urdu Android |
16 :-If user is not advanced, redirect to Service Request screen. |
|
EVAM |
P |
|
|
| 22339 |
5:-SR Creation Urdu IOS |
16 :-If user is not advanced, redirect to Service Request screen. |
|
EVAM |
P |
|
|
| 22339 |
2:-SR Creation English Android |
3 :-The menu and widget should not be shown to the user who has already switched to advance billing. |
|
EVAM |
P |
|
|
| 22339 |
3:-SR Creation English IOS |
3 :-The menu and widget should not be shown to the user who has already switched to advance billing. |
|
EVAM |
P |
|
|
| 22339 |
4:-SR Creation Urdu Android |
3 :-The menu and widget should not be shown to the user who has already switched to advance billing. |
|
EVAM |
P |
|
|
| 22339 |
5:-SR Creation Urdu IOS |
3 :-The menu and widget should not be shown to the user who has already switched to advance billing. |
|
EVAM |
P |
|
|
| 22339 |
2:-SR Creation English Android |
5 :-On 'Switch to Advance Billing' screen, user should see: Banner, How to Use section, Terms & Conditions checkbox, Next button disabled. |
|
EVAM |
P |
|
|
| 22339 |
3:-SR Creation English IOS |
5 :-On 'Switch to Advance Billing' screen, user should see: Banner, How to Use section, Terms & Conditions checkbox, Next button disabled. |
|
EVAM |
P |
|
|
| 22339 |
4:-SR Creation Urdu Android |
5 :-On 'Switch to Advance Billing' screen, user should see: Banner, How to Use section, Terms & Conditions checkbox, Next button disabled. |
|
EVAM |
P |
|
|
| 22339 |
5:-SR Creation Urdu IOS |
5 :-On 'Switch to Advance Billing' screen, user should see: Banner, How to Use section, Terms & Conditions checkbox, Next button disabled. |
|
EVAM |
P |
|
|
| 22339 |
2:-SR Creation English Android |
4 :-User should be redirected to 'Switch to Advance Billing' screen when clicking 'Advance Billing' on Home, Menu, or Shop. |
|
EVAM |
P |
|
|
| 22339 |
3:-SR Creation English IOS |
4 :-User should be redirected to 'Switch to Advance Billing' screen when clicking 'Advance Billing' on Home, Menu, or Shop. |
|
EVAM |
P |
|
|
| 22339 |
4:-SR Creation Urdu Android |
4 :-User should be redirected to 'Switch to Advance Billing' screen when clicking 'Advance Billing' on Home, Menu, or Shop. |
|
EVAM |
P |
|
|
| 22339 |
5:-SR Creation Urdu IOS |
4 :-User should be redirected to 'Switch to Advance Billing' screen when clicking 'Advance Billing' on Home, Menu, or Shop. |
|
EVAM |
P |
|
|
| 22339 |
2:-SR Creation English Android |
1 :-Verify that only PTCL/FlashFiber user can view the 'Switch to Advance Billing' widget and quick links on the home screen. |
|
EVAM |
P |
|
|
| 22339 |
3:-SR Creation English IOS |
1 :-Verify that only PTCL/FlashFiber user can view the 'Switch to Advance Billing' widget and quick links on the home screen. |
|
EVAM |
P |
|
|
| 22339 |
4:-SR Creation Urdu Android |
1 :-Verify that only PTCL/FlashFiber user can view the 'Switch to Advance Billing' widget and quick links on the home screen. |
|
EVAM |
P |
|
|
| 22339 |
5:-SR Creation Urdu IOS |
1 :-Verify that only PTCL/FlashFiber user can view the 'Switch to Advance Billing' widget and quick links on the home screen. |
|
EVAM |
P |
|
|
| 22339 |
2:-SR Creation English Android |
2 :-Verify that PTCL/FlashFiber user can view the 'Advance Billing' menu in Menu listing & Shop screen. |
|
EVAM |
P |
|
|
| 22339 |
3:-SR Creation English IOS |
2 :-Verify that PTCL/FlashFiber user can view the 'Advance Billing' menu in Menu listing & Shop screen. |
|
EVAM |
P |
|
|
| 22339 |
4:-SR Creation Urdu Android |
2 :-Verify that PTCL/FlashFiber user can view the 'Advance Billing' menu in Menu listing & Shop screen. |
|
EVAM |
P |
|
|
| 22339 |
5:-SR Creation Urdu IOS |
2 :-Verify that PTCL/FlashFiber user can view the 'Advance Billing' menu in Menu listing & Shop screen. |
|
EVAM |
P |
|
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
2 :-To Verify that the value of Radius for Eligibility & Feasibility are configurable for regions independent of IRR. |
Value of Radius should be configurable. No order will be placed. |
IBM |
P |
|
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
1 :-To Verify that the new optional field Parcel is available in Service Account. Validate the lat long fields are mandatory and cannot be null. |
New field should be visible in Service Account. No order will be placed. |
IBM |
P |
|
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
5 :-To Create a New Order with promotion Price Plan for GPON Subscription having the correct Lat Long value for specific FDH for which the promotion is not eligible. |
New Order should not be submitted & error message should be displayed. Error Message: “Promotion is not available for this customer” |
IBM |
P |
|
|
| 20009 |
1:- |
4 :-To Create a New Order with promotion Price Plan for GPON Subscription having the correct Lat Long value for specific FDH for which the promotion is eligible. |
New Order should be successfully submitted to next step. |
IBM |
P |
66, 67 , 71, 72 , 73, 74 , 77 |
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
3 :-To Verify that the identifier is available against the Price Plans & Discount Suites which require the Eligibility check from the External System. |
Identifier should be available. No order will be placed. |
IBM |
P |
|
|
| 20009 |
1:- |
16 :-To Verify that for New Order having GPON Subscription the ‘Y’ or ‘N’ status of the Auto Feasibility is displayed in the Order Header after Submitting the order when the Lat/Long values and radius are provided in the Service Account and Order revision is less than or equal to 1. |
Status of Auto Feasibility should be available on Order Header. |
IBM |
P |
5,54 |
|
| 20009 |
1:- |
15 :-To Create a New Order for GPON Subscription and verify that the auto feasibility is called upon Submitting the order when the Lat/Long values and radius are provided in the Service Account and Order revision is less than or equal to 1. Also add a valid promotion in the order. |
Auto Eligibility should respond with Yes and Auto Feasibility should be called for New Order having GPON Subscription when the above criteria are met. |
IBM |
P |
5,47 |
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
14 :-To Create a Restore Order for Terminated customer which already contains promotional Price Plan & Discount Suite for GPON Subscription but promotional Price Plan and Discount Suite are valid at the time of Restore Order. |
Order should be submitted successfully with same Price Plan & Discount Suite. |
IBM |
P |
85 |
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
12 :-To Create a Resume Order for Suspended customer which already contains promotional Price Plan & Discount Suite for GPON Subscription. |
Order should be successfully submitted to next step. |
IBM |
P |
84 |
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
13 :-To Create a Restore Order for Terminated customer which already contains promotional Price Plan & Discount Suite for GPON Subscription but promotional Price Plan and Discount Suite are not valid at the time of Restore Order. |
Order should not be submitted and user should be asked to select new Price Plan and Discount Suite. |
IBM |
P |
86 |
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
11 :-To Create a xDSL to GPON Conversion New Order with promotion Price Plan for GPON Subscription having the correct Lat Long value for specific FDH for which the promotion is not eligible. |
Order should not be submitted to next step. Error Message should be displayed. Error Message: “Promotion is not available for this customer” |
IBM |
P |
|
|
| 20009 |
1:- |
10 :-To Create a xDSL to GPON Conversion New Order with promotion Price Plan for GPON Subscription having the correct Lat Long value for specific FDH for which the promotion is eligible. The feasibility response to be Y. |
Order should be successfully submitted to next step. |
IBM |
P |
31,32 |
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
8 :-To Create a Modify Order with promotion Price Plan for GPON Subscription having the correct Lat Long value for specific FDH for which the promotion is eligible. |
Modify Order should be successfully submitted to next step. Ensure that Auto Feasibility is not called for this case. |
IBM |
P |
17,18,81 |
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
9 :-To Create a Modify Order with promotion Discount Suite for GPON Subscription having the correct Lat Long value for specific FDH for which the promotion is eligible. |
Order should be successfully submitted to next step. |
IBM |
P |
|
|
| 20009 |
1:- |
6 :-To Create a New Order with promotion Discount Suite for GPON Subscription having the correct Lat Long value for specific FDH for which the promotion is eligible. This will be tested after one promo returns N as eligibility. |
New Order should be successfully submitted to next step. |
IBM |
P |
78 |
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
7 :-To Create a New Order with promotion Discount Suite for GPON Subscription having the correct Lat Long value for specific FDH for which the promotion is not eligible. |
Order should not be submitted to next step. Error Message should be displayed. Error Message: “Promotion is not available for this customer” |
IBM |
P |
|
|
| 20009 |
1:- |
20 :-To Create a New Order having GPON Subscription when ‘Y’ is returned from Auto Feasibility, verify order moves to ‘Awaiting Payment Confirmation’ or ‘WFRA’, SMS sent, and resources locked in Maximo. |
Resources should be reserved and not editable at WFRA step. |
IBM |
P |
35,52,53 |
|
| 20009 |
1:- |
21 :-To Create a New Order having GPON Subscription when ‘Y’ is returned from Auto Feasibility, verify order moves to ‘Awaiting Payment Confirmation’ or ‘WFRA’, SMS sent, and resources are editable after new role assignment in Maximo. |
Resources should be reserved and editable by user having proper rights at WFRA Step. |
IBM |
P |
59 |
|
| 20009 |
1:- |
23 :-To Verify that for Restore Order having GPON Subscription when ‘Y’ is returned from Auto Feasibility the Order moves to ‘Awaiting Payment Confirmation’ or ‘WFRA’ and SMS is sent. |
Restore Order should move to ‘Awaiting Payment Confirmation’ or ‘WFRA’ and SMS sent. |
IBM |
P |
19,20,24 |
|
| 20009 |
1:- |
22 :-To verify that for a Restore Order for GPON Subscription if there are any OTC Charges available then the Order moves to Awaiting Payment Confirmation, and proceeds after payment is received. |
Restore order should move to Awaiting Payment Confirmation and upon receiving payment should move to WFRA. |
IBM |
P |
14,101 |
|
| 20009 |
1:- |
28 :-To Create a Modify Order with promotion Price Plan for GPON Subscription having the correct Lat Long value for FDH where promotion is not eligible. |
Modify Order should not be submitted to next step & error message displayed: “Promotion is not available for this customer.” |
IBM |
P |
82,83 |
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
29 :-To Create a Modify Order with promotion Discount Suite for GPON Subscription having the correct Lat Long value for FDH where promotion is not eligible. |
Modify Order should not be submitted to next step & error message displayed: “Promotion is not available for this customer.” |
IBM |
P |
|
|
| 20009 |
1:- |
27 :-To Create a Restore Order having GPON Subscription when ‘Y’ is returned from Auto Feasibility, verify order moves to ‘Awaiting Payment Confirmation’ or ‘WFRA’, SMS sent, and resources editable after new role assignment in Maximo. |
Resources should be reserved and editable by user with proper rights at WFRA Step. |
IBM |
P |
36,104 |
|
| 20009 |
1:- |
24 :-To Verify that for Restore Order having GPON Subscription when ‘N’ is returned from Auto Feasibility the Order moves to ‘Awaiting Mark Feasibility’. |
Restore Order should move to ‘Awaiting Mark Feasibility’. |
IBM |
P |
25,16,102 |
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
25 :-To Verify that for Restore Order having GPON Subscription when ‘N’ is returned from Auto Feasibility and Manual Feasibility marks ‘Not Feasible’, Order is marked as Not Feasible and SMS sent. |
Restore Order should be marked as ‘Not Feasible’ and SMS sent to customer. |
IBM |
P |
21,22 |
|
| 20009 |
1:- |
26 :-To Create a Restore Order having GPON Subscription when ‘Y’ is returned from Auto Feasibility, verify order moves to ‘Awaiting Payment Confirmation’ or ‘WFRA’, SMS sent, and resources not editable in Maximo. |
Resources should be reserved and not editable by user at WFRA Step. |
IBM |
P |
103 |
|
| 20009 |
1:- |
19 :-To Verify that when Auto Feasibility returns ‘N’, and Manual Feasibility marks ‘Not Feasible’, the Order is marked as Not Feasible and SMS sent. |
Order should be marked as ‘Not Feasible’ and SMS sent to customer. |
IBM |
P |
96 |
|
| 20009 |
1:- |
18 :-To Verify that for New Order having GPON Subscription when ‘N’ is returned from Auto Feasibility the Order is moved to ‘Awaiting Mark Feasibility’. Add a valid promotion. |
Order should be moved to ‘Awaiting Mark Feasibility’. |
IBM |
P |
12,13,64 |
|
| 20009 |
1:- |
17 :-To Verify that for New Order having GPON Subscription when ‘Y’ is returned from the Auto Feasibility the Order is moved to ‘Awaiting Payment Confirmation’ or ‘WFRA’ and SMS sent to customer. Also check revision 2 for feasibility copy. |
Order should move to ‘Awaiting Payment Confirmation’/‘WFRA’, SMS sent, feasibility copied in revision. |
IBM |
P |
108.6,48 |
|
| 20009 |
1:- |
32 :-To Verify the error responses returned from Maximo in case of Missing Hierarchy. |
Error message showing the missing network element should be displayed. |
IBM |
P |
76 |
|
| 20009 |
1:- |
33 :-To Create a xDSL to GPON Conversion New Order without promotion Price Plan for GPON Subscription and verify Auto Feasibility returns Y when Lat/Long and radius are provided and revision =1. |
Auto Eligibility should respond “Yes”, Auto Feasibility called, and SMS sent: “Dear Customer, Your order number [Order_Num] is marked feasible for installation and will be installed in due course.” |
IBM |
P |
27,28 |
|
| 20009 |
1:- |
34 :-To Create a xDSL to GPON Conversion New Order with promotion Price Plan for GPON Subscription and verify Auto Feasibility returns N when Lat/Long and radius are provided and revision =1. |
New Order should be moved to ‘Awaiting Mark Feasibility’. |
IBM |
P |
29,30,33,34,25 |
|
| 20009 |
1:- |
31 :-To Verify that in a New Order for GPON Subscription when Payment Bypass line item is available in the Order and the Order has 0 upfront payment, the Order should move directly to Awaiting Resource Allocation upon receiving success response from Auto-Feasibility webservice. |
New Order should move to Awaiting Resource Allocation. |
IBM |
P |
106 |
|
| 20009 |
1:- |
30 :-To Verify that in a New Order for GPON Subscription when exception is returned by Auto-Feasibility web service the order is moved to Awaiting Mark Feasibility and error message displayed. |
New Order should move to Awaiting Mark Feasibility and error message displayed. |
IBM |
P |
37 |
|
| 20009 |
1:- |
42 :-To Verify that for New Order having GPON Subscription (OTC = 0, Feasibility Bypass = Y, Payment Bypass = Y) — Order should go to WFRA. |
New Order should go to WFRA. |
IBM |
P |
113 |
|
| 20009 |
1:- |
41 :-To Verify that for New Order having GPON Subscription (OTC > 0, Feasibility Bypass = Y, Payment Bypass = N) — Order should go to Payment Confirmation and then WFRA. |
New Order should go to Payment step and then WFRA. |
IBM |
P |
112 |
|
| 20009 |
1:- |
40 :-To Verify that for New Order having GPON Subscription (OTC=0, Feasibility Bypass=Y, Payment Bypass=N) — Order should go to WFRA. |
New Order should go to WFRA. |
IBM |
P |
111 |
|
| 20009 |
1:- |
39 :-To Verify that for New Order having GPON Subscription (OTC=0, Feasibility Bypass=N, Payment Bypass=N, Auto Feasibility=N, Manual Feasibility=Feasible) — Order should go to WFRA. |
Order should move to ‘Awaiting Mark Feasibility’ and then to WFRA. |
IBM |
P |
110 |
|
| 20009 |
1:- |
38 :-To Verify that for New Order having GPON Subscription (OTC > 0, Feasibility Bypass=N, Payment Bypass=N, Auto Feasibility=N, Manual Feasibility=Feasible) — Order should go to WFRA. |
Order should move to ‘Awaiting Mark Feasibility’, then ‘Awaiting Payment Confirmation’. |
IBM |
P |
109 |
|
| 20009 |
1:- |
37 :-To Verify that in a New Order for GPON Subscription, resources are allowed to be changed after 48 hours in an order where resources were reserved. |
After 48 hours, resources should be allowed to be changed. |
IBM |
P |
58 |
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
35 :-Auto Eligibility web service (ACE wrapper) will be called from SoapUI with values expected to return “Yes”. |
Service should respond with Success — “The promo is eligible.” |
IBM |
P |
|
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
36 :-To Verify that in a New Order for GPON Subscription when installation charges and advance payment are both 0 (total upfront 0), the Order moves directly to Awaiting Resource Allocation upon Auto-Feasibility success. |
Order should move to Awaiting Resource Allocation without any payment step. |
IBM |
P |
|
|
| 20009 |
1:-GPON Auto Eligibility/Feasibility |
46 :-To Verify that for New Order having GPON Subscription (OTC > 0, Feasibility Bypass = N, Payment Bypass = Y, Auto Feasibility Response = Y) — Order should go to WFRA. |
New Order should go to WFRA after Auto Feasibility. |
IBM |
P |
|
|
| 20009 |
1:- |
45 :-To Verify that for New Order having GPON Subscription (OTC = 0, Feasibility Bypass = N, Payment Bypass = Y, Auto Feasibility = N, Manual Feasibility = Feasible) — Order should go to WFRA. |
New Order should go to WFRA after manual feasibility. |
IBM |
P |
116 |
|
| 20009 |
1:- |
44 :-To Verify that for New Order having GPON Subscription (OTC = 0, Feasibility Bypass = N, Payment Bypass = Y, Auto Feasibility Response = Y) — Order should go to WFRA. |
New Order should go to WFRA. |
IBM |
P |
115 |
|
| 20009 |
1:- |
43 :-To Verify that for New Order having GPON Subscription (OTC > 0, Feasibility Bypass = Y, Payment Bypass = Y) — Order should go to WFRA. |
New Order should go to WFRA. |
IBM |
P |
114 |
|
| 20009 |
1:- |
47 :-To Verify that for New Order having GPON Subscription (OTC > 0, Feasibility Bypass = N, Payment Bypass = Y, Auto Feasibility = N, Manual Feasibility = Feasible) — Order should go to WFRA. |
New Order should go to WFRA after manual feasibility |
IBM |
P |
118 |
|
| 17243 |
1:-Consolidated bill register for B2B Product |
2 :-Cloud Reporting |
data |
BI |
P |
|
|
| 3333 |
1:-crm ui function |
2 :-ui tst |
display user and packages |
IBM |
P |
|
|
| 3333 |
1:-crm ui function |
3 :-fgg |
display user and packages |
IBM |
F |
|
|
| 1234 |
1:-ADV Billing Service |
3 :-SMS on whatsapp ( no) |
SMS on whatsapp ( no) |
IBM |
P |
|
|
| 3333 |
1:-crm ui function |
1 :-Testing data |
Testing data |
IBM |
P |
|
|
| 1234 |
1:-ADV Billing Service |
2 :-SMS on regestered mobile no |
SMS on regestered mobile no |
IBM |
P |
|
|
| 22339 |
1:-SR Creation for postpaid to Advance- PTCL Web |
2 :-SR Creation |
Order Submisstion |
PTCL |
P |
|
|
| 22339 |
1:-SR Creation for postpaid to Advance- PTCL Web |
1 :-Button is not enable untill customer agree T&C |
Checkbox T&C |
PTCL |
P |
|
|
| 22339 |
1:-SR Creation for postpaid to Advance- PTCL Web |
3 :-Natite of Billing |
CRM Status |
PTCL |
P |
|
|
| 22339 |
1:-SR Creation for postpaid to Advance- PTCL Web |
4 :-Button Disable/Enable for Advance Billing |
Only For Non Advance base |
PTCL |
P |
|
|
| 22339 |
1:-SR Creation for postpaid to Advance- PTCL Web |
5 :-Error message for arelady Sr submitted |
SR Already Exist |
PTCL |
P |
|
|
| 22339 |
1:-SR Creation for postpaid to Advance- PTCL Web |
6 :-IF Nature of Billing is Advance |
SR Already Exist |
PTCL |
P |
|
|
| 21299 |
9:-Advance billing for UphoneApp Android Frequent TransactionEnglish |
1 :-User should be able to see the performed subscribed speed Boltons in frequent transactions |
frequent transactions |
PTCL |
P |
|
|
| 21299 |
10:-Advance billing for UphoneApp Android Frequent TransactionUrdu |
1 :-User should be able to see the performed subscribed speed boltons in frequent transactions |
frequent transactions |
PTCL |
P |
|
|
| 21299 |
11:-Advance billing for UphoneApp IOS Frequent TransactionUrdu |
1 :-User should be able to see the performed subscribed speed boltons in frequent transactions |
frequent transactions |
PTCL |
P |
|
|
| 21299 |
12:-Advance billing for UphoneApp IOS Frequent TransactionEnglish |
1 :-User should be able to see the performed subscribed speed boltons in frequent transactions
|
frequent transactions |
PTCL |
P |
|
|
| 21299 |
13:-Advance billing for UphoneApp IOS Transaction History
English |
1 :-"Success" bottom sheet should be displayed by clicking on Yes button in confirmation bottom sheet. |
Speed bolton should be visible |
EVAMP |
P |
Apps |
|
| 21299 |
14:-Advance billing for UphoneApp IOS Transaction History
Urdu |
1 :-User should be redirected to home screen by clicking on "continue" button showing on the success bottom sheet. |
|
EVAMP |
P |
Apps |
|
| 21299 |
15:-Advance billing for UphoneApp Android Transaction History
Urdu |
1 :-User should be able to see the performed subscribed speed boltons in frequent transactions |
|
EVAMP |
P |
Apps |
|
| 21299 |
16:-Advance billing for UphoneApp Android Transaction History
English |
1 :-User should be able to see the performed subscribed speed boltons in frequent transactions |
|
EVAMP |
P |
Apps |
|
| 21299 |
1:-Advance billing for UphoneApp Android VAS English |
1 :-User should be able to login to the PTCL Super app. |
user screen |
EVAMP |
P |
Apps |
|
| 21299 |
2:-Advance billing for UphoneApp IOS VAS English |
1 :-User should be able to login to the PTCL Super app. |
user screen |
EVAMP |
P |
Apps |
|
| 21299 |
3:-Advance billing for UphoneApp Android VAS Urdu |
1 :-User should be able to login to the PTCL Super app. |
user screen |
EVAMP |
P |
Apps |
|
| 21299 |
4:-Advance billing for UphoneApp IOS VAS Urdu |
1 :-User should be able to login to the PTCL Super app. |
user screen |
EVAMP |
P |
Apps |
|
| 21299 |
5:-Advance billing for UphoneApp Android Package English |
1 :-Speed bolton should be visible for PTCL users only. |
Speed bolton should be visible |
EVAMP |
P |
Apps |
|
| 21299 |
6:-Advance billing for UphoneApp Android Package Urdu |
1 :-Speed bolton should be visible for PTCL users only. |
Speed bolton should be visible for PTCL |
EVAMP |
P |
Apps |
|
| 21299 |
7:-Advance billing for UphoneApp IOS Package Urdu |
1 :-Speed bolton should be visible for PTCL users only. |
Speed bolton should be visible for PTCL |
EVAMP |
P |
Apps |
|
| 21299 |
8:-Advance billing for UphoneApp IOS Package English |
1 :-Speed bolton should not be visible for Ufone users. |
Speed bolton should be visible for PTCL |
EVAMP |
P |
Apps |
|
| 21299 |
1:-Advance billing for UphoneApp Android VAS English |
2 :-After successful login user should be able to redirected to the dashboard screen. |
|
EVAMP |
P |
Apps |
|
| 21299 |
2:-Advance billing for UphoneApp IOS VAS English |
2 :-After successful login user should be able to redirected to the dashboard screen. |
|
EVAMP |
P |
Apps |
|
| 21299 |
3:-Advance billing for UphoneApp Android VAS Urdu |
2 :-After successful login user should be able to redirected to the dashboard screen. |
|
EVAMP |
P |
Apps |
|
| 21299 |
4:-Advance billing for UphoneApp IOS VAS Urdu |
2 :-After successful login user should be able to redirected to the dashboard screen. |
|
EVAMP |
P |
Apps |
|
| 21299 |
5:-Advance billing for UphoneApp Android Package English |
2 :-Speed bolton should not be visible for Ufone users. |
|
EVAMP |
P |
Apps |
|
| 21299 |
6:-Advance billing for UphoneApp Android Package Urdu |
2 :-Speed bolton should not be visible for Ufone users. |
|
EVAMP |
P |
Apps |
|
| 21299 |
7:-Advance billing for UphoneApp IOS Package Urdu |
2 :-Speed bolton should not be visible for Ufone users. |
|
EVAMP |
P |
Apps |
|
| 21299 |
8:-Advance billing for UphoneApp IOS Package English |
2 :-Speed bolton should be visible for ptcl/flashfiber profiles as secondary profiles |
|
EVAMP |
P |
Apps |
|
| 21299 |
1:-Advance billing for UphoneApp Android VAS English |
5 :-VAS menu should be visible for PTCL/flashfiber |
|
EVAMP |
P |
Apps |
|
| 21299 |
2:-Advance billing for UphoneApp IOS VAS English |
5 :-VAS menu should be visible for PTCL/flashfiber |
|
EVAMP |
P |
Apps |
|
| 21299 |
3:-Advance billing for UphoneApp Android VAS Urdu |
5 :-VAS menu should be visible for PTCL/flashfiber |
|
EVAMP |
P |
Apps |
|
| 21299 |
4:-Advance billing for UphoneApp IOS VAS Urdu |
5 :-VAS menu should be visible for PTCL/flashfiber |
|
EVAMP |
P |
Apps |
|
| 21299 |
5:-Advance billing for UphoneApp Android Package English |
5 :-User should be able to see speed boltons displaying on banner |
|
EVAMP |
P |
Apps |
|
| 21299 |
6:-Advance billing for UphoneApp Android Package Urdu |
5 :-User should be able to see speed boltons displaying on banner |
|
EVAMP |
P |
Apps |
|
| 21299 |
7:-Advance billing for UphoneApp IOS Package Urdu |
5 :-User should be able to see speed boltons displaying on banner |
|
EVAMP |
P |
Apps |
|
| 21299 |
8:-Advance billing for UphoneApp IOS Package English |
5 :-All speed boltons should be clickable and user should be redirected to details screen |
|
EVAMP |
P |
Apps |
|
| 21299 |
1:-Advance billing for UphoneApp Android VAS English |
3 :-VAS section should be visible to the user in quick menus. |
|
EVAMP |
P |
Apps |
|
| 21299 |
2:-Advance billing for UphoneApp IOS VAS English |
3 :-VAS section should be visible to the user in quick menus. |
|
EVAMP |
P |
Apps |
|
| 21299 |
3:-Advance billing for UphoneApp Android VAS Urdu |
3 :-VAS section should be visible to the user in quick menus. |
|
EVAMP |
P |
Apps |
|
| 21299 |
4:-Advance billing for UphoneApp IOS VAS Urdu |
3 :-VAS section should be visible to the user in quick menus. |
|
EVAMP |
P |
Apps |
|
| 21299 |
5:-Advance billing for UphoneApp Android Package English |
3 :-Speed bolton should be visible for ptcl/flashfiber profiles as secondary profiles |
|
EVAMP |
P |
Apps |
|
| 21299 |
6:-Advance billing for UphoneApp Android Package Urdu |
3 :-Speed bolton should be visible for ptcl/flashfiber profiles as secondary profiles |
|
EVAMP |
P |
Apps |
|
| 21299 |
7:-Advance billing for UphoneApp IOS Package Urdu |
3 :-Speed bolton should be visible for ptcl/flashfiber profiles as secondary profiles |
|
EVAMP |
P |
Apps |
|
| 21299 |
8:-Advance billing for UphoneApp IOS Package English |
3 :-Speed bolton banner should be shown below "My Number" menus |
|
EVAMP |
P |
Apps |
|
| 21299 |
1:-Advance billing for UphoneApp Android VAS English |
4 :-User should be redirected to VAS screen by clicking on VAS icon. |
|
EVAMP |
P |
Apps |
|
| 21299 |
2:-Advance billing for UphoneApp IOS VAS English |
4 :-User should be redirected to VAS screen by clicking on VAS icon. |
|
EVAMP |
P |
Apps |
|
| 21299 |
3:-Advance billing for UphoneApp Android VAS Urdu |
4 :-User should be redirected to VAS screen by clicking on VAS icon. |
|
EVAMP |
P |
Apps |
|
| 21299 |
4:-Advance billing for UphoneApp IOS VAS Urdu |
4 :-User should be redirected to VAS screen by clicking on VAS icon. |
|
EVAMP |
P |
Apps |
|
| 21299 |
5:-Advance billing for UphoneApp Android Package English |
4 :-Speed bolton banner should be shown below "My Number" menus |
|
EVAMP |
P |
Apps |
|
| 21299 |
6:-Advance billing for UphoneApp Android Package Urdu |
4 :-Speed bolton banner should be shown below "My Number" menus |
|
EVAMP |
P |
Apps |
|
| 21299 |
7:-Advance billing for UphoneApp IOS Package Urdu |
4 :-Speed bolton banner should be shown below "My Number" menus |
|
EVAMP |
P |
Apps |
|
| 21299 |
8:-Advance billing for UphoneApp IOS Package English |
4 :-User should be able to see speed boltons displaying on banner |
|
EVAMP |
P |
Apps |
|
| 21299 |
5:-Advance billing for UphoneApp Android Package English |
6 :-All speed boltons should be clickable and user should be redirected to details screen |
|
EVAMP |
P |
Apps |
|
| 21299 |
6:-Advance billing for UphoneApp Android Package Urdu |
6 :-All speed boltons should be clickable and user should be redirected to details screen |
|
EVAMP |
P |
Apps |
|
| 21299 |
7:-Advance billing for UphoneApp IOS Package Urdu |
6 :-All speed boltons should be clickable and user should be redirected to details screen |
|
EVAMP |
P |
Apps |
|
| 21299 |
8:-Advance billing for UphoneApp IOS Package English |
6 :-User should be able to subscribe speed bolton from details screen |
|
EVAMP |
P |
Apps |
|
| 21299 |
5:-Advance billing for UphoneApp Android Package English |
7 :-User should be able to subscribe speed bolton from details screen |
|
EVAMP |
P |
Apps |
|
| 21299 |
6:-Advance billing for UphoneApp Android Package Urdu |
7 :-User should be able to subscribe speed bolton from details screen |
|
EVAMP |
P |
Apps |
|
| 21299 |
7:-Advance billing for UphoneApp IOS Package Urdu |
7 :-User should be able to subscribe speed bolton from details screen |
|
EVAMP |
P |
Apps |
|
| 21299 |
8:-Advance billing for UphoneApp IOS Package English |
7 :-On Vas screen, all speed boltons should be displayed on swipe. |
|
EVAMP |
P |
Apps |
|
| 21299 |
5:-Advance billing for UphoneApp Android Package English |
9 :-User should be redirected to "Speed Boltons" screen by clicking on "view all" |
|
EVAMP |
P |
Apps |
|
| 21299 |
6:-Advance billing for UphoneApp Android Package Urdu |
9 :-User should be redirected to "Speed Boltons" screen by clicking on "view all" |
|
EVAMP |
P |
Apps |
|
| 21299 |
7:-Advance billing for UphoneApp IOS Package Urdu |
9 :-User should be redirected to "Speed Boltons" screen by clicking on "view all" |
|
EVAMP |
P |
Apps |
|
| 21299 |
8:-Advance billing for UphoneApp IOS Package English |
9 :-Speed Boltons offer should be displayed in the list |
|
EVAMP |
P |
Apps |
|
| 21299 |
5:-Advance billing for UphoneApp Android Package English |
8 :-On Vas screen, all speed boltons should be displayed on swipe. |
|
EVAMP |
P |
Apps |
|
| 21299 |
6:-Advance billing for UphoneApp Android Package Urdu |
8 :-On Vas screen, all speed boltons should be displayed on swipe. |
|
EVAMP |
P |
Apps |
|
| 21299 |
7:-Advance billing for UphoneApp IOS Package Urdu |
8 :-On Vas screen, all speed boltons should be displayed on swipe. |
|
EVAMP |
P |
Apps |
|
| 21299 |
8:-Advance billing for UphoneApp IOS Package English |
8 :-User should be redirected to "Speed Boltons" screen by clicking on "view all" |
|
EVAMP |
P |
Apps |
|
| 21299 |
5:-Advance billing for UphoneApp Android Package English |
10 :-Speed Boltons offer should be displayed in the list |
|
EVAMP |
P |
Apps |
|
| 21299 |
6:-Advance billing for UphoneApp Android Package Urdu |
10 :-Speed Boltons offer should be displayed in the list |
|
EVAMP |
P |
Apps |
|
| 21299 |
7:-Advance billing for UphoneApp IOS Package Urdu |
10 :-Speed Boltons offer should be displayed in the list |
|
EVAMP |
P |
Apps |
|
| 21299 |
8:-Advance billing for UphoneApp IOS Package English |
10 :-Below details should be shown for each speed bolton:
i. Name
ii. Price
iii. Detail
iv. Learn more option
v. Subscribe button |
|
EVAMP |
P |
Apps |
|
| 21299 |
5:-Advance billing for UphoneApp Android Package English |
11 :-Below details should be shown for each speed bolton:
i. Name
ii. Price
iii. Detail
iv. Learn more option
v. Subscribe button |
|
EVAMP |
P |
Apps |
|
| 21299 |
6:-Advance billing for UphoneApp Android Package Urdu |
11 :-Below details should be shown for each speed bolton:
i. Name
ii. Price
iii. Detail
iv. Learn more option
v. Subscribe button |
|
EVAMP |
P |
Apps |
|
| 21299 |
7:-Advance billing for UphoneApp IOS Package Urdu |
11 :-Below details should be shown for each speed bolton:
i. Name
ii. Price
iii. Detail
iv. Learn more option
v. Subscribe button |
|
EVAMP |
P |
Apps |
|
| 21299 |
8:-Advance billing for UphoneApp IOS Package English |
11 :-When user clicks on "Learn More" button, Speed bolton details screen should be displayed with below:
i. Banner at the top
ii. Speed Bolton name
iii. Price
iv. Overview section
v. Subscribe button |
|
EVAMP |
P |
Apps |
|
| 21299 |
5:-Advance billing for UphoneApp Android Package English |
13 :-User should be able to click on Subscribe button. |
|
EVAMP |
P |
Apps |
|
| 21299 |
6:-Advance billing for UphoneApp Android Package Urdu |
13 :-User should be able to click on Subscribe button. |
|
EVAMP |
P |
Apps |
|
| 21299 |
7:-Advance billing for UphoneApp IOS Package Urdu |
13 :-User should be able to click on Subscribe button. |
|
EVAMP |
P |
Apps |
|
| 21299 |
8:-Advance billing for UphoneApp IOS Package English |
13 :-Confirmation bottom sheet with "Cancel" and "Yes" button should be displayed on clicking subscribe button |
|
EVAMP |
P |
Apps |
|
| 21299 |
5:-Advance billing for UphoneApp Android Package English |
12 :-When user clicks on "Learn More" button, Speed bolton details screen should be displayed with below:
i. Banner at the top
ii. Speed Bolton name
iii. Price
iv. Overview section
v. Subscribe button |
|
EVAMP |
P |
Apps |
|
| 21299 |
6:-Advance billing for UphoneApp Android Package Urdu |
12 :-When user clicks on "Learn More" button, Speed bolton details screen should be displayed with below:
i. Banner at the top
ii. Speed Bolton name
iii. Price
iv. Overview section
v. Subscribe button |
|
EVAMP |
P |
Apps |
|
| 21299 |
7:-Advance billing for UphoneApp IOS Package Urdu |
12 :-When user clicks on "Learn More" button, Speed bolton details screen should be displayed with below:
i. Banner at the top
ii. Speed Bolton name
iii. Price
iv. Overview section
v. Subscribe button |
|
EVAMP |
P |
Apps |
|
| 21299 |
8:-Advance billing for UphoneApp IOS Package English |
12 :-User should be able to click on Subscribe button. |
|
EVAMP |
P |
Apps |
|
| 21299 |
5:-Advance billing for UphoneApp Android Package English |
14 :-Confirmation bottom sheet with "Cancel" and "Yes" button should be displayed on clicking subscribe button |
|
EVAMP |
P |
Apps |
|
| 21299 |
6:-Advance billing for UphoneApp Android Package Urdu |
14 :-Confirmation bottom sheet with "Cancel" and "Yes" button should be displayed on clicking subscribe button |
|
EVAMP |
P |
Apps |
|
| 21299 |
7:-Advance billing for UphoneApp IOS Package Urdu |
14 :-Confirmation bottom sheet with "Cancel" and "Yes" button should be displayed on clicking subscribe button |
|
EVAMP |
P |
Apps |
|
| 21299 |
8:-Advance billing for UphoneApp IOS Package English |
14 :-Confirmation bottom sheet should be closed when user clicks on Cancel button |
|
EVAMP |
P |
Apps |
|
| 21299 |
5:-Advance billing for UphoneApp Android Package English |
15 :-Confirmation bottom sheet should be closed when user clicks on Cancel button |
|
EVAMP |
P |
Apps |
|
| 21299 |
6:-Advance billing for UphoneApp Android Package Urdu |
15 :-Confirmation bottom sheet should be closed when user clicks on Cancel button |
|
EVAMP |
P |
Apps |
|
| 21299 |
7:-Advance billing for UphoneApp IOS Package Urdu |
15 :-Confirmation bottom sheet should be closed when user clicks on Cancel button |
|
EVAMP |
P |
Apps |
|
| 21299 |
5:-Advance billing for UphoneApp Android Package English |
16 :-"Success" bottom sheet should be displayed by clicking on Yes button in confirmation bottom sheet. |
|
EVAMP |
P |
Apps |
|
| 21299 |
6:-Advance billing for UphoneApp Android Package Urdu |
16 :-"Success" bottom sheet should be displayed by clicking on Yes button in confirmation bottom sheet. |
|
EVAMP |
P |
Apps |
|
| 21299 |
7:-Advance billing for UphoneApp IOS Package Urdu |
16 :-"Success" bottom sheet should be displayed by clicking on Yes button in confirmation bottom sheet. |
|
EVAMP |
P |
Apps |
|
| 21299 |
5:-Advance billing for UphoneApp Android Package English |
17 :-User should be redirected to home screen by clicking on "continue" button showing on the success bottom sheet. |
|
EVAMP |
P |
Apps |
|
| 21299 |
6:-Advance billing for UphoneApp Android Package Urdu |
17 :-User should be redirected to home screen by clicking on "continue" button showing on the success bottom sheet. |
|
EVAMP |
P |
Apps |
|
| 21299 |
7:-Advance billing for UphoneApp IOS Package Urdu |
17 :-User should be redirected to home screen by clicking on "continue" button showing on the success bottom sheet. |
|
EVAMP |
P |
Apps |
|
| 21299 |
7:-Advance billing for UphoneApp IOS Package Urdu |
18 :-Speed bolton should be visible for PTCL users only. |
|
EVAMP |
P |
Apps |
|
| 21449 |
1:-Digitalization Toolbox talk Risk Identifications card(TRIC) |
7 :-User resubmits a form assigned for resubmission by manager |
Form resubmitted successfully; dialog shows success message that form updated successfully; upon pressing ok user navigated to main screen |
PTCL |
P |
|
|
| 21449 |
1:-Digitalization Toolbox talk Risk Identifications card(TRIC) |
6 :-User checks submitted forms status |
List displays all forms submitted by user with status: Pending, Approved, Rejected, Resubmit |
PTCL |
P |
|
|
| 21449 |
1:-Digitalization Toolbox talk Risk Identifications card(TRIC) |
4 :-User fills three Urdu forms with mandatory fields |
User should be able to navigate through forms only if all mandatory fields are filled; errors if missing |
PTCL |
P |
|
|
| 21449 |
1:-Digitalization Toolbox talk Risk Identifications card(TRIC) |
3 :-User opens TRIC Form and fills Employee Details form
|
Next form (Urdu Form 1) should open |
PTCL |
P |
|
|
| 21449 |
1:-Digitalization Toolbox talk Risk Identifications card(TRIC) |
5 :-User uploads images (optional) and submits form
|
Form should be submitted successfully; dialog shows success message and Form ID; user navigated to main screen |
PTCL |
P |
|
|
| 21449 |
1:-Digitalization Toolbox talk Risk Identifications card(TRIC) |
2 :-User clicks TRIC icon on main screen
|
Two buttons displayed: 'TRIC Form' and 'Status Check' |
PTCL |
P |
|
|
| 21449 |
1:-Digitalization Toolbox talk Risk Identifications card(TRIC) |
1 :-User logs in to WIFI Analyzer
|
User should be logged in and main screen displayed |
PTCL |
P |
|
|
| 17243 |
1:-Consolidated bill register for B2B Product |
1 :-Consolidated Report included Cloud and Data products |
data will be pushed in fields |
PTCL |
F |
|
|
| 22011 |
1:-Auto Detection of TOS-POS Numbers and Billing Announcement at IVR |
5 :-Report Varification |
values should not be blank |
ExpertFlow |
P |
|
|
| 22011 |
1:-Auto Detection of TOS-POS Numbers and Billing Announcement at IVR
|
3 :-Mobile (Not Whitelisted, Check via Web Service)
|
Web service validation is triggered, related TOS/POS prompt plays if applicable, flow continues. |
ExpertFlow |
P |
|
|
| 22011 |
1:-Auto Detection of TOS-POS Numbers and Billing Announcement at IVR
|
4 :-Landline (General Validation)
|
Correct prompt plays depending on CLI validation path, flow continues as per design. |
ExpertFlow |
P |
|
|
| 22011 |
1:-Auto Detection of TOS-POS Numbers and Billing Announcement at IVR
|
2 :-Landline (Whitelisted in Supervisor Tool)
|
Supervisor tool validation succeeds, related prompt plays, no web service check. |
ExpertFlow |
P |
|
|
| 22011 |
1:-Auto Detection of TOS-POS Numbers and Billing Announcement at IVR
|
1 :-Calling from Mobile (OMO Number)
|
TOS/POS prompt is played based on web service status and flow continues. |
ExpertFlow |
P |
|
|
| 18798 |
1:-NTT Routing on SMP ref: 14305 |
1 :-To verify that when an SR is created under Technical Services, with a configured Trouble Ticket, undergoes an SMP Health Check for rectification. After rectification upon SMP Reopen the system correctly assigns the SR to the appropriate ABM and FT. |
SR should be on In Progress / SMP Reopen and is automatically assigned to the appropriate ABM and FT |
IBM |
P |
|
|
| 13928 |
1:-(Audit Objection) SALAM Event Tracking Log |
1 :-Verify log creation on item deletion |
Event can be seen on Log |
PTCL |
P |
|
|
| 13928 |
2:-(Audit Objection) CDT Event Tracking Log |
1 :-Verify log creation on user login
|
Event can be seen on Log |
PTCL |
P |
|
|
| 13928 |
3:-(Audit Objection) CorpWatch Event Tracking Log |
1 :-Verify log creation on user login
|
Event can be seen on Log |
PTCL |
P |
|
|
| 18798 |
1:-NTT Routing on SMP ref: 14305 |
2 :-To verify that when an SR is created under GPON Technical Services, with a configured Trouble Ticket, undergoes an SMP Health Check for rectification. After rectification upon SMP Reopen the system correctly assigns the SR to the appropriate ABM and FT. |
SR should be on In Progress / SMP Reopen and is automatically assigned to the appropriate ABM and FT. |
IBM |
P |
|
|
| 13928 |
1:-(Audit Objection) SALAM Event Tracking Log |
2 :-View log on content view |
Event can be seen on Log |
PTCL |
P |
|
|
| 13928 |
2:-(Audit Objection) CDT Event Tracking Log |
2 :-Verify log creation on inquiry update |
Event can be seen on Log |
PTCL |
P |
|
|
| 13928 |
3:-(Audit Objection) CorpWatch Event Tracking Log |
2 :-Verify log creation on password change
|
Event can be seen on Log |
PTCL |
P |
|
|
| 18798 |
1:-NTT Routing on SMP ref: 14305 |
3 :-when an SR is created under Technical Services, with a configured Trouble Ticket, undergoes an SMP Health Check for rectification. After rectification SR goes to OBD, upon customer reopen the system correctly assigns the SR to the appropriate ABM and FT. |
SR in Progress Reopened and is automatically assigned ABM and FT. |
IBM |
P |
|
|
| 13928 |
1:-(Audit Objection) SALAM Event Tracking Log |
3 :-Verify log creation on content update |
Event can be seen on Log |
PTCL |
P |
|
|
| 13928 |
2:-(Audit Objection) CDT Event Tracking Log |
3 :-Verify log creation on inquiry creation |
Event can be seen on Log |
PTCL |
P |
|
|
| 13928 |
3:-(Audit Objection) CorpWatch Event Tracking Log |
3 :-Verify log creation on service call creation
|
Event can be seen on Log |
PTCL |
P |
|
|
| 18798 |
1:- |
4 :-To verify that when an SR is created under GPON Technical Services, with a configured Trouble Ticket, undergoes an SMP Health Check for rectification. After rectification SR goes to OBD, upon customer reopen the system correctly assigns the SR to the appropriate ABM and F |
SR in Progress Reopened and is automatically assigned ABM and FT. |
IBM |
P |
77 |
|