Update CPE Info
This page explains focused CTT flow for updating CPE information.
API Endpoints
POST /ticket/ctt/cpe/update/:id
Purpose
CPE update flow lets operator correct or refresh device-related information on eligible CTTs.
Business meaning
This is not open edit for every CTT.
Current implementation treats it as controlled update with:
- confirmation in portal
- payload validation
- Managed Services restriction
- downstream NIG sync
- local corp-data refresh
- CPE history write
Portal behavior
Current portal flow:
- opens confirmation dialog
- builds payload from current and new CPE fields
- calls
POST ticket/ctt/cpe/update/:id - refreshes shown CPE values after success
Flow summary
| Step | Business meaning |
|---|---|
| user confirms CPE update | explicit operator approval happens |
| load CTT by id | target ticket must exist |
| validate manufacturer, model, IP, bandwidth, and port data | input must pass business validation |
| load CTT network elements | backing network context must exist |
check FTTH + Managed Services | only eligible CTTs can continue |
| derive current CPE snapshot | baseline values are prepared |
| send update to NIG | downstream system must accept change |
| update local corp data temp records | local representation is refreshed |
| reload updated network-element data | response is rebuilt from latest state |
| create CPE history entry | audit-style change history is preserved |
| return updated CPE response | UI can refresh visible fields |
Implementation note
Current repo confirms:
- portal submits update from ticket status subcomponent
- backend exposes
POST /ticket/ctt/cpe/update/:id - backend blocks non-Managed-Services path
- NIG sync failure rejects request
- successful update writes CPE history
Code refs:
intt-portal/src/app/components/pages/main-modules/ctt/ctt-details/sub-components/ticket-status/ticket-status.component.ts:371intt-portal/src/app/components/pages/main-modules/ctt/ctt-details/sub-components/ticket-status/ticket-status.component.ts:409intt-portal/src/app/components/pages/main-modules/ctt/ctt-details/sub-components/ticket-status/ticket-status.component.ts:579mvp3-ticket-service/src/modules/ctt/ctt.controller.ts:351mvp3-ticket-service/src/modules/ctt/ctt.service.ts:2979
Important behavior
- portal editability is gated by segment group
- backend rechecks eligibility; frontend gate alone not enough
- NIG sync is part of success criteria
- CPE history matters for support review after updates