Trouble Ticketing
Routes under: tkt
- tkt > customer
- tkt > customer > add
- tkt > internal
- tkt > internal > add
- tkt > partner
- tkt > partner > add
- tkt > settings > customer
- tkt > settings > internal
- tkt > settings > partner
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
ui_tab_1
Captured URL: https://admin.myslbb.com/#/tkt/customer
ui_tab_2
Captured URL: https://admin.myslbb.com/#/tkt/customer
ui_tab_3
Captured URL: https://admin.myslbb.com/#/tkt/customer
ui_tab_4
Captured URL: https://admin.myslbb.com/#/tkt/customer
ui_tab_5
Captured URL: https://admin.myslbb.com/#/tkt/customer
ui_tab_6
Captured URL: https://admin.myslbb.com/#/tkt/customer
ui_tab_7
Captured URL: https://admin.myslbb.com/#/tkt/customer
ui_tab_8
Captured URL: https://admin.myslbb.com/#/tkt/customer
common_tab_1
Captured URL: https://admin.myslbb.com/#/tkt/customer
common_tab_2
Captured URL: https://admin.myslbb.com/#/tkt/customer
common_tab_3
Captured URL: https://admin.myslbb.com/#/tkt/customer
common_tab_4
Captured URL: https://admin.myslbb.com/#/tkt/customer
common_tab_5
Captured URL: https://admin.myslbb.com/#/tkt/customer
common_tab_6
Captured URL: https://admin.myslbb.com/#/tkt/customer
common_tab_7
Captured URL: https://admin.myslbb.com/#/tkt/customer
common_tab_8
Captured URL: https://admin.myslbb.com/#/tkt/customer
common_tab_9
Captured URL: https://admin.myslbb.com/#/tkt/customer
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/tkt/customer
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
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
ui_tab_1
Captured URL: https://admin.myslbb.com/#/tkt/internal
ui_tab_2
Captured URL: https://admin.myslbb.com/#/tkt/internal
common_tab_1
Captured URL: https://admin.myslbb.com/#/tkt/internal
common_tab_2
Captured URL: https://admin.myslbb.com/#/tkt/internal
common_tab_3
Captured URL: https://admin.myslbb.com/#/tkt/internal
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/tkt/internal
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
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
ui_tab_1
Captured URL: https://admin.myslbb.com/#/tkt/partner
ui_tab_2
Captured URL: https://admin.myslbb.com/#/tkt/partner
common_tab_1
Captured URL: https://admin.myslbb.com/#/tkt/partner
common_tab_2
Captured URL: https://admin.myslbb.com/#/tkt/partner
common_tab_3
Captured URL: https://admin.myslbb.com/#/tkt/partner
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/tkt/partner
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
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
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
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
