MSO Portal Automation

A pending change — a recharge, a plan change, a cut or a restore — can be replayed on the network’s own LCO portal from inside the app, and what the portal answered is recorded against the row. Off leaves that work to be done by hand on the portal and ticked off here, which is what it has always been.

Switch: Settings > Cable > MSO Portal Automation. Permissions: the Portal actions permission, on top of the cable shell.

Where it appears

Cable shell: the Portal page, right after History — the queue it drives is the history read the other way round: what has not been done on the network yet. Portal actions also appear on a connection’s history rows.

Flow

flowchart TD
    A[Change made in the app
recharge · plan · cut · restore] --> B[(Logged against the connection)]
    B --> C[Portal queue: not yet done upstream]
    C --> D[Replay on the LCO portal]
    D --> E{Portal's answer}
    E -->|accepted| F[(Verdict recorded on the row)]
    E -->|refused| G[Stays in the queue with the reason]

The app’s book and the network’s portal are two records of the same change; this is the step that keeps them the same.

Screens

Portal - everything waiting to be done upstream, with what the portal said to each attempt.
History - a connection’s timeline, with the portal verdict beside the change that caused it.

Switching off. An action over the existing log — the rows and their portal verdicts stay where they are, only the button goes away.