Table Page Overview – RevOS Documentation & Support

Table overview page is a main page where you can see a main table with model data and statistics of the scoring

Upper part of the screen is occupied by the table statistics visualisations and lower part shows the data table.

On the left sidebar, you can find quick access to additional resources:

Help Center: Provides access to extensive documentation covering various aspects of working with RevOS Tables. Here, you can find detailed explanations, guides, and troubleshooting tips.

Chat Support: Opens a side panel where you can start a conversation and ask any questions related to the platform. This feature allows users to get real-time assistance from the support team.

These tools ensure that users can efficiently navigate and utilize RevOS Tables while having direct access to help when needed.

Table statistics

There are two parts of the table statistics that you see on top:

Score distribution - the current state of the scoring model showing a chart visualising the score distribution, such as how many High, Medium and Low scored rows are in the table below.

Two numbers in the center shows:

Left - average score across all total scores of all rows of the table and

Right - a maximum total score that can be achieved given the scoring table configuration, imagine a maximum number a row could reach if each score will be ‘green’ and maximum scoring points assigned to each score will be reached

So for example average score above is 54 out of maximum possible 100.

Score History - visualises the average score in time grouped by the scoring group

How the color of the total score is determined?

This picture demonstrate it in a simple code:

The score is considered to be ‘high’ / or ‘green’ if the value of the total score is higher than 70% of Maximum Total Score, so for example if maximum total score is 100 then 70 will be ‘medium’ or ‘yellow’ and 71 will be ‘high’ / ‘green’.

The score is considered to be ‘low’ or ‘red’ if the value of the total score is lower than 30% of the Maximum Total Score, so for example if the maximum total score is 100 then 29 will be ‘low’/‘red’ while 30 will still be ‘medium’/‘yellow’.

How the color of the total score in group is determined?

Just like for the total score same logic applies to the group scores and how they are mapped to ‘red/yellow/green` colours is the same as the definition for Total Score - thresholds are 70% and 30% of all individual scores in the group.

Legacy vs Semanic tables

We now offer two generations of tables—Legacy (our original format) and Semantic (the new, model-driven format).

Feature	Legacy Table	Semantic Table
Availability	Existing only – new Legacy tables can’t be created.	Default for all new tables.
Table creation	Manual column selection during setup.	One-click: once a semantic model exists, you can spin up the matching table in seconds.
Data source	Bound directly to a dataset chosen at creation.	Generated from a semantic model that is built from your integration; every column represents an entity or attribute from that model.
Views (saved column/filter presets)	✔ Supported	✖ Not yet available
Measures (aggregated metrics)	✖ Not available	✔ Built-in measure objects auto-aggregate to the table’s grain
Back-compatibility	Fully supported; all existing Legacy tables and their data remain intact.	Actively developed format

What’s new in Semantic tables

Instant table creation – After you define a semantic model, creating the corresponding table is essentially a single click; no manual schema mapping.

Model-driven columns – The table always stays in sync with the integration-backed semantic model, so new data fields just appear automatically once they’re added to the model.

Measures for roll-ups – Semantic models can include measures (aggregated metrics). These adjust automatically to whatever grain the client’s table is built on.

Example: Your model links Companies ↔ Deals and defines a Total Revenue measure on Deals. When you add that measure to a Company-based table, you instantly see each company’s total deal revenue—no SQL, no look-ups.

What stays the same

Every Legacy table you already have continues to work exactly as before.

Data connected to Legacy tables is unaffected, so anyone relying on them can keep using them without changes.