Publish a change or go back to a version

Nothing you change in Studio reaches your team until you publish it. Each publish keeps a numbered version, so if a change does not work out you can go back to the version before it. The change history lists every change: who, when and what.

Before you start

• You need the right Manage Studio (fields, layouts, statuses, rules, templates).

Steps

To publish a draft:

1. Open the editor where you made the change (fields, layout, statuses, an approval limit or a template). The bar at the top shows Draft not published and Only you see it until it is published.
2. Check the Preview.
3. Type what changed in the note box (optional) and select Publish. The bar shows Published · version n.
4. To drop the draft instead, select Discard draft.

To go back to an earlier version:

1. In the same bar, open Versions (n).
2. Find the version you want and select Go back to version n. The earlier version is published again as a new version.

To read the change history:

1. Open Studio → Change history.
2. Read each line: When, Who, the Item with its version, and What changed (fields added, changed or retired, or document parts).
3. On a publish, select Go back to version n to undo it. Select Older changes to see more.

Good to know

• Drafts waiting are listed on the Studio overview and on Today for people who manage Studio, so nobody forgets one.
• Two people at once. If someone published the same item after you started your draft, your publish is refused with studio_stale: reload and make your change again.
• Going back keeps values. Fields added after the version you go back to are retired, not deleted, so no value is lost.
• Discarded drafts, the owner acting above an approval limit, and saved-view changes are in the history too.
• There is no separate test copy of your organisation: the preview and the versions are the safety net.
• Related: Add a custom field, error studio_no_draft.