Stateful Objects

This update adds stateful objects.

An object's time axis is now optional, so data where the current state matters more than when something happened can live in the ontology too.

Why we made this

Some of the data an organization works with has a clear moment of occurrence, like an inquiry or an order. Other data, like an equipment register or a product master, matters for its current state rather than a point in time. If every object must carry a time axis, that reference data either gets an artificial date attached or stays outside entirely, and every analysis means reconciling two places.

This update closes that gap so data without a time axis can be handled with the same analysis tools.

Choosing a time axis

Decide whether an object carries a time axis when you create it.

• Two shapes: Choose between time-series, which carries an occurrence time, and stateful, which holds a current state.
• State updates: For stateful objects, new values for the same subject overwrite the previous state.
• Existing objects unchanged: Objects you already use continue to behave as time-series.

Now equipment registers, product masters, and contract status, where state matters more than timing, can live inside the ontology.

The same analysis tools

Stateful objects use the existing analysis features as they are.

• Search and filters: Narrow by property conditions and move from the list into detail.
• Summaries and rankings: Aggregate value distributions and top items.
• Optional time basis: Designate a date property, such as registration time, as the time basis to narrow by period.

Now reference data does not need to be managed separately and can be read alongside operational data on the same screen.

You can try it right away from the Deskroom sidebar > Ontology. Spend the time you used to spend reconciling two sources on making decisions from your data.