Capital scoreboard
The receivables-advancing scoreboard: volume advanced, net released, average rate and effective take rate — and the number that closes the loop with the score: REAL × PREDICTED default. The predicted is the risk premium charged (what the score said it would lose); the real is the face value of adva…
What you find on this screen
A portrait of the screen, read from the screen itself — it changes when the screen changes.
Available actions
Refresh
The list shows
ScreenAccesslegacy msnew msTime gainLegacy err. × newSamples (legacy/new)Verdict
Form fields
Endereço de destino
Apurada em
Ms Ate Interacao
Erros
Origem
Start here
Nenhuma tela migra por estética
This is the yardstick for the slice-by-slice front-end migration: the platform's most used screens, cross-referenced with the LEGACY × NEW comparison for each one. The decision to migrate a screen comes from here — from measured gain — and not from opinion about which front end is prettier. Platform Super Admin screen.
What this screen is
Super admin screen for deciding the slice-by-slice front-end migration: the ranking of the most used screens cross-referenced with the LEGACY × NEW comparison for each one (time to 1st interaction and error rate). No screen migrates for aesthetics — only with measured gain and a sufficient sample. It serves to prioritize: migrate first what is heavily used AND has proven gain.
How to
How to read the columns
Accesses = total use of the screen (prioritize what is heavily used AND has proven gain). "Legacy ms" and "new ms" = average time to first interaction in each origin. "Time gain" = the difference as a percentage. "Error leg. × new" = error rate on each side. A dash "—" = no sample has arrived from that origin yet.
Rules
When the verdict recommends migrating
Only when the new slice is FASTER (time to first interaction) AND DOES NOT ERR MORE (error rate), with a sufficient sample: a minimum of 30 page views from each origin. If any of the three is missing, the verdict holds — the hourglass means "there is no basis to claim it yet".
A telemetria é opt-in por tela
A screen only reports after receiving the /pages/comum/telemetria-include.xhtml fragment. Today only the pilot (/pages/novo/host.xhtml) reports the NEW origin — the rest of the ranking shows usage, but without comparison. The migration playbook is in docs/03-arquitetura/MIGRACAO-FRONT-POR-FATIAS.md.
Frequently asked questions
O ranking está vazio
No usage data yet: the ranking comes from real access to the screens. As soon as there is navigation, the screens appear sorted by total accesses. The Refresh button reloads the reading.
Which question this screen answers
Which screen is worth migrating to the new front end — where is there truly MEASURED gain? The screen cross-references the ranking of the most used screens with the legacy versus new comparison for each one: time to first interaction and error rate. No screen migrates for aesthetics — only with measured gain and a sufficient sample. The cross-reference serves to prioritize: migrate first what is heavily used AND has proven gain; what is rarely used, or has not yet shown gain, waits. Telemetry is opt-in per screen.
Was this article helpful?
In the same module: Platform1
Tenka Academy
Explore the AcademyStep-by-step learning paths for your industry, inside the platform.