permalinkManage object view versions

Changes you make to an object view are stored as versions, with a separate history for each object type. A version can contain several changes, such as adding, editing and deleting widgets or tabs. Here are some of the things versions enable you to do:

• Iterate on object views safely by saving your changes as incremental versions
• Control which of the versions is published and visible to users
• Republish older versions in case things go wrong
• Collaborate more efficiently by adding descriptions to versions

permalinkUsage

permalinkSaving new versions

To save a new version of an object view, you must first edit the object view (for example, change/add a widget or a tab) and then save those changes.

By default, when a new version is saved, it will also be published to users because automatic publishing is enabled. You will see a Save and Publish button in the header.

If the automatic publishing is disabled, the header will have a Save button instead and this will simply save a new version without publishing it. Read more about the automatic publishing behavior or how to disable it.

You can also add a description to your version either from the top left of the header or in the versions history panel.

permalinkNavigating the history

To see all changes that have been made on an object view, you can navigate to the version history panel from the editor header navigation in the top right. Here you will see a chronological list of all versions, with the newest one in the top and oldest one in the bottom. The currently published version has a green tick icon next to it and the versions that were published before it have a gray tick icon.

You can see when a version was saved, who is the author and which version it was based on (the version the author started making their changes on top of). Additionally, you will see a description for the version if the author has added one.

To see the full description, and more details about a version, you can hover your mouse cursor over the item in the list. In the card that appears on hover, you can also edit the description, or add one if there isn’t one yet.

The version history panel will also highlight which version is currently published to everyone at the very top of the panel.

The history panel will show you the 20 latest versions when opened. You can view older ones by navigating to the bottom of the list and clicking on the Load more button. You can only view up to 200 past versions.

permalinkPublishing new versions

If automatic publishing is turned off, you need to explicitly publish your version to make it available to users.

Once you’re happy with the changes you’ve made and have saved them, you can go ahead and publish your desired version to users by clicking on the Publish button in the editor header, or in the version hover card if you’re in the version history panel.

permalinkPreviewing

You can preview any version simply by clicking on one in the version history panel.

However, if you have unsaved changes, you must first either save or discard these changes to preview a version.

permalinkRepublishing older versions

You can republish previous versions of an object view. For example, if a newer version of an object view is broken, you can republish an older version of the object view that you know is working. To republish a previously published version, you can simply republish it either from the version history panel or from the editor header, if you’re previewing it. This will then duplicate that version to the very top of the version history list to retain the chronological order of actions.

permalink Automatic publishing

By default, automatic publishing is enabled on all object types, which means each new version will also be published when saved. To disable this, turn it off either from the dropdown next to the Save & Publish button in the header, or the History panel.

If your object view is being actively used by many users and/or there are multiple editors collaborating on the view, then we recommend disabling automatic publishing. This lowers the chances of breaking views or workflows for users and improves collaboration by making it clearer what everyone is working on.

Only editors with publishing permissions can change the automatic publishing setting.