Version history for deliverables, and a clearer restore

Deliverables now have a version history. Every time a specialist publishes a deliverable, that version is saved, and anyone who can open the deliverable can see the list from its menu. Editors can restore any earlier version: its pages and data sources come back, and if those sources differ from the ones that last fetched its data, it fetches again the next time it opens. Apps, workflows, and skills share the same redesigned history.

How it works

• Nothing is lost on restore. Restoring a version adds it to the top of the history as the newest version. Every version before it stays listed, including the one that was current, so you can always go back.
• Grouped by day. Versions are listed under Today, Yesterday, or their date, each with the time it was saved and whether a specialist published it or it was restored from an earlier version.
• Confirmed in place. Restore asks once more in the same row instead of opening a second window, and an app rebuilds on its own after a restore.
• Everyone can look, editors can restore. Members who can view an app or workflow can now open its history too. Restoring stays with its editors, and the button says why when you can't.

Also shipped

• Restoring a version that was itself a restore now brings back exactly what it showed.
• The version you restore from no longer drops out of the list.