Versions and history
Read what changed on a model, turn by turn, go back to an earlier version of it, and see who did what in its audit log.
Where: Models→a model→The record→Details→History
A model has one history, at the foot of its record: History, what each turn of your conversation with RIA changed. Each change to the model also keeps a version of it, and Earlier versions, under History, lists those versions so you can go back to one. The Audit log records every event on the model, including the ones that change nothing in it.
Open the history
- On the model's page, open Details at the foot of the record. History is its last part.
- On Models, open a row's ⋯ menu and click History. The model's page opens with Details and History open, scrolled into view.
A link to a model's history, such as one RIA gives you, opens the model's page the same way.
Read the history
History lists your turns with RIA, newest first. Each turn says when, the start of what you said ("You said “…”"), and what the turn changed:
- a line for each thing added, changed or removed, a change reading "was …, now …";
- what a run found, such as "Solved: …, … above the last solve.";
- what eode did around it, such as The build started., "RIA read your workbook and proposed what each sheet holds." or "You attached …".
Ten turns show; Show earlier shows the rest. A model with nothing recorded yet reads No updates yet.
Open earlier versions
Click Earlier versions at the foot of History. The Earlier versions drawer opens on the right, headed with the model's name. Close it with ✕, Esc, or a click outside it.
Versions are listed newest first. Each row shows:
- a mark for who made it (a person, RIA, or eode itself), when, and their name;
- a Now tag on the version the model is at;
- what changed, in a sentence: "The model was built.", "The model was built again.", "Its data was changed.", "Its measures were changed.", "Its checks were changed.", "Its news was refreshed.", "It was brought up to date.", "Went back to the version of …", "Kept before going back to an earlier version.", or the change's own summary;
- chips for what moved: +N objects, −N objects, +N links, −N links (+1 object, +1 link for one), Measures changed, Its map changed.
Renames, permission changes, locks and sharing aren't versions; they're in the audit log. A model with none reads "No earlier versions yet. Each change to the model keeps one here."
Go back to an earlier version
- In Earlier versions, click Go back to this version on any version but the one marked Now.
- A card opens at the top of the drawer: Go back to the version of date? It says the model returns to how it was then, and what happens to the work since.
- Click Go back (Running…), or Cancel.
What going back does:
- What changed since that version leaves the model. The version you had is kept first, so you can come back to it from Earlier versions.
- The model needs building again. Tell RIA what to change in the conversation and it builds from there.
- Until it's built, the model's runs and its file wait, and every what-if reads out of date.
- The owner, organization, sharing and permissions never go back.
The record then reads Back at an earlier version, not built for it yet. Its top card explains, and offers Go back to the version kept before it, which asks "Go back to the version kept before going back?" and returns the model to how it was, with its own build and last solve. History notes the go-back.
You can't go back:
- on a locked model: there's no Go back to this version, and the footer reads "Unlock the model to go back to an earlier version." See Share and govern;
- past a later edit to the model's data: the row reads "A later data edit can't be undone by going back."
Anyone else reads "The model's owners and organization admins can go back to an earlier version."
Read the audit log
Where: Models→⋯→Model settings→Audit log
On Models, open a row's ⋯ menu, click Model settings, then Audit log. The drawer lists every event on the model as a sentence, newest first, with N events in its header. Close it with ✕ or Esc.
Filter by family (All, Locks, Promotions, Authoring, Scenarios, Data, Workflows + runs, Permissions) and by person (All actors). Reverts and backlog events (applied, set aside, reopened, change requests) show only under All.
| Family | Example sentences |
|---|---|
| Locks and promotion | "… locked “…”: reason", "… took over the lock on …", "… unlocked …", "… force-released the lock on …", "… promoted … to …", "… demoted … to …" |
| Changes | "… reverted … to rev N", "… edited … (fields)", "… authored …", "… re-authored … from chat", "… applied a change to …: title" |
| Scenarios and backlog | "… added a what-if to …", "… set aside a suggestion on …", "… reopened a suggestion on …", "… queued a what-if to make permanent on …", "… added a change request to …" |
| Data | "… updated data integration on …", "… downloaded the Excel template for …" |
| Permissions | "… granted role on … to …", "… revoked …" |
Each row also shows the date and the revision, and a robot mark when RIA or an agent did it. The log is append-only: removing old versions never removes events.
Limits
- History shows 10 turns before Show earlier.
- The audit log shows the newest 300 events.
- Going back never restores owner, organization, sharing or permissions, and never crosses a later data edit.
Related
- Read a model's record: where History sits
- RIA's proposals: changes RIA proposes, which keep a version when applied
- Share and govern: locks, which block going back
- Models: the row menu with History and Model settings
Change a model
Tell RIA what to change about a model in its conversation, decide each change it proposes, make a what-if permanent, and bring in an updated workbook.
The model's evidence
Show someone what a built model rests on: where each figure came from, what a check of the result flagged, and the documents to hand on.