Data periods, versions & context
Every view names its period and version. Here is why that matters and how to compare snapshots.
Numen is a management-accounting product, and in management accounting a number means nothing without its context. So every view in Numen states three things up front: its data period, its version, and the query period you asked for. When you read a figure, you always know exactly what it describes.
Versioning is simple by design
- Data — every upload is a version. The moment you upload a file, that upload becomes a version. Nothing to configure, nothing to remember.
- KPI formulas live inside widgets — changes apply immediately. Edit a widget's formula and the new logic takes effect right away.
- Formula history is managed through widgets. Changing a widget's logic adds a new custom widget carrying the updated formula — the old widget keeps the old logic, the new one carries the new. Your Library is the version history.
On top of that, two agents keep their own version records: Budget Planning preserves the baseline and tracks each revision on top of it, and What-if records which scenario each variation was copied from.
Comparing versions
Because snapshots are kept, you can compare versions to see exactly what changed — this budget revision against the original baseline, or a scenario variation against the scenario it was copied from. The comparison shows the delta, not just two separate numbers, so the story behind a change is easy to read.
How context flows to widgets
The period and entity context filters in the canvas header are the single source of truth for a page. Set them once, and that context flows to every widget on the canvas — each one re-reads your data for the chosen period and entity. You do not adjust widgets one by one to move a whole view to a new month or company.