You reach any entry from an entries table — Entries in the top navigation, or a table on a directory page — and open it to see exactly what was captured. A draft stays yours to revise until you log it; a logged entry can be corrected or extended from its detail if your role allows editing entries, and every change it takes on is kept in its history.
Opening the editor
Open an entry from any entries table to see its full detail beside the table. The stream lists entries grouped by where they belong, each labelled with its number and the date it was logged.
While an entry is still a draft, it stays the editable state. Before an entry is logged you can reopen and revise it as many times as you need — filling in more fields, correcting a value, or setting it aside to finish later. You save it as a draft while you work and log it once it is complete; logging an entry walks through that flow from start to finish.
Once an entry is logged, opening it shows every field as it was submitted, in the detail covered in viewing an entry. If your role allows editing entries, the entry detail carries an Edit control:
- Select Edit to open the entry as an editable form.
- Adjust the fields you need to correct or extend.
- Select Save to keep the change, or Discard to drop it and return to the detail unchanged.
Saving records the change against the entry rather than typing over the original, so the earlier values stay recoverable from its history. The same permission is checked when the change is saved, so an entry you can open but not edit opens as its finished detail with no Edit control.
A draft is yours to revise as often as you like before you log it. A logged entry opens as its finished detail; where your role allows editing entries, open it with Edit, adjust the fields, and Save — the change joins the entry's history rather than replacing what was logged.
What edits are recorded
Every change to an entry is captured as a change history: the field that changed, its value before and after, and who made the change and when. Nothing is quietly overwritten — the history is the trail of how an entry reached its latest values, whether the change came from an edit in its detail or as the entry moved through a lifecycle.
Changes are shown in plain language, not the raw values stored behind them. A coded option appears as its readable label — a status held as code_grey_planned reads as "Code Grey (Planned)" — a linked site or person appears by name, yes/no fields read as Yes or No, and every time is shown in your own time zone.
An entry's change history is part of Pyron's audit trail. If your role includes access to the audit trail, you can review an entry's changes from the entry itself; roles without that access see the entry's details on their own. For what the audit trail covers across your organisation, see the audit trail.