Tables: columns, pages, selection and phones

Every list in the panel (calls, trunks, organisations, numbers, campaigns, the audit log and the rest) works the same way.

​

Choosing columns

The Columns button is the small icon at the bottom of the list, in the footer beside the page controls. It is there rather than beside the search box, where it crowded the filters. Its tooltip says how many columns are shown out of how many exist. Tick a column to show it, untick it to hide it. The menu stays open while you work, because choosing columns is usually several decisions looked at together. Reset to default puts the list back to how it arrived. Everyone who signs in to the panel can choose their columns: operators, organisation admins, supervisors and agents.

​

What it remembers

Your choice is kept per list and per person, in the browser you made it in. It survives reloading and signing out, and it does not follow you to another computer or another browser. Two people using the same panel never change each other’s lists. A choice made under an older version of a list (the call history’s columns were once one shared setting) is carried over the first time you open the list, not forgotten.

​

What you cannot hide

The column that says which row it is. On a call that is who spoke to whom; on a trunk, its name. Hiding it would leave a table of measurements belonging to nothing, so it is not offered. Hiding everything else is allowed and leaves that one column standing.

​

Columns that start hidden

Some columns are off until you ask for them — on Call history, the codec, whether the call was transcoded, the hangup cause and the AI tokens. They are the switch’s own diagnostics: exactly what you want when you are chasing a fault and noise on every other day. They are still on each call’s own page whether or not the column is on.

​

Columns you will not find

A column is missing from the menu entirely when the account may not see the figure behind it. Carrier cost and margin need margin:read; without it the API does not send them at all, so there is nothing a column could show. This is the same rule as everywhere else in FireTone: absent means not permitted, not applicable, or not known — never zero. Granting the permission makes the column appear in the menu.

​

Pages

Lists are paged on the server, so a list of a hundred thousand calls opens as fast as one of ten and nothing is quietly cut off at a fixed number of rows. The footer shows which rows you are looking at and the total, moves between pages, and sets rows per page (25, 50, 100 or 200). Sorting, searching and filtering apply to the whole list, not only the page on screen.

​

Acting on several rows

Lists that allow it have a checkbox on each row and one in the heading for the whole page. With rows selected, a bar offers the actions that apply to them: enabling or disabling several trunks, releasing several bans, retrying several failed emails or messages, allowing several organisations client trunks.

• A selection is only of the rows you can see. It clears when you change page, filter or search, so an action never reaches rows you are not looking at.
• An action that cannot be undone asks you to confirm first.
• Each row is done separately and the bar reports the outcome, for example 8 of 10 done, 2 failed, with the reason for each failure. It stays until you dismiss it.
• An action is offered only for the rows it applies to. Enable skips rows that are already enabled.

​

On a phone

On a narrow screen each row becomes a card. The row’s identity (a call’s parties, a trunk’s name) is the card’s heading, and the other columns are listed under it with their labels. Columns that matter only at a desk are left out of the card. On a tablet, the table keeps its columns and drops the ones it can spare. The Columns button, the pages and selection all work the same way.