Reports & Analytics
Routes under: rep
- rep > agree > all
- rep > ccrep > list > all
- rep > coltr > all
- rep > dtl
- rep > loltr > all
- rep > notif > adv
- rep > notif > email
- rep > notif > sms
- rep > notif > whatsapp
- rep > poltr > all
- rep > srep > add
- rep > srep > all
- rep > stdrep
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
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/rep/agree/all
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
default
Captured URL: https://admin.myslbb.com/#/rep/ccrep/list/all
create_new
Captured URL: https://admin.myslbb.com/#/rep/ccrep/list/all
create_new
Captured URL: https://admin.myslbb.com/#/rep/ccrep/list/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/rep/ccrep/list/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/rep/ccrep/list/all
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
ui_tab_1
Captured URL: https://admin.myslbb.com/#/rep/coltr/all
common_tab_1
Captured URL: https://admin.myslbb.com/#/rep/coltr/all
common_tab_2
Captured URL: https://admin.myslbb.com/#/rep/coltr/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/rep/coltr/all
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
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
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/rep/loltr/all
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
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/rep/notif/adv
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
default
Captured URL: https://admin.myslbb.com/#/rep/notif/email
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/rep/notif/email
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/rep/notif/email
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
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/rep/notif/sms
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
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/rep/notif/whatsapp
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
ui_tab_1
Captured URL: https://admin.myslbb.com/#/rep/poltr/all
common_tab_1
Captured URL: https://admin.myslbb.com/#/rep/poltr/all
common_tab_2
Captured URL: https://admin.myslbb.com/#/rep/poltr/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/rep/poltr/all
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
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
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/rep/srep/all
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
ui_tab_1
Captured URL: https://admin.myslbb.com/#/rep/stdrep
ui_tab_2
Captured URL: https://admin.myslbb.com/#/rep/stdrep
ui_tab_3
Captured URL: https://admin.myslbb.com/#/rep/stdrep
ui_tab_4
Captured URL: https://admin.myslbb.com/#/rep/stdrep
common_tab_1
Captured URL: https://admin.myslbb.com/#/rep/stdrep
common_tab_2
Captured URL: https://admin.myslbb.com/#/rep/stdrep
common_tab_3
Captured URL: https://admin.myslbb.com/#/rep/stdrep
common_tab_4
Captured URL: https://admin.myslbb.com/#/rep/stdrep
common_tab_5
Captured URL: https://admin.myslbb.com/#/rep/stdrep
create_new
Captured URL: https://admin.myslbb.com/#/rep/stdrep
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/rep/stdrep
