Provisioning & Activation
Routes under: pro
- pro > actm > addactm
- pro > actm > list > all
- pro > charge > chpost
- pro > charge > list > all
- pro > iptv > broadcaster > all
- pro > iptv > category > all
- pro > iptv > channel > add
- pro > iptv > channel > all
- pro > iptv > package > add
- pro > iptv > package > all
- pro > iqos > addiqos
- pro > iqos > all
- pro > plan > list > all
- pro > promotion policy > add
- pro > promotion policy > all
- pro > voucher > batch > add
- pro > voucher > batch > all
- pro > voucher > temp > add
- pro > voucher > temp > all
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
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
ui_tab_1
Captured URL: https://admin.myslbb.com/#/pro/actm/list/all
common_tab_1
Captured URL: https://admin.myslbb.com/#/pro/actm/list/all
common_tab_2
Captured URL: https://admin.myslbb.com/#/pro/actm/list/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/pro/actm/list/all
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
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
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/pro/charge/list/all
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
default
Captured URL: https://admin.myslbb.com/#/pro/iptv/broadcaster/all
create_new
Captured URL: https://admin.myslbb.com/#/pro/iptv/broadcaster/all
create_new
Captured URL: https://admin.myslbb.com/#/pro/iptv/broadcaster/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/pro/iptv/broadcaster/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/pro/iptv/broadcaster/all
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
create_new
Captured URL: https://admin.myslbb.com/#/pro/iptv/category/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/pro/iptv/category/all
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
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
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/pro/iptv/channel/all
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
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
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/pro/iptv/package/all
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
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
ui_tab_1
Captured URL: https://admin.myslbb.com/#/pro/iqos/all
common_tab_1
Captured URL: https://admin.myslbb.com/#/pro/iqos/all
common_tab_2
Captured URL: https://admin.myslbb.com/#/pro/iqos/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/pro/iqos/all
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
ui_tab_1
Captured URL: https://admin.myslbb.com/#/pro/plan/list/all
common_tab_1
Captured URL: https://admin.myslbb.com/#/pro/plan/list/all
common_tab_2
Captured URL: https://admin.myslbb.com/#/pro/plan/list/all
create_new
Captured URL: https://admin.myslbb.com/#/pro/plan/list/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/pro/plan/list/all
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
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
ui_tab_1
Captured URL: https://admin.myslbb.com/#/pro/promotion-policy/all
common_tab_1
Captured URL: https://admin.myslbb.com/#/pro/promotion-policy/all
common_tab_2
Captured URL: https://admin.myslbb.com/#/pro/promotion-policy/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/pro/promotion-policy/all
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
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
ui_tab_1
Captured URL: https://admin.myslbb.com/#/pro/voucher/batch/all
common_tab_1
Captured URL: https://admin.myslbb.com/#/pro/voucher/batch/all
common_tab_2
Captured URL: https://admin.myslbb.com/#/pro/voucher/batch/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/pro/voucher/batch/all
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
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
ui_tab_1
Captured URL: https://admin.myslbb.com/#/pro/voucher/temp/all
common_tab_1
Captured URL: https://admin.myslbb.com/#/pro/voucher/temp/all
common_tab_2
Captured URL: https://admin.myslbb.com/#/pro/voucher/temp/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/pro/voucher/temp/all