draw.io for Confluence Server 5.3 offers a first look at the mass Gliffy import option, currently in beta. For now, we recommend trying it out on a copy of your Confluence spaces before applying in production. If the import fidelity of any import is not good enough, please email the Gliffy diagram (it's an attachment on the page) to email@example.com.
Navigate to the draw.io plugin admin screen, CONFLUENCE_PATH/admin/drawioConfig.action, and click on the "Diagram Import" tab. You'll see this:
You'll be told how many pages contain Gliffy diagrams. To start the import click "Import" and "OK" on the confirmation dialog. Importing will take some time if you have a lot of diagrams. On a low-end server, allow 1 minute per 10 diagrams as a rule of thumb.
Once the import is complete, all your Gliffy diagrams will be replaced. The import is all or nothing, if there are problems during the process, no diagrams will import. We also do not delete the original Gliffy diagram from the page attachments.
If you have questions about the content in this post, please email us directly at firstname.lastname@example.org.
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.
draw.io for Confluence server 5.0 introduces the ability to create and share custom libraries within draw.io. Within the draw.io editor select File->New Library to create just that:
This will bring up the custom libraries dialog:
Having populated and saved your custom library it will then appear as a library in the left hand side library panel:
You can drag shapes from this new library into the drawing area as per any built-in shape. Custom libraries also have three small icons at the top right:
Add the current selection in the diagram to the custom library (see below).
Edit the custom library, this brings up the library dialog once more.
Close the custom library (this does not delete the library).
The add selection option enables you to select as much of the diagram as you wish, click the "+" icon in a custom library and that selection will be added to the library as a single shape to drag and drop back as you require.
File->Open Library shows you all available libraries, showing the name, author and a preview:
Select any library on the left hand side and press "open" to open that custom library in your editor. Also, custom libraries persist in the libraries panel per diagram, so if a diagram is using certain custom libraries, those always open with the diagram.
If your company need formal auditing for Confluence that includes diagrams within documentation, traceability of who changed what, or you simply don't like what someone else has done to a draw.io diagram
draw.io v3.9.0 introduces in-place preview and restore of revisions for each diagram. Click to edit the diagram and once in the editor select File->Revision History.
You'll be shown a list of all revisions of the diagram
You can select any revision and click preview, this will display the diagram in-place so you can quickly check it.
Selecting and clicking open will replace your diagram of the latest version with a new revision (once you save it).
We've always got a packed roadmap of improvement for the draw.io for Confluence plugin, we thought we'd share some of the items currently in the roadmap in the short and medium term.
1) First is the diagram viewer.
There have been positive and negative comments about the viewer. The positive are that it's a vector drawing and it's zoomable and pannable. The negatives are that sizing is too hard and that it doesn't look like an image in the Confluence page when there's no interaction with it. So, in the default page, unless you hover next the diagram, it'll appear like an image.
In page edit mode the diagram appears as:
Clicking on "settings" (yes, that should be edit) brings you to the macro editor:
This flow is excessive and having to decide the width/height/auto-sizing is wrong. Instead we are going to follow the Confluence image settings functionality:
This will be more familiar to users, plus enable them to size with less clicks in a more intuitive manner.
2) Next is Gliffy import. This is a large task, but is making progress. The process for importing will be to run a batch converter tool. The tool will take all Gliffy data, import it and replace the Gliffy diagrams with draw.io diagrams. Note that it won't delete the Gliffy diagram data, so that will still be available if you wished to revert. Here's an example Gliffy diagram:
And how it currently looks in draw.io converted:
3) Next, the attachments we store. Currently, like Gliffy, we store a PNG and XML file attachment for every diagram. That's wrong. We're going to change to only storing a PNG and embedding the XML within that.
4) Plugins are functional in the draw.io plugin (we might need to rename them to avoid confusion). draw.io plugins allow any part of the diagram editor to be customized. Currently, they are installed on a per-browser basis. This will change to make them only installable by admins who can choose which groups have which plugins active by default and whether users can select plugins.
5) Custom libraries have been available in the online version for some time, we're aware they need to go into the plugin, also.
6) The online version also has support for Mathematical Typesetting, that will be ported to the plugin.