If you have questions about the content in this post, please email us directly at email@example.com.
In draw.io for Confluence Server 5.1 we've improved the revision handling. The concept is best demonstrated through the creation of a page with diagrams in it. First, we'll create a blank page.
Next we'll add a draw.io and a Gliffy diagram. Each diagram has a single rectangle in it with the revision of that diagram written as the label. (The draw.io diagram is on the left, the toolbar is not normally visible without a mouse hover).
One thing to note is that the viewer toolbar no longer has an edit button in draw.io. This is because we are strictly enforcing edits to happen within the page edit flow. Gliffy will allow you to edit the diagram directly from the page without a new page revision ever having been created, i.e. you can change the page without there being a unique snapshot of the page ever being made. In fact, a page revision is not created if a Gliffy diagram is edited via the page edit flow, either. Page revision 3 in the steps below is only created because the draw.io diagram is edited at the same time.
The page history is as expected for now, but let's edit the diagrams again within the page edit flow:
The page and page history appear as expected:
But when we click on "v.2" of the page:
It can be seen that Gliffy diagram macros always show the last revision of the diagram regardless of which page is displayed, i.e. is the Gliffy macro there or not, if yes, show the latest diagram. If you revert a page containing a draw.io diagram the diagram will also revert in step. One caveat is that the diagram history is only created since draw.io 5.1, so the diagram revision must be created using 5.1 or later. But if a draw.io diagram is created with 5.1+, that means it will have a correct, auditable, revision history.