i2i Core – Carrier-Grade User & Operations Guide (Draft) Draft guide created from captured UI states. Review & enrich for production release. AAA & Authentication Routes under: aaa aaa > radius > clientg > all aaa > radius > clientg > all Route: aaa/radius/clientg/all URL: https://admin.myslbb.com/#/aaa/radius/clientg/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, AAA, Radius, Radius Client Group, New Client Group, Default Rad Group, SmartLink Dandy BNG Group, SmartLink Mikrotik Group, Sunrise WiFi Mikrotik Group Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/aaa/radius/clientg/all Images uploading… default Captured URL: https://admin.myslbb.com/#/aaa/radius/clientg/all Images uploading… create_new Captured URL: https://admin.myslbb.com/#/aaa/radius/clientg/all Images uploading… create_new Captured URL: https://admin.myslbb.com/#/aaa/radius/clientg/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/aaa/radius/clientg/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/aaa/radius/clientg/all Images uploading… aaa > radius > clients > addclient aaa > radius > clients > addclient Route: aaa/radius/clients/addclient URL: https://admin.myslbb.com/#/aaa/radius/clients/addclient Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: identity, IP Address For Client, MAC Address For Client, Client Group, Client Profile, Shared Secret, CoA/DM Shared Secret, Request Timeout (ms), CoA Port, CoA Timeout (ms), Accounting Interval (s), Share Across Organization, Description, Mac Id attribute of the client, NAS Port Id Attribute, Option 82 Attribute, API Type Actions detected: Auto, Close, AAA, Radius, Trusted Client, Cancel, Create Radius Client Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/aaa/radius/clients/addclient Images uploading… create_new Captured URL: https://admin.myslbb.com/#/aaa/radius/clients/addclient Images uploading… aaa > radius > clients > l aaa > radius > clients > l Route: aaa/radius/clients/l URL: https://admin.myslbb.com/#/aaa/radius/clients/l Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, AAA, Radius, Trusted Client, New Radius Client, Relaod Cache, 103.5.187.18, 49.143.252.226, 49.143.252.59, 49.143.252.60, 49.143.255.172, 49.143.255.173, 49.143.255.226 Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/aaa/radius/clients/l Images uploading… default Captured URL: https://admin.myslbb.com/#/aaa/radius/clients/l Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/aaa/radius/clients/l Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/aaa/radius/clients/l Images uploading… aaa > radius > node > l aaa > radius > node > l Route: aaa/radius/node/l URL: https://admin.myslbb.com/#/aaa/radius/node/l Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, AAA, Radius, Node (Interface), New Radius Server Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/aaa/radius/node/l Images uploading… create_new Captured URL: https://admin.myslbb.com/#/aaa/radius/node/l Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/aaa/radius/node/l Images uploading… aaa > radius > sesdis > all aaa > radius > sesdis > all Route: aaa/radius/sesdis/all URL: https://admin.myslbb.com/#/aaa/radius/sesdis/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, AAA, Radius, Session Disconnection, Session Disconnect, New Batch, 3/2/2026, Username, 2/2/2026, 1/2/2026, 31/1/2026, 30/1/2026, 29/1/2026, 28/1/2026, 27/1/2026, 26/1/2026, 25/1/2026, 24/1/2026, 23/1/2026 Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/aaa/radius/sesdis/all Images uploading… create_new Captured URL: https://admin.myslbb.com/#/aaa/radius/sesdis/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/aaa/radius/sesdis/all Images uploading… aaa > radius > set aaa > radius > set Route: aaa/radius/set URL: https://admin.myslbb.com/#/aaa/radius/set Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, AAA, Radius, Settings Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/aaa/radius/set Images uploading… Billing & Charging Routes under: bill bill > area > add bill > area > add Route: bill/area/add URL: https://admin.myslbb.com/#/bill/area/add Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Name, Description, Bill Base Month, Bill Day Actions detected: Auto, Close, Billing, Billing Area, Create Billing Area Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/bill/area/add Images uploading… bill > area > all bill > area > all Route: bill/area/all URL: https://admin.myslbb.com/#/bill/area/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Billing, Billing Area, Add Billing Area, Clear, BLA/-0001, Default Billing Area Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/bill/area/all Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/bill/area/all Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/bill/area/all Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/bill/area/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/bill/area/all Images uploading… bill > deposit > add bill > deposit > add Route: bill/deposit/add URL: https://admin.myslbb.com/#/bill/deposit/add Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Deposit Name, Deposit Type Actions detected: Auto, Close, Billing, Deposit Management, Save, Cancel Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/bill/deposit/add Images uploading… bill > deposit > all bill > deposit > all Route: bill/deposit/all URL: https://admin.myslbb.com/#/bill/deposit/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Billing, Deposit Management, Add Deposit, Clear Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/bill/deposit/all Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/bill/deposit/all Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/bill/deposit/all Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/bill/deposit/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/bill/deposit/all Images uploading… bill > proc > all bill > proc > all Route: bill/proc/all URL: https://admin.myslbb.com/#/bill/proc/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Select Date, Select Billing Area Actions detected: Auto, Close, Billing, Billing Process, Clear Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/bill/proc/all Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/bill/proc/all Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/bill/proc/all Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/bill/proc/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/bill/proc/all Images uploading… bill > serbill > all bill > serbill > all Route: bill/serbill/all URL: https://admin.myslbb.com/#/bill/serbill/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Search Field, Search Type Actions detected: Auto, Close, Billing, Billing Area, Clear, Cult Fit, sybr_hiranandani_cult, abdul rehaman rashid maredia, abdul22, r.e r.e, r.e, dharamshingh sonar, dharamshingh22, vijay panchal, s_vijay, sanjay rana, rana22, rahul sharma, rahulsharma22, Khan Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/bill/serbill/all Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/bill/serbill/all Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/bill/serbill/all Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/bill/serbill/all Images uploading… bill > serdoc > all bill > serdoc > all Route: bill/serdoc/all URL: https://admin.myslbb.com/#/bill/serdoc/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Select Partner, Date Range, Billing Type Actions detected: Auto, Close, Billing, Documents List, Clear Filters Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/bill/serdoc/all Images uploading… default Captured URL: https://admin.myslbb.com/#/bill/serdoc/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/bill/serdoc/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/bill/serdoc/all Images uploading… BILLING Routes under: billing billing > summary billing > summary Route: billing/summary URL: https://admin.myslbb.com/#/billing/summary Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Financial Year, Invoice Type Actions detected: Auto, Close, Billing, Apply, Clear, August 2025, September 2025, October 2025, November 2025, December 2025, January 2026, February 2026 Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/billing/summary Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/billing/summary Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/billing/summary Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/billing/summary Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/billing/summary Images uploading… Customer & Subscriber Management Routes under: cust cust > accesslog > adv cust > accesslog > adv Route: cust/accesslog/adv URL: https://admin.myslbb.com/#/cust/accesslog/adv Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Customer, Access Request, Refresh Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/cust/accesslog/adv Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/cust/accesslog/adv Images uploading… cust > accesslog > all cust > accesslog > all Route: cust/accesslog/all URL: https://admin.myslbb.com/#/cust/accesslog/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Customer, Access Request, Refresh Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/cust/accesslog/all Images uploading… default Captured URL: https://admin.myslbb.com/#/cust/accesslog/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/cust/accesslog/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/cust/accesslog/all Images uploading… cust > acct > list cust > acct > list Route: cust/acct/list URL: https://admin.myslbb.com/#/cust/acct/list Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Headings detected: Search Customers Fields detected: Search Field, Search Type Actions detected: Auto, Close, Customer, Advanced Search, New Customer, Bulk Operations on Selected Accounts, Clear, Bulk Operations, s_vijay, vijay panchal, khan420, Khan, DSC_laxmipatil, Laxmi Patil, s_proficientsm, Proficientsm, DSC_rajeshchauhan, Rajesh Chavhan, 14b602, Prashant Sahu Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/cust/acct/list Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/cust/acct/list Images uploading… ui_tab_2 Captured URL: https://admin.myslbb.com/#/cust/acct/list Images uploading… ui_tab_3 Captured URL: https://admin.myslbb.com/#/cust/acct/list Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/cust/acct/list Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/cust/acct/list Images uploading… common_tab_3 Captured URL: https://admin.myslbb.com/#/cust/acct/list Images uploading… common_tab_4 Captured URL: https://admin.myslbb.com/#/cust/acct/list Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/cust/acct/list Images uploading… cust > acct > vacct > 1001286 > 1287 > findetdv cust > acct > vacct > 1001286 > 1287 > findetdv Route: cust/acct/vacct/1001286/1287/findetdv URL: https://admin.myslbb.com/#/cust/acct/vacct/1001286/1287/findetdv Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Document Type, Status, Date Range Actions detected: Auto, Close, Customer, Service Account, View, Transactions, Edit, Change Status, Renew, Cancel Plan, Reset MAC, Change Password, Live Monitoring, eCAF, Apply Filter, Clear Filter, Add Debit Note, Add Credit Note Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots drilldown_one_item Captured URL: https://admin.myslbb.com/#/cust/acct/vacct/1001286/1287/findetdv Images uploading… cust > actsess > all cust > actsess > all Route: cust/actsess/all URL: https://admin.myslbb.com/#/cust/actsess/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Search Field Actions detected: Auto, Close, Customer, Active Session, Refresh, Clear, sn19a1002, bn3x16x16, snsuraj1_pc, bn17x6x6, sl_suryakant, tnrch, lacreme_301, maplea_1301, sn15a103, rakeshsolanki, kanakia_c1404, inyatshaikh, baalwadi, bn17x4x7 Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/cust/actsess/all Images uploading… default Captured URL: https://admin.myslbb.com/#/cust/actsess/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/cust/actsess/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/cust/actsess/all Images uploading… cust > autorenew > all cust > autorenew > all Route: cust/autorenew/all URL: https://admin.myslbb.com/#/cust/autorenew/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Type Actions detected: Auto, Close, Customer, Auto Renewal Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/cust/autorenew/all Images uploading… create_new Captured URL: https://admin.myslbb.com/#/cust/autorenew/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/cust/autorenew/all Images uploading… cust > bulkrenew > all cust > bulkrenew > all Route: cust/bulkrenew/all URL: https://admin.myslbb.com/#/cust/bulkrenew/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Customer, Bulk Renewal, Create Bulk Renewal Batch Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/cust/bulkrenew/all Images uploading… default Captured URL: https://admin.myslbb.com/#/cust/bulkrenew/all Images uploading… create_new Captured URL: https://admin.myslbb.com/#/cust/bulkrenew/all Images uploading… create_new Captured URL: https://admin.myslbb.com/#/cust/bulkrenew/all Images uploading… cust > cpo > banner mgmt cust > cpo > banner mgmt Route: cust/cpo/banner-mgmt URL: https://admin.myslbb.com/#/cust/cpo/banner-mgmt Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Customer, Portal Setting, Upload Image Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots ui_tab_3 Captured URL: https://admin.myslbb.com/#/cust/cpo/banner-mgmt Images uploading… common_tab_3 Captured URL: https://admin.myslbb.com/#/cust/cpo/banner-mgmt Images uploading… common_tab_4 Captured URL: https://admin.myslbb.com/#/cust/cpo/banner-mgmt Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/cust/cpo/banner-mgmt Images uploading… cust > cpo > pfv cust > cpo > pfv Route: cust/cpo/pfv URL: https://admin.myslbb.com/#/cust/cpo/pfv Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Customer, Portal Setting, Edit Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/cust/cpo/pfv Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/cust/cpo/pfv Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/cust/cpo/pfv Images uploading… cust > cpo > ppv cust > cpo > ppv Route: cust/cpo/ppv URL: https://admin.myslbb.com/#/cust/cpo/ppv Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Customer, Portal Setting, Add Plans Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots ui_tab_2 Captured URL: https://admin.myslbb.com/#/cust/cpo/ppv Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/cust/cpo/ppv Images uploading… cust > lead > all cust > lead > all Route: cust/lead/all URL: https://admin.myslbb.com/#/cust/lead/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Show All Closed Lead Actions detected: Auto, Close, Customer, Customer Lead, New Customer Lead, Clear Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/cust/lead/all Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/cust/lead/all Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/cust/lead/all Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/cust/lead/all Images uploading… create_new Captured URL: https://admin.myslbb.com/#/cust/lead/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/cust/lead/all Images uploading… cust > lealineacct > list > all cust > lealineacct > list > all Route: cust/lealineacct/list/all URL: https://admin.myslbb.com/#/cust/lealineacct/list/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Customer, Group Account, New Group Account, Add New Service Account, Clear Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/cust/lealineacct/list/all Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/cust/lealineacct/list/all Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/cust/lealineacct/list/all Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/cust/lealineacct/list/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/cust/lealineacct/list/all Images uploading… cust > lealineacct > postpaid > create > 0 cust > lealineacct > postpaid > create > 0 Route: cust/lealineacct/postpaid/create/0 URL: https://admin.myslbb.com/#/cust/lealineacct/postpaid/create/0 Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Group Name, Group Segment, Group Phone, Group Email, Group Charge Type, Group Category Type, Person Name, Person Phone, Person Email, CAFNO, Address Line 1, Address Line 2, Pincode, Sub District, District, State, Tax Zone, Billing Area Actions detected: Auto, Close, Customer, Group Account, Create Group Account, Cancel Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/cust/lealineacct/postpaid/create/0 Images uploading… cust > set cust > set Route: cust/set URL: https://admin.myslbb.com/#/cust/set Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Customer, Settings Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/cust/set Images uploading… Customer & Subscriber Management – Overview Customer & Subscriber Management – Overview Product: i2i Core OSS/BSS Company: i2i Tech Services Private Limited Purpose The Customer & Subscriber Management module is the foundation of i2i Core OSS/BSS. It establishes the authoritative identity and ownership model used across AAA, provisioning, billing, reporting, and audit flows. Conceptual Model Customer : Legal/commercial entity (individual/organization/partner). Account : Billing & service container under a customer. Service : A provisioned offering (broadband, leased line, add-ons) owned by an account. Subscriber : End endpoint/identity consuming the service (credentials + network identifiers). Lifecycle Create Customer → Create Account Attach Service(s) to Account Create Subscriber identity and map it to service Activate → Operate (Modify/Suspend/Resume) → Terminate Operational Principles Data integrity first : Avoid duplicates and uncontrolled edits. Controlled state transitions : Changes must be lifecycle-aware. Downstream impact awareness : Customer data drives AAA & billing behavior. Auditability : All changes must be traceable to a user and time. Role Responsibilities L1/NOC : Create customers/accounts, routine updates, status checks, basic lifecycle actions. L2 Ops : Validate AAA/provisioning dependencies, handle complex corrections safely. L3/Admin : Policy, configuration, integration, and defect triage. Screenshots Screenshots not yet added. Customer Creation & Classification Customer Creation & Classification Product: i2i Core OSS/BSS Company: i2i Tech Services Private Limited Purpose Customer creation establishes the legal and operational identity for all downstream workflows in i2i Core OSS/BSS. Classification determines policy eligibility, billing ownership, provisioning constraints, and reporting visibility. When to Create a New Customer New legal/commercial entity onboarding (residential, enterprise, partner/reseller). Contractually separate ownership requiring distinct invoicing/compliance. When NOT to Create a New Customer Additional services for the same entity (create a new Account or Service ). New location under the same agreement (use account/service mapping as per policy). Classification Guidance Residential : Standard policies, minimal exceptions. Enterprise : SLA-sensitive, multi-service/multi-site, approvals often required. Partner/Reseller : Revenue-share/settlement logic; restricted operational permissions. Mandatory Data & Verification Customer name (legal), classification, verified contact details. Installation & billing address mapping (as applicable). Uniqueness checks (avoid duplicates). Validation & Controls Mandatory fields enforced; role-based permissions apply. Classification changes should be restricted after dependent entities exist. All creation actions must be auditable. Downstream Impact Billing : invoicing entity, tax/compliance behavior, ownership. AAA : root ownership for subscriber identities and policy boundaries. Provisioning : service eligibility and lifecycle enforcement. Screenshots Screenshots not yet added. Account Creation & Billing Relationship Account Creation & Billing Relationship Product: i2i Core OSS/BSS Company: i2i Tech Services Private Limited Purpose Accounts represent the commercial and billing container under a customer. Accounts are used to group services, define billing ownership, and enforce policies such as billing cycle, credit controls, and operational constraints. When to Create a New Account Separate billing relationship required (different GST/tax entity, cycle, or payer). Multi-site enterprise requiring separate service grouping and reporting. Partner/reseller models where settlement and ownership boundaries differ. Key Attributes Billing owner and invoicing details Billing cycle / effective dates Payment terms / credit policy (if applicable) Account status (active/suspended/closed) Workflow Select the correct customer → Create Account Set billing ownership & cycle Validate address/tax/compliance data (if used) Save → Confirm account readiness for service attachment Validation & Safety Do not attach services to incorrect account; ownership impacts billing and reporting. Do not change billing cycle/effective date without approvals. Account closure must ensure services are terminated/archived per policy. Downstream Impact Billing : invoice generation, adjustments, and ledger grouping. Service : services inherit account ownership and constraints. Reporting : KPIs roll up by account/customer hierarchy. Screenshots Screenshots not yet added. Service Association & Ownership Service Association & Ownership Product: i2i Core OSS/BSS Company: i2i Tech Services Private Limited Purpose Services represent the deliverable offering mapped to an account. Service association defines entitlement, provisioning scope, AAA applicability, and chargeability. Ownership must remain unambiguous to avoid revenue leakage and provisioning conflicts. Service Ownership Rules A service must belong to exactly one Account at a time. Service identifiers must remain stable (IDs used by provisioning/AAA/billing). Ownership transfers require controlled workflow and audit trail. Workflow Open Account → Add/Attach Service Select service type/plan/profile (as per product configuration) Set activation/effective dates (if applicable) Validate mandatory attributes → Save Validation & Safety Confirm service type aligns with customer classification (residential vs enterprise vs partner). Confirm charging/rating applicability before activation. Do not edit service identifiers in production without escalation. Downstream Impact Provisioning : triggers activation workflows and network mapping. AAA : defines authorization scope and service entitlement. Billing : determines recurring/one-time charges and invoice mapping. Screenshots Screenshots not yet added. Subscriber Creation & Identity Mapping Subscriber Creation & Identity Mapping Product: i2i Core OSS/BSS Company: i2i Tech Services Private Limited Purpose Subscribers represent the operational endpoint identity consuming a service (credentials + network identifiers). Correct mapping ensures authentication success, accurate accounting, and consistent service state across systems. Identity Components Authentication identity : username/identifier used by AAA Authorization mapping : which service/plan/profile applies Network identifiers : MAC/VLAN/Circuit/Interface mapping where applicable Status : active/suspended/terminated aligned to lifecycle Workflow Open Service → Create Subscriber Assign identity/credentials per policy Map subscriber to service entitlement Validate uniqueness → Save Perform post-save validation (AAA/provisioning readiness) Validation & Safety Credentials must be unique within the defined domain/policy scope. Ensure correct plan/profile mapping; wrong mapping causes speed/policy mismatches. Any production credential reset should be auditable and approved. Troubleshooting Signals Authentication fails → check identity mapping and subscriber status Session starts but wrong policy → check service profile mapping Usage not visible → check accounting correlation and identifiers Screenshots Screenshots not yet added. Customer Search, Verification & Duplicate Prevention Customer Search, Verification & Duplicate Prevention Product: i2i Core OSS/BSS Company: i2i Tech Services Private Limited Purpose Search and verification reduces duplicate creation, prevents ownership errors, and ensures operational accuracy. This workflow must be executed before creating any new customer or account in production. Minimum Verification Checks Search by primary phone and email Search by identity reference (customer code/ID, document reference if used) Search by address keywords (when phone/email are unknown) Duplicate Prevention Rules Do not create a new customer if the same legal entity already exists. If multiple records exist, escalate for merge/dedup policy handling. Prefer updating verified contact fields rather than creating a second customer. Operational Workflow Search using strongest identifiers first (phone/email/customer ID). Open matching record and verify classification and active services. If match confirmed → proceed with account/service actions under the existing customer. If uncertain → escalate for verification before creation. Screenshots Screenshots not yet added. Customer Updates & Controlled Changes Customer Updates & Controlled Changes Product: i2i Core OSS/BSS Company: i2i Tech Services Private Limited Purpose Customer updates must be controlled because changes can impact billing, compliance communication, and operational routing. This page defines safe update practices and approval boundaries. Allowed Routine Updates (L1) Contact phone/email corrections (verified) Address corrections (as per SOP) Non-policy metadata updates (tags/notes if used) Restricted Updates (Require Approval / L2-L3) Customer classification changes (residential ↔ enterprise ↔ partner) Billing owner / invoicing identity changes Compliance identifiers used in invoices or regulatory reporting Safe Workflow Confirm you are editing the correct customer (ID verification). Review active services and accounts before changes. Apply minimal change; avoid bulk edits. Save and document reason/notes (as per policy). Common Risks Wrong customer edited → downstream billing/communication issues. Unapproved classification change → policy mismatches and audit risk. Screenshots Screenshots not yet added. Service Lifecycle Actions – Suspend / Resume Service Lifecycle Actions – Suspend / Resume Product: i2i Core OSS/BSS Company: i2i Tech Services Private Limited Purpose Suspension and resumption are controlled lifecycle actions used to enforce policy (non-payment, misuse, temporary hold) without full termination. These actions must be consistent across customer/account/service/subscriber states. When to Suspend Billing/collection policy trigger (as approved) Security/abuse policy trigger (as approved) Customer-requested temporary hold (if supported) When NOT to Suspend When service must be permanently disconnected (use termination workflow) When entity ownership is unclear (verify customer/account first) Operational Workflow Open the service → verify current status and active subscriber identity. Trigger Suspend → confirm reason code/notes (if required). Validate downstream: AAA should deny/limit session as per policy. For Resume: confirm approvals/collection closure → resume → validate sessions. Validation Confirm the correct service and subscriber mapping before action. Confirm the expected downstream enforcement behavior (AAA state). Record action reason for audit trail. Troubleshooting Service suspended but user still online → verify AAA session handling and session termination policy. Service resumed but cannot authenticate → verify subscriber status and mapping. Screenshots Screenshots not yet added. Service Termination / Disconnection & Data Retention Service Termination / Disconnection & Data Retention Product: i2i Core OSS/BSS Company: i2i Tech Services Private Limited Purpose Termination is the permanent lifecycle closure of a service/subscriber relationship. Termination must ensure charging is closed correctly, AAA access is revoked, and records are retained according to policy. Pre-termination Checks Confirm customer/account ownership and correct service selection. Confirm billing closure or final invoice policy (as applicable). Confirm provisioning rollback policy (if applicable). Operational Workflow Open service → validate active state and dependencies. Trigger Termination/Disconnection → select reason and effective date if used. Validate downstream: AAA access revoked, sessions terminated as per policy. Confirm billing closure behavior and data retention flags. Retention & Audit Operational records should remain queryable for audit for defined retention period. Do not hard-delete production entities unless explicitly approved and supported by policy. Common Issues Residual sessions after termination → check AAA session termination enforcement. Final invoice mismatch → check effective date and billing cycle alignment. Screenshots Screenshots not yet added. Common Operational Scenarios & Troubleshooting Common Operational Scenarios & Troubleshooting Product: i2i Core OSS/BSS Company: i2i Tech Services Private Limited Scenario A: Customer exists but onboarding fails Verify customer classification and mandatory data completeness. Verify account exists and is active. Verify service can be attached to that account per policy. Scenario B: Authentication fails after subscriber creation Verify subscriber is active and mapped to correct service/plan. Verify credential uniqueness and correct username format. Verify AAA policy assignment and service entitlement mapping. Scenario C: Wrong speed/policy applied Verify service plan/profile mapping. Verify subscriber is mapped to the intended service and not a stale record. Re-check effective dates and policy inheritance rules. Scenario D: Billing mismatch after ownership changes Verify account ownership and billing cycle/effective date alignment. Verify service is attached to the correct account. Escalate if correction requires ledger adjustments. Escalation Guidance L1 : Verify IDs, status, and basic mapping. L2 : Validate AAA/provisioning/billing dependencies and run corrective SOP. L3 : Policy/config/integration issues and suspected product defects. Screenshots Screenshots not yet added. Developer & Integrations Routes under: dev dev > netdev > addbysubnet dev > netdev > addbysubnet Route: dev/netdev/addbysubnet URL: https://admin.myslbb.com/#/dev/netdev/addbysubnet Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Device Type, Device Profile, Device Model, Device Group, Status, IP with Subnet mask Actions detected: Auto, Close, Network, Device, Cancel, Submit Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/dev/netdev/addbysubnet Images uploading… dev > netdev > all dev > netdev > all Route: dev/netdev/all URL: https://admin.myslbb.com/#/dev/netdev/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Search Field, Search Type Actions detected: Auto, Close, Network, Device, Add Servers Subnet, New Server, Clear, DBCG1DC4704D, DBCG1DC47055, DBCG1DC4705D, DBCG1DC47035, DBCG1DC4703D, DBCG1DC47065, DBCG1DC46ECD, DBCG1DC47025, DBCG1DC4701D, DBCG1DC46EC5, DBCG1DC46E8D, DBCG1DC46EA5, DBCG1DC46ED5 Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/dev/netdev/all Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/dev/netdev/all Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/dev/netdev/all Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/dev/netdev/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/dev/netdev/all Images uploading… dev > netdiscdev > all dev > netdiscdev > all Route: dev/netdiscdev/all URL: https://admin.myslbb.com/#/dev/netdiscdev/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Network, Discovered Device, Clear, 12345989DB29C3259, Auto Registration Failed, 12345989DB29C1169, 12345989DB29D0A99, 12345989DB29C1889, 12345989DB29D02C9, 12345989DB299D7E9, 12345989DB29A5029, 12345989DB299C549, 12345989DB29A47A9, 12345989DB29A4459, 12345989DB299C4F9, 12345989DB29A4FA9, 12345989DB299C2A9, DBCG1DC3A3B4 Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/dev/netdiscdev/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/dev/netdiscdev/all Images uploading… dev > settings > firm > all dev > settings > firm > all Route: dev/settings/firm/all URL: https://admin.myslbb.com/#/dev/settings/firm/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Network, Settings, Device Firmware, Add Firmware Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/dev/settings/firm/all Images uploading… create_new Captured URL: https://admin.myslbb.com/#/dev/settings/firm/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/dev/settings/firm/all Images uploading… dev > settings > mg > add dev > settings > mg > add Route: dev/settings/mg/add URL: https://admin.myslbb.com/#/dev/settings/mg/add Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Name, Description, Device Type, Activity Type, Activity, Execution Interval Actions detected: Auto, Close, Network, Settings, Monitoring Group, Add Device, Cancel, Submit Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/dev/settings/mg/add Images uploading… dev > settings > mg > all dev > settings > mg > all Route: dev/settings/mg/all URL: https://admin.myslbb.com/#/dev/settings/mg/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Network, Settings, Monitoring Group, New Monitoring Group, TR069 Power Monitoring Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/dev/settings/mg/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/dev/settings/mg/all Images uploading… dev > settings > model > add dev > settings > model > add Route: dev/settings/model/add URL: https://admin.myslbb.com/#/dev/settings/model/add Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Name *, Description, Model Number *, Model Vendor *, Device Type *, Status *, Select Device Model Image Actions detected: Auto, Close, Network, Settings, Model, Submit Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/dev/settings/model/add Images uploading… create_new Captured URL: https://admin.myslbb.com/#/dev/settings/model/add Images uploading… dev > settings > model > all dev > settings > model > all Route: dev/settings/model/all URL: https://admin.myslbb.com/#/dev/settings/model/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Network, Settings, Model, New Model, BDCM GP1705-2GV 0055B1 ONT Model, HWTC Router_123 40BB56 ONT Model, HWTC Router_789 00053B ONT Model, HWTC Snet-128s A68F06 ONT Model, PPCT PPCT 64FB92 ONT Model, Realtek HGU-V210-4AC 4CAE1C ONT Model, TP-Link IGD E0D362 ONT Model, TP-Link XC220-G3v DC6279 ONT Model, XPON SM009 XPON ONT Model Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/dev/settings/model/all Images uploading… default Captured URL: https://admin.myslbb.com/#/dev/settings/model/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/dev/settings/model/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/dev/settings/model/all Images uploading… dev > settings > profile > all dev > settings > profile > all Route: dev/settings/profile/all URL: https://admin.myslbb.com/#/dev/settings/profile/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Network, Settings, Profile, BDCM-GP1705-2GV-0055B1 Profile, Internet Gateway Device v1.0, HWTC-Router_123-40BB56 Profile, HWTC-Router_789-00053B Profile, HWTC-Snet-128s-A68F06 Profile, PPCT-PPCT-64FB92 Profile, Realtek-HGU-V210-4AC-4CAE1C Profile, TP-Link-IGD-E0D362 Profile, TP-Link-XC220-G3v-DC6279 Profile, XPON-SM009-XPON Profile Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/dev/settings/profile/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/dev/settings/profile/all Images uploading… dev > settings > rule > all dev > settings > rule > all Route: dev/settings/rule/all URL: https://admin.myslbb.com/#/dev/settings/rule/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Network, Settings, Device Association Rule Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/dev/settings/rule/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/dev/settings/rule/all Images uploading… dev > site > add dev > site > add Route: dev/site/add URL: https://admin.myslbb.com/#/dev/site/add Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Site Level *, Site Name *, Site Code, Status *, Physical Location *, Address Line 1 *, Address Line 2, Pincode, State, City, Latitude, Longitude Actions detected: Auto, Close, Network, Site, Cancel, Create Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/dev/site/add Images uploading… dev > site > all dev > site > all Route: dev/site/all URL: https://admin.myslbb.com/#/dev/site/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Network, Site, Add Site, Clear Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/dev/site/all Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/dev/site/all Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/dev/site/all Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/dev/site/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/dev/site/all Images uploading… HOME Routes under: home home home Route: home URL: https://admin.myslbb.com/#/home Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Retry Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/home Images uploading… default Captured URL: https://admin.myslbb.com/#/home Images uploading… default Captured URL: https://admin.myslbb.com/#/home Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/home Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/home Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/home Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/home Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/home Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/home Images uploading… Inventory & Resources Routes under: inv inv > dconf > model > 105 inv > dconf > model > 105 Route: inv/dconf/model/105 URL: https://admin.myslbb.com/#/inv/dconf/model/105 Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Inventory, Device Model, Add New Model, HGU-400-4AC, DBC Technologies, PPCT-All, PPCT, TP-Link-All, TP-Link, XPON-All, XPON, HWTC-All, HWTC, Realtek-All, Realtek, BDCM-All, BDCM Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/inv/dconf/model/105 Images uploading… create_new Captured URL: https://admin.myslbb.com/#/inv/dconf/model/105 Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/inv/dconf/model/105 Images uploading… inv > dconf > vendor > 104 inv > dconf > vendor > 104 Route: inv/dconf/vendor/104 URL: https://admin.myslbb.com/#/inv/dconf/vendor/104 Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Inventory, Vendor, New Vendor, DBC Technologies, PPCT, TP-Link, XPON, HWTC, Realtek, BDCM, Syrotech Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/inv/dconf/vendor/104 Images uploading… create_new Captured URL: https://admin.myslbb.com/#/inv/dconf/vendor/104 Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/inv/dconf/vendor/104 Images uploading… inv > device > modem > 103 inv > device > modem > 103 Route: inv/device/modem/103 URL: https://admin.myslbb.com/#/inv/device/modem/103 Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Inventory, Device Batch, New Device Batch, BAT00011, DBC Router 18-12-2025, BAT00010, Rajan Avasthi 18-12-2025, BAT00009, DBC 15-12-2025, BAT00008, DBC-04-12-2025, BAT00007, HGU-400-4AC_01, BAT00006, PPCT Auto Capture CPE, BAT00005, TP-Link Auto Capture CPE, BAT00004 Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/inv/device/modem/103 Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/inv/device/modem/103 Images uploading… inv > device > modem > 103 > add inv > device > modem > 103 > add Route: inv/device/modem/103/add URL: https://admin.myslbb.com/#/inv/device/modem/103/add Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Internet Service, IPTV, Both, Name, Select Vendor, Select Model, Description Actions detected: Auto, Close, Inventory, Device Batch, Download Sample CSV, Cancel, Create Device Batch Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/inv/device/modem/103/add Images uploading… inv > device > modemitm > 106 inv > device > modemitm > 106 Route: inv/device/modemitm/106 URL: https://admin.myslbb.com/#/inv/device/modemitm/106 Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Select Partner, Customer Actions detected: Auto, Close, Inventory, Device Item, Clear Filters, DBC Router 18-12-2025, DBCG1DC46F35, DBCG1DC46E8D, DBCG1DC46F75, DBCG1DC47075, DBCG1DC46E3D, DBCG1DC46E7D, DBCG1DC46F9D, DBCG1DC46EAD, DBCG1DC46ED5, DBCG1DC46DF5, DBCG1DC46FBD, DBCG1DC47005, DBCG1DC470A5, DBCG1DC4704D Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/inv/device/modemitm/106 Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/inv/device/modemitm/106 Images uploading… inv > ip > batch > 101 inv > ip > batch > 101 Route: inv/ip/batch/101 URL: https://admin.myslbb.com/#/inv/ip/batch/101 Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Inventory, IP Pool, Inventory Batch, New Batch, StarNet, Direct Static IP, JLR Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/inv/ip/batch/101 Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/inv/ip/batch/101 Images uploading… inv > ip > batch > 101 > add inv > ip > batch > 101 > add Route: inv/ip/batch/101/add URL: https://admin.myslbb.com/#/inv/ip/batch/101/add Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Name, Description, From (IP address), To (IP address), Trusted Client (Optional), Subnet Mask (Optional), Gateway IP (Optional), IP Type, Association Type Actions detected: Auto, Close, Inventory, IP Pool, Inventory Batch, Create Batch, Cancel Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/inv/ip/batch/101/add Images uploading… inv > ip > item inv > ip > item Route: inv/ip/item URL: https://admin.myslbb.com/#/inv/ip/item Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Inventory, IP Pool, Inventory Item, 103.5.184.192, 103.5.184.129, 103.5.184.130, 103.5.184.131, 103.5.184.132, 103.5.184.133, 103.5.184.134, 103.5.184.135, 103.5.184.136, 103.5.184.137, 103.5.184.138, 103.5.184.139, 103.5.184.140, 103.5.184.141, 103.5.184.142 Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/inv/ip/item Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/inv/ip/item Images uploading… inv > landlinem > landline > 101 inv > landlinem > landline > 101 Route: inv/landlinem/landline/101 URL: https://admin.myslbb.com/#/inv/landlinem/landline/101 Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Inventory, Landline Number Batch, New Landline Batch Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/inv/landlinem/landline/101 Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/inv/landlinem/landline/101 Images uploading… inv > landlinem > landline > 104 > add inv > landlinem > landline > 104 > add Route: inv/landlinem/landline/104/add URL: https://admin.myslbb.com/#/inv/landlinem/landline/104/add Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Name, Description Actions detected: Auto, Close, Inventory, Landline Number Batch, Download Sample CSV, Cancel, Create Landline Batch Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/inv/landlinem/landline/104/add Images uploading… inv > landlinem > landlinenumber > 102 inv > landlinem > landlinenumber > 102 Route: inv/landlinem/landlinenumber/102 URL: https://admin.myslbb.com/#/inv/landlinem/landlinenumber/102 Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Select Partner, Customer Actions detected: Auto, Close, Inventory, Landline Number, Clear Filters Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/inv/landlinem/landlinenumber/102 Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/inv/landlinem/landlinenumber/102 Images uploading… IPLM Routes under: iplm iplm > ipnode > l iplm > ipnode > l Route: iplm/ipnode/l URL: https://admin.myslbb.com/#/iplm/ipnode/l Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Mediation, IP Node, New Server, SmartLink Mediation Node, 49.143.255.165 Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/iplm/ipnode/l Images uploading… create_new Captured URL: https://admin.myslbb.com/#/iplm/ipnode/l Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/iplm/ipnode/l Images uploading… iplm > ipreqflw iplm > ipreqflw Route: iplm/ipreqflw URL: https://admin.myslbb.com/#/iplm/ipreqflw Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Mediation, IP Request Flows Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/iplm/ipreqflw Images uploading… iplm > pov iplm > pov Route: iplm/pov URL: https://admin.myslbb.com/#/iplm/pov Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Mediation Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/iplm/pov Images uploading… NOTFOUND Routes under: notfound notfound notfound Route: notfound URL: https://admin.myslbb.com/#/notfound Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Headings detected: Access Denied!! Actions detected: Auto, Close, GO BACK TO DASHBOARD Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/notfound Images uploading… default Captured URL: https://admin.myslbb.com/#/notfound Images uploading… default Captured URL: https://admin.myslbb.com/#/notfound Images uploading… default Captured URL: https://admin.myslbb.com/#/notfound Images uploading… default Captured URL: https://admin.myslbb.com/#/notfound Images uploading… Partner & Reseller Management Routes under: part part > paccpo > add part > paccpo > add Route: part/paccpo/add URL: https://admin.myslbb.com/#/part/paccpo/add Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Name, Description, View Active Sessions, Bulk Renew, Manage KYC, Manage Customer Comments, New Customer Auto Renewal, Edit Customer Account, View Financial Transaction Details, Change Customer Account Status, Cancel Future Plan, Manage Service Parameters, View Manage AddOn, Manage Customer Auto Renewal, View Customer Communication, Modify Communication Address, Cancel Service Plan, Download ECaf, Manage Service Parameter (Mac Bindings), View Account Operation Log, Manage On Demand Bill, View Service Usage Details, Manage Customer Subscriber Preferences, Override QOS Policy, Enable Edit Partner Actions detected: Auto, Close, Partner, Partner Access policies, Expand All, Collapse All, Select All, Deselect All, Module - Customer, Actions - Active Sessions, Actions - Ticket, Actions - Bulk Renewal, Actions - Account, Actions - Lead, Actions - Auto Renewal, Actions - Access Requests, Actions - Portal Settings, Module - Inventory, Actions - Device Items, Actions - IP Pool Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/part/paccpo/add Images uploading… part > paccpo > list > all part > paccpo > list > all Route: part/paccpo/list/all URL: https://admin.myslbb.com/#/part/paccpo/list/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Partner, Partner Access policies, New Policy, Default Partner Access Policy, LCO Access Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/part/paccpo/list/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/part/paccpo/list/all Images uploading… part > pacct > list > all part > pacct > list > all Route: part/pacct/list/all URL: https://admin.myslbb.com/#/part/pacct/list/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Partner, Partner Account, Quick Create, New Partner, Clear, CSL/0000001, SHREE SIDHHIVINAYAK NET, CSL/0000002, Glance_Amolnet, CSR/0000001, JLR Networks Pvt Ltd, CSR/0000002, Samarth Cable Services, CSR/0000003, Sumit Cables, CSR/0000004, StarNet - Powai, CSR/0000005 Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/part/pacct/list/all Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/part/pacct/list/all Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/part/pacct/list/all Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/part/pacct/list/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/part/pacct/list/all Images uploading… part > pacct > quick add part > pacct > quick add Route: part/pacct/quick-add URL: https://admin.myslbb.com/#/part/pacct/quick-add Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Partner Name, Partner Network Name, Description, Partner Type, Partner Profile, Business Entity, Access Profile, TDS(in %), GSTIN, Aadhar Number, PAN Number, Agreement Start Date, Agreement End Date, Email Id, Phone, Additional Phone Number(Optional), AddressLine 1, AddressLine 2, Pincode, Sub District, District, State, Default UserName, Default Password, User Email Actions detected: Auto, Close, Partner, Partner Account, Create Partner Account, Cancel Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/part/pacct/quick-add Images uploading… part > phm > l part > phm > l Route: part/phm/l URL: https://admin.myslbb.com/#/part/phm/l Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Partner, Partner Hierarchy Management Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/part/phm/l Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/part/phm/l Images uploading… part > ptnrprf > list > all part > ptnrprf > list > all Route: part/ptnrprf/list/all URL: https://admin.myslbb.com/#/part/ptnrprf/list/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Partner, Partner Profile, New Simple Partner Profile, New Advanced Partner Profile, Clear Filters, PRF/0002, 100_InRate, PRF/0014, 100EXCLGST, PRF/0025, 100INCLGST_Default_Distributor, PRF/0005, 60_InRate, PRF/0027, 60INCLGST, PRF/0028, 65INCLGST, PRF/0004 Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/part/ptnrprf/list/all Images uploading… create_new Captured URL: https://admin.myslbb.com/#/part/ptnrprf/list/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/part/ptnrprf/list/all Images uploading… part > tu > tra > re > details part > tu > tra > re > details Route: part/tu/tra/re/details URL: https://admin.myslbb.com/#/part/tu/tra/re/details Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Select Date Range, Amount Filter Actions detected: Auto, Close, Partner, Topup Wallet, Reversal, Apply Filter, Clear Filters Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots ui_tab_2 Captured URL: https://admin.myslbb.com/#/part/tu/tra/re/details Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/part/tu/tra/re/details Images uploading… common_tab_3 Captured URL: https://admin.myslbb.com/#/part/tu/tra/re/details Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/part/tu/tra/re/details Images uploading… part > tu > tra > re > summary part > tu > tra > re > summary Route: part/tu/tra/re/summary URL: https://admin.myslbb.com/#/part/tu/tra/re/summary Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Select Date Range Actions detected: Auto, Close, Partner, Topup Wallet, Reversal, Apply Filter, Clear Filters, XLS, CSV Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/part/tu/tra/re/summary Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/part/tu/tra/re/summary Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/part/tu/tra/re/summary Images uploading… Provisioning & Activation Routes under: pro pro > actm > addactm pro > actm > addactm Route: pro/actm/addactm URL: https://admin.myslbb.com/#/pro/actm/addactm Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Policy Name *, Description Actions detected: Auto, Close, Product, Access Time Policy, Add Rule, Create Policy, Cancel Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/pro/actm/addactm Images uploading… pro > actm > list > all pro > actm > list > all Route: pro/actm/list/all URL: https://admin.myslbb.com/#/pro/actm/list/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Product, Access Time Policy, New Policy, Clear, Allow Weekends Only, No Access Time Restriction Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/pro/actm/list/all Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/pro/actm/list/all Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/pro/actm/list/all Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/pro/actm/list/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/pro/actm/list/all Images uploading… pro > charge > chpost pro > charge > chpost Route: pro/charge/chpost URL: https://admin.myslbb.com/#/pro/charge/chpost Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Charge Name, Charge Type, Recurrence, Bill Treatment, Number of Cycles, Amount per Cycle, Bill Frequency, Charge Head, Tax Group Actions detected: Auto, Close, Product, Charges, Create Charges, Cancel Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/pro/charge/chpost Images uploading… pro > charge > list > all pro > charge > list > all Route: pro/charge/list/all URL: https://admin.myslbb.com/#/pro/charge/list/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Product, Charges, New Charges, CHRG/0001, Static IP_1200, CHRG/0002, IP_Direct Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/pro/charge/list/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/pro/charge/list/all Images uploading… pro > iptv > broadcaster > all pro > iptv > broadcaster > all Route: pro/iptv/broadcaster/all URL: https://admin.myslbb.com/#/pro/iptv/broadcaster/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: IPTV Platform Actions detected: Auto, Close, Product, IPTV, Manage Broadcaster, Add Broadcaster Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/pro/iptv/broadcaster/all Images uploading… default Captured URL: https://admin.myslbb.com/#/pro/iptv/broadcaster/all Images uploading… create_new Captured URL: https://admin.myslbb.com/#/pro/iptv/broadcaster/all Images uploading… create_new Captured URL: https://admin.myslbb.com/#/pro/iptv/broadcaster/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/pro/iptv/broadcaster/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/pro/iptv/broadcaster/all Images uploading… pro > iptv > category > all pro > iptv > category > all Route: pro/iptv/category/all URL: https://admin.myslbb.com/#/pro/iptv/category/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: IPTV Platform Actions detected: Auto, Close, Product, IPTV, Manage Category, Add Category Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/pro/iptv/category/all Images uploading… create_new Captured URL: https://admin.myslbb.com/#/pro/iptv/category/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/pro/iptv/category/all Images uploading… pro > iptv > channel > add pro > iptv > channel > add Route: pro/iptv/channel/add URL: https://admin.myslbb.com/#/pro/iptv/channel/add Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Channel Name, Channel Description, Channel Status, Select Broadcaster, Select Category, Select Content Type Actions detected: Auto, Close, Product, IPTV, Manage Channel, Cancel, Create Channel Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/pro/iptv/channel/add Images uploading… pro > iptv > channel > all pro > iptv > channel > all Route: pro/iptv/channel/all URL: https://admin.myslbb.com/#/pro/iptv/channel/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Product, IPTV, Manage Channel, Add Channel Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/pro/iptv/channel/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/pro/iptv/channel/all Images uploading… pro > iptv > package > add pro > iptv > package > add Route: pro/iptv/package/add URL: https://admin.myslbb.com/#/pro/iptv/package/add Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Package Name, Package Description, Package Status, Package Type, Package Definition Type, Validity Date, Channels, Bouquet Type Actions detected: Auto, Close, Product, IPTV, Manage Package, Cancel, Create Package Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/pro/iptv/package/add Images uploading… pro > iptv > package > all pro > iptv > package > all Route: pro/iptv/package/all URL: https://admin.myslbb.com/#/pro/iptv/package/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Product, IPTV, Manage Package, Add Package Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/pro/iptv/package/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/pro/iptv/package/all Images uploading… pro > iqos > addiqos pro > iqos > addiqos Route: pro/iqos/addiqos URL: https://admin.myslbb.com/#/pro/iqos/addiqos Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: QoS Policy Name, Download Speed, Upload Speed, AAA Policies, Tx Burst Rate, Tx Burst Threshold, Tx Burst Time, Rx Burst Rate, Rx Burst Threshold, Rx Burst Time Actions detected: Auto, Close, Product, Internet QoS Policy, Add, Save, Cancel Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/pro/iqos/addiqos Images uploading… pro > iqos > all pro > iqos > all Route: pro/iqos/all URL: https://admin.myslbb.com/#/pro/iqos/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Product, Internet QoS Policy, New Internet Qos Policy, Clear, 7 Mbps, 7168, 35 Mbps, 35840, 350 Mbps, 45875200, 175 Mbps, 22937600, 210 Mbps, 210000, 0 Kbps, 0, 225 Mbps, 225000 Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/pro/iqos/all Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/pro/iqos/all Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/pro/iqos/all Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/pro/iqos/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/pro/iqos/all Images uploading… pro > plan > list > all pro > plan > list > all Route: pro/plan/list/all URL: https://admin.myslbb.com/#/pro/plan/list/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Search Field Actions detected: Auto, Close, Product, Service Plan, New Service Plan, Clear, Somnath Demo 100Mbps, Base, OTT Smartlink Lite 300 Mbps 1 Year, Combo, OTT Smartlink Lite 300 Mbps 6 Month, OTT Smartlink Lite 300 Mbps 3 Month, OTT Smartlink Lite 300 Mbps 1 Month, OTT Smartlink Lite 200 Mbps 1 Year, OTT Smartlink Lite 200 Mbps 6 Month, OTT Smartlink Lite 200 Mbps 3 Month, OTT Smartlink Lite 200 Mbps 1 Month, OTT Smartlink Lite 150 Mbps 1 Year, OTT Smartlink Lite 150 Mbps 6 Month, OTT Smartlink Lite 150 Mbps 3 Month Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/pro/plan/list/all Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/pro/plan/list/all Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/pro/plan/list/all Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/pro/plan/list/all Images uploading… create_new Captured URL: https://admin.myslbb.com/#/pro/plan/list/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/pro/plan/list/all Images uploading… pro > promotion policy > add pro > promotion policy > add Route: pro/promotion-policy/add URL: https://admin.myslbb.com/#/pro/promotion-policy/add Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Policy Name, Offer Start Date, Offer End Date, Select Customer Type, Select Offer, What discount amount should be given?, Which partners should this offer apply to?, Which plans should this offer apply to? Actions detected: Auto, Close, Product, Promotion Policy, Create Policy, Cancel Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/pro/promotion-policy/add Images uploading… pro > promotion policy > all pro > promotion policy > all Route: pro/promotion-policy/all URL: https://admin.myslbb.com/#/pro/promotion-policy/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Product, Promotion Policy, New Policy, Clear Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/pro/promotion-policy/all Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/pro/promotion-policy/all Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/pro/promotion-policy/all Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/pro/promotion-policy/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/pro/promotion-policy/all Images uploading… pro > voucher > batch > add pro > voucher > batch > add Route: pro/voucher/batch/add URL: https://admin.myslbb.com/#/pro/voucher/batch/add Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Batch Name, Voucher Type, Description, Voucher Template, No of Items, Lock Status, Pin Generation Method, Batch Prefix, Pin Prefix, Pin Type, Pin Length, Serial Prefix, Serial Type, Serial Length Actions detected: Auto, Close, Product, Vouchers, Batch, Cancel, Generate Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/pro/voucher/batch/add Images uploading… pro > voucher > batch > all pro > voucher > batch > all Route: pro/voucher/batch/all URL: https://admin.myslbb.com/#/pro/voucher/batch/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Product, Vouchers, Batch, Add Voucher Batch, Clear Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/pro/voucher/batch/all Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/pro/voucher/batch/all Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/pro/voucher/batch/all Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/pro/voucher/batch/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/pro/voucher/batch/all Images uploading… pro > voucher > temp > add pro > voucher > temp > add Route: pro/voucher/temp/add URL: https://admin.myslbb.com/#/pro/voucher/temp/add Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Voucher Template Name, Voucher Type, Voucher Lock Status, Description, Voucher Pin Generation Method, Batch Prefix, Pin Prefix, Voucher Pin Type, Pin Length, Serial Prefix, Voucher Serial Type, Serial Length Actions detected: Auto, Close, Product, Vouchers, Template, Create Template Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/pro/voucher/temp/add Images uploading… pro > voucher > temp > all pro > voucher > temp > all Route: pro/voucher/temp/all URL: https://admin.myslbb.com/#/pro/voucher/temp/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Product, Vouchers, Template, Add Voucher Template, Clear Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/pro/voucher/temp/all Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/pro/voucher/temp/all Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/pro/voucher/temp/all Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/pro/voucher/temp/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/pro/voucher/temp/all Images uploading… Reports & Analytics Routes under: rep rep > agree > all rep > agree > all Route: rep/agree/all URL: https://admin.myslbb.com/#/rep/agree/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Status Actions detected: Auto, Close, Report, eKYC Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/rep/agree/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/rep/agree/all Images uploading… rep > ccrep > list > all rep > ccrep > list > all Route: rep/ccrep/list/all URL: https://admin.myslbb.com/#/rep/ccrep/list/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Report, Cyber Crime Reports, New Cyber Crime Report Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/rep/ccrep/list/all Images uploading… default Captured URL: https://admin.myslbb.com/#/rep/ccrep/list/all Images uploading… create_new Captured URL: https://admin.myslbb.com/#/rep/ccrep/list/all Images uploading… create_new Captured URL: https://admin.myslbb.com/#/rep/ccrep/list/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/rep/ccrep/list/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/rep/ccrep/list/all Images uploading… rep > coltr > all rep > coltr > all Route: rep/coltr/all URL: https://admin.myslbb.com/#/rep/coltr/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Select Date Range, Select Partner, Status Actions detected: Auto, Close, Report, Customer Online Transaction, Clear Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/rep/coltr/all Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/rep/coltr/all Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/rep/coltr/all Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/rep/coltr/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/rep/coltr/all Images uploading… rep > dtl rep > dtl Route: rep/dtl URL: https://admin.myslbb.com/#/rep/dtl Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Headings detected: Partner Account, Partner Ledger, Customer Account, DOT Reports, Archived Reports, Device Report, PMR Report Actions detected: Auto, Close, Report Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/rep/dtl Images uploading… rep > loltr > all rep > loltr > all Route: rep/loltr/all URL: https://admin.myslbb.com/#/rep/loltr/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Lead Search Filter, Status, Payment Method, Select Date Range Actions detected: Auto, Close, Report, Lead Online Transaction Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/rep/loltr/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/rep/loltr/all Images uploading… rep > notif > adv rep > notif > adv Route: rep/notif/adv URL: https://admin.myslbb.com/#/rep/notif/adv Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Event Type, Event Sub Type, Date Range Actions detected: Auto, Close, Report, Alerts & Notifications History, Refresh, Not Enabled, Not Subscribed Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/rep/notif/adv Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/rep/notif/adv Images uploading… rep > notif > email rep > notif > email Route: rep/notif/email URL: https://admin.myslbb.com/#/rep/notif/email Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Event Type Actions detected: Auto, Close, Report, Alerts & Notifications History Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/rep/notif/email Images uploading… default Captured URL: https://admin.myslbb.com/#/rep/notif/email Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/rep/notif/email Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/rep/notif/email Images uploading… rep > notif > sms rep > notif > sms Route: rep/notif/sms URL: https://admin.myslbb.com/#/rep/notif/sms Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Event Type Actions detected: Auto, Close, Report, Alerts & Notifications History Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/rep/notif/sms Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/rep/notif/sms Images uploading… rep > notif > whatsapp rep > notif > whatsapp Route: rep/notif/whatsapp URL: https://admin.myslbb.com/#/rep/notif/whatsapp Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Event Type Actions detected: Auto, Close, Report, Alerts & Notifications History Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/rep/notif/whatsapp Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/rep/notif/whatsapp Images uploading… rep > poltr > all rep > poltr > all Route: rep/poltr/all URL: https://admin.myslbb.com/#/rep/poltr/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Select Date Range, Select Partner, Status Actions detected: Auto, Close, Report, Partner Online Transaction, Clear, Success, 1 Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/rep/poltr/all Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/rep/poltr/all Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/rep/poltr/all Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/rep/poltr/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/rep/poltr/all Images uploading… rep > srep > add rep > srep > add Route: rep/srep/add URL: https://admin.myslbb.com/#/rep/srep/add Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Scheduled Report Name, Report Group, Report, Schedule Frequency, Schedule Time, Email, SMS, Whatsapp, FTP Actions detected: Auto, Close, Report, Scheduled Reports, Create Scheduled Report, Cancel Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/rep/srep/add Images uploading… rep > srep > all rep > srep > all Route: rep/srep/all URL: https://admin.myslbb.com/#/rep/srep/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Report, Scheduled Reports, Add Scheduled Report, Daily Summary Report Direct Customer Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/rep/srep/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/rep/srep/all Images uploading… rep > stdrep rep > stdrep Route: rep/stdrep URL: https://admin.myslbb.com/#/rep/stdrep Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Headings detected: Direct Reports, Customer Account, Sales, Partner Reports, Custom Reports, DoT Reports, Service Usage Reprts Fields detected: Status Actions detected: Auto, Close, Report, Standard Reports, + Add Category, Open, Add Offline Report Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/rep/stdrep Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/rep/stdrep Images uploading… ui_tab_2 Captured URL: https://admin.myslbb.com/#/rep/stdrep Images uploading… ui_tab_3 Captured URL: https://admin.myslbb.com/#/rep/stdrep Images uploading… ui_tab_4 Captured URL: https://admin.myslbb.com/#/rep/stdrep Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/rep/stdrep Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/rep/stdrep Images uploading… common_tab_3 Captured URL: https://admin.myslbb.com/#/rep/stdrep Images uploading… common_tab_4 Captured URL: https://admin.myslbb.com/#/rep/stdrep Images uploading… common_tab_5 Captured URL: https://admin.myslbb.com/#/rep/stdrep Images uploading… create_new Captured URL: https://admin.myslbb.com/#/rep/stdrep Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/rep/stdrep Images uploading… System Configuration Routes under: sys sys > alerts sys > alerts Route: sys/alerts URL: https://admin.myslbb.com/#/sys/alerts Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, System, Alerts, Clear Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/sys/alerts Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/sys/alerts Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/sys/alerts Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/sys/alerts Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/sys/alerts Images uploading… sys > alerts > summary sys > alerts > summary Route: sys/alerts/summary URL: https://admin.myslbb.com/#/sys/alerts/summary Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Headings detected: Alerts Summary, Recent Alerts, Alerts by Module Actions detected: Auto, Close, System, Alerts, Internet Gateway Device v1.0, 1 Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/sys/alerts/summary Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/sys/alerts/summary Images uploading… sys > audit sys > audit Route: sys/audit URL: https://admin.myslbb.com/#/sys/audit Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/sys/audit Images uploading… sys > csv sys > csv Route: sys/csv URL: https://admin.myslbb.com/#/sys/csv Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, System, Bulk Operations Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/sys/csv Images uploading… sys > logs sys > logs Route: sys/logs URL: https://admin.myslbb.com/#/sys/logs Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, System, Logs Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/sys/logs Images uploading… sys > ntfrem sys > ntfrem Route: sys/ntfrem URL: https://admin.myslbb.com/#/sys/ntfrem Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, System, Notification & Reminder Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/sys/ntfrem Images uploading… sys > role > addrole sys > role > addrole Route: sys/role/addrole URL: https://admin.myslbb.com/#/sys/role/addrole Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Name, Description, New Paytv Channel, Delete Paytv Channel, Edit Paytv Channel, View Paytv Channel, Delete Paytv Broadcaster, Edit Paytv Broadcaster, View Paytv Broadcaster, New Paytv Broadcaster, View Paytv Category, Edit Paytv Category, Delete Paytv Category, New Paytv Category, New Paytv Package, Delete Paytv Package, Edit Paytv Package, View Paytv Package, Manage Voucher Batch, Manage Voucher Template, Edit Internet Service Plan, View Product Active Users, View Product Operation Log, New Internet Service Plan, View Internet Service Plan Actions detected: Auto, Close, System, Staff Role, Expand All, Collapse All, Select All, Deselect All, Module - Product, Actions - IPTV, Actions - Voucher, Actions - OTT, Actions - Service Plan, Actions - Promotions, Actions - Policies, Actions - Charges, Module - Customer, Actions - Group Account, Actions - Account, Actions - Settings Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/sys/role/addrole Images uploading… create_new Captured URL: https://admin.myslbb.com/#/sys/role/addrole Images uploading… sys > role > all sys > role > all Route: sys/role/all URL: https://admin.myslbb.com/#/sys/role/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, System, Staff Role, New Role, SRL/003, Collection, SRL/001, Customer Care, N/A, Organization Admin, SRL/005, Sales Team, SRL/002, Super Admin, SRL/004, Technical Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/sys/role/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/sys/role/all Images uploading… sys > role > l > all sys > role > l > all Route: sys/role/l/all URL: https://admin.myslbb.com/#/sys/role/l/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, System, Staff Role, New Role, SRL/003, Collection, SRL/001, Customer Care, N/A, Organization Admin, SRL/005, Sales Team, SRL/002, Super Admin, SRL/004, Technical Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/sys/role/l/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/sys/role/l/all Images uploading… sys > sau sys > sau Route: sys/sau URL: https://admin.myslbb.com/#/sys/sau Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, System, Bulk Search and Upload Operations Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/sys/sau Images uploading… sys > set sys > set Route: sys/set URL: https://admin.myslbb.com/#/sys/set Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Headings detected: Charge Head, Global Parameters, Tax, Tax Group, My Organization, Display Preferences, Manage Gateways, Financial Document Management, WorkFlow, Agent Actions detected: Auto, Close, System, System Settings, Refresh Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/sys/set Images uploading… sys > staff > add sys > staff > add Route: sys/staff/add URL: https://admin.myslbb.com/#/sys/staff/add Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Employee Code, Staff Name, Username, Staff Role, Primary Team, Email Address, Phone/Mobile, Reporting Manager Actions detected: Auto, Close, System, Staff, Create Staff, Cancel Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/sys/staff/add Images uploading… create_new Captured URL: https://admin.myslbb.com/#/sys/staff/add Images uploading… sys > staff > all sys > staff > all Route: sys/staff/all URL: https://admin.myslbb.com/#/sys/staff/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, System, Staff, New Staff, ANIL, Anil (anil), ATIQ, Atiq Chauhan (atiq), Aziz, Aziz (aziz), EMP/000111, Hotspot User (hotspotuser), emp/00001, i2iSupport (i2isupport_smart), 004, Mahendra Bisht (mahendra), 003, Najuka (najuka), NAM Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/sys/staff/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/sys/staff/all Images uploading… sys > staff > l > all sys > staff > l > all Route: sys/staff/l/all URL: https://admin.myslbb.com/#/sys/staff/l/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, System, Staff, New Staff, ANIL, Anil (anil), ATIQ, Atiq Chauhan (atiq), Aziz, Aziz (aziz), EMP/000111, Hotspot User (hotspotuser), emp/00001, i2iSupport (i2isupport_smart), 004, Mahendra Bisht (mahendra), 003, Najuka (najuka), NAM Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/sys/staff/l/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/sys/staff/l/all Images uploading… sys > staffg > add sys > staffg > add Route: sys/staffg/add URL: https://admin.myslbb.com/#/sys/staffg/add Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Headings detected: Access Ticket Fields detected: Name, Description, All, Assigned To Team, Assigned To Me, Associate All Partner, Associate All Branch Actions detected: Auto, Close, System, Team, Add Partner, Add Branch, Create Team, Cancel Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/sys/staffg/add Images uploading… create_new Captured URL: https://admin.myslbb.com/#/sys/staffg/add Images uploading… sys > staffg > all sys > staffg > all Route: sys/staffg/all URL: https://admin.myslbb.com/#/sys/staffg/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, System, Team, New Team, N/A, Default Group, TM/003, Direct, TM/004, Ghatkopar Team Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/sys/staffg/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/sys/staffg/all Images uploading… sys > staffg > l > all sys > staffg > l > all Route: sys/staffg/l/all URL: https://admin.myslbb.com/#/sys/staffg/l/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, System, Team, New Team, N/A, Default Group, TM/003, Direct, TM/004, Ghatkopar Team Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/sys/staffg/l/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/sys/staffg/l/all Images uploading… Trouble Ticketing Routes under: tkt tkt > customer tkt > customer Route: tkt/customer URL: https://admin.myslbb.com/#/tkt/customer Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Date Range Actions detected: Auto, Close, Ticket, Customer, Create Customer Ticket, Clear Filter, CTKT/00002, Hubcom Techno System LLP Unit, Connectivity Issue -> Fiber Issue, CTKT/00001, Najuka Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/tkt/customer Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/tkt/customer Images uploading… ui_tab_2 Captured URL: https://admin.myslbb.com/#/tkt/customer Images uploading… ui_tab_3 Captured URL: https://admin.myslbb.com/#/tkt/customer Images uploading… ui_tab_4 Captured URL: https://admin.myslbb.com/#/tkt/customer Images uploading… ui_tab_5 Captured URL: https://admin.myslbb.com/#/tkt/customer Images uploading… ui_tab_6 Captured URL: https://admin.myslbb.com/#/tkt/customer Images uploading… ui_tab_7 Captured URL: https://admin.myslbb.com/#/tkt/customer Images uploading… ui_tab_8 Captured URL: https://admin.myslbb.com/#/tkt/customer Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/tkt/customer Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/tkt/customer Images uploading… common_tab_3 Captured URL: https://admin.myslbb.com/#/tkt/customer Images uploading… common_tab_4 Captured URL: https://admin.myslbb.com/#/tkt/customer Images uploading… common_tab_5 Captured URL: https://admin.myslbb.com/#/tkt/customer Images uploading… common_tab_6 Captured URL: https://admin.myslbb.com/#/tkt/customer Images uploading… common_tab_7 Captured URL: https://admin.myslbb.com/#/tkt/customer Images uploading… common_tab_8 Captured URL: https://admin.myslbb.com/#/tkt/customer Images uploading… common_tab_9 Captured URL: https://admin.myslbb.com/#/tkt/customer Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/tkt/customer Images uploading… tkt > customer > add tkt > customer > add Route: tkt/customer/add URL: https://admin.myslbb.com/#/tkt/customer/add Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Select Customer, Type, Select Category, Priority, High, Medium, Low, Call From, Auto Assignment, Manual Assignment Actions detected: Auto, Close, Ticket, Customer, Cancel, Create Ticket, Create Ticket With Resolve Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/tkt/customer/add Images uploading… tkt > internal tkt > internal Route: tkt/internal URL: https://admin.myslbb.com/#/tkt/internal Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Ticket, Create Internal Ticket Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/tkt/internal Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/tkt/internal Images uploading… ui_tab_2 Captured URL: https://admin.myslbb.com/#/tkt/internal Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/tkt/internal Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/tkt/internal Images uploading… common_tab_3 Captured URL: https://admin.myslbb.com/#/tkt/internal Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/tkt/internal Images uploading… tkt > internal > add tkt > internal > add Route: tkt/internal/add URL: https://admin.myslbb.com/#/tkt/internal/add Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Type, Select Category, Priority, High, Medium, Low, Title, Auto Assignemnt, Manual Assignment Actions detected: Auto, Close, Ticket, Internal, Cancel, Create Ticket, Create Ticket With Resolve Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/tkt/internal/add Images uploading… tkt > partner tkt > partner Route: tkt/partner URL: https://admin.myslbb.com/#/tkt/partner Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Ticket, Create Partner Ticket Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/tkt/partner Images uploading… ui_tab_1 Captured URL: https://admin.myslbb.com/#/tkt/partner Images uploading… ui_tab_2 Captured URL: https://admin.myslbb.com/#/tkt/partner Images uploading… common_tab_1 Captured URL: https://admin.myslbb.com/#/tkt/partner Images uploading… common_tab_2 Captured URL: https://admin.myslbb.com/#/tkt/partner Images uploading… common_tab_3 Captured URL: https://admin.myslbb.com/#/tkt/partner Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/tkt/partner Images uploading… tkt > partner > add tkt > partner > add Route: tkt/partner/add URL: https://admin.myslbb.com/#/tkt/partner/add Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Select Partner, Type, Select Category, Priority, High, Medium, Low, Title, Auto Assignemnt, Manual Assignment Actions detected: Auto, Close, Ticket, Partner, Cancel, Create Ticket, Create Ticket With Resolve Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/tkt/partner/add Images uploading… tkt > settings > customer tkt > settings > customer Route: tkt/settings/customer URL: https://admin.myslbb.com/#/tkt/settings/customer Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Ticket, Settings Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/tkt/settings/customer Images uploading… tkt > settings > internal tkt > settings > internal Route: tkt/settings/internal URL: https://admin.myslbb.com/#/tkt/settings/internal Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Ticket, Settings Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/tkt/settings/internal Images uploading… tkt > settings > partner tkt > settings > partner Route: tkt/settings/partner URL: https://admin.myslbb.com/#/tkt/settings/partner Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, Ticket, Settings Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/tkt/settings/partner Images uploading… WSMP Routes under: wsmp wsmp > advment > add wsmp > advment > add Route: wsmp/advment/add URL: https://admin.myslbb.com/#/wsmp/advment/add Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Advertisement Name, Type, Select Category Actions detected: Auto, Close, WiFi, Advertisement Service, Cancel, Create Advertisement Portal Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/wsmp/advment/add Images uploading… create_new Captured URL: https://admin.myslbb.com/#/wsmp/advment/add Images uploading… wsmp > advment > list > all wsmp > advment > list > all Route: wsmp/advment/list/all URL: https://admin.myslbb.com/#/wsmp/advment/list/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, WiFi, Advertisement Service, Add Advertisement Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/wsmp/advment/list/all Images uploading… default Captured URL: https://admin.myslbb.com/#/wsmp/advment/list/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/wsmp/advment/list/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/wsmp/advment/list/all Images uploading… wsmp > ap > all wsmp > ap > all Route: wsmp/ap/all URL: https://admin.myslbb.com/#/wsmp/ap/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, WiFi, Access Point, New Access point, AP/001, Athani Mikrotik, Office Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/wsmp/ap/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/wsmp/ap/all Images uploading… wsmp > ap > create wsmp > ap > create Route: wsmp/ap/create URL: https://admin.myslbb.com/#/wsmp/ap/create Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Access Point Name, Hotspot, Device Serial Number, Device MAC Address, Latitude, VLAN, Description Actions detected: Auto, Close, WiFi, Access Point, Create Access Point, Cancel Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/wsmp/ap/create Images uploading… wsmp > cp > add wsmp > cp > add Route: wsmp/cp/add URL: https://admin.myslbb.com/#/wsmp/cp/add Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Captive Portal Name, Description, Layout, Background Configuration Actions detected: Auto, Close, WiFi, Captive Portal Service, Create Captive Portal, Cancel Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/wsmp/cp/add Images uploading… wsmp > cp > list > all wsmp > cp > list > all Route: wsmp/cp/list/all URL: https://admin.myslbb.com/#/wsmp/cp/list/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, WiFi, Captive Portal Service, Add Captive Portal, CP/001, Smartlink Office Captive Portal, 1 Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/wsmp/cp/list/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/wsmp/cp/list/all Images uploading… wsmp > hspot > create wsmp > hspot > create Route: wsmp/hspot/create URL: https://admin.myslbb.com/#/wsmp/hspot/create Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Fields detected: Advertisement Allowed, Hotspot Name, Captive Portal, Latitude, Longitude, Select Partner, Default Country Code, Key, Description, Select All, One Time Use, Time Duration, Never Expires Actions detected: Auto, Close, WiFi, Hotspot, Create Hotspot, Cancel Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots create_new Captured URL: https://admin.myslbb.com/#/wsmp/hspot/create Images uploading… wsmp > hspot > list > all wsmp > hspot > list > all Route: wsmp/hspot/list/all URL: https://admin.myslbb.com/#/wsmp/hspot/list/all Overview This page is a draft SOP reference for the above screen in i2i Core OSS/BSS . It is auto-generated from UI exports and should be reviewed for operational correctness before customer release. When to Use Use this screen for the workflow represented by this route. Do not make billing/AAA/provisioning-impacting changes without required authorization. Typical Workflow Verify you are working on the correct entity (Customer/Account/Service). Review the current lifecycle state before making changes. Apply changes and validate system response. Confirm downstream impact (AAA/Provisioning/Billing) where applicable. Field & Action Hints (Auto-detected) Actions detected: Auto, Close, WiFi, Hotspot, Create Hotspot, HPT/001, Smartlink Office Hotspot Validation & Safety Checks Confirm identifiers before saving. Confirm lifecycle state allows the change. Confirm rollback/support path exists for production actions. Escalation Guidance L1: Verify input, permissions, and entity state. L2: Validate dependencies and downstream state. L3/Admin: Policy/config changes or suspected defect. Screenshots default Captured URL: https://admin.myslbb.com/#/wsmp/hspot/list/all Images uploading… drilldown_one_item Captured URL: https://admin.myslbb.com/#/wsmp/hspot/list/all Images uploading…