Chris K
posted this on April 19, 2011 12:17
The Gliffy Plugin for Confluence enables you to create and edit diagrams from within the popular enterprise wiki, Confluence. The Gliffy Plugin is tightly integrated with Confluence so you can use the powerful diagramming capabilities of Gliffy seamlessly through your wiki.
New diagrams are added as attachments to pages. This means that all of your data is stored in the same manner as any other content in your wiki. If you have backup procedures and network security setup for Confluence, all of these configurations will automatically apply to any Gliffy diagrams you create.
Installing the Gliffy Plugin for Confluence is quite easy! We have easy to follow instructions on our download page.
Yes! Please refer to our detailed user manual.
To link to diagrams that were originally created on another page, you must specify the space key and original page name in the {gliffy} tag. For example: {gliffy:name=my diagram|space=ds|page=A great new way to share ideas|align=left|size=L}. If you've been creating your diagrams with the Add Diagram link, all of this information will already be in the {gliffy} tag, and you can simply copy and paste it.
You must have Administrative access to remove the Add Diagram link. On the Administration>Plugins page, select Gliffy Plugin. Disable the module with the title - "Web Item to show Add Diagram link".
You will find in depth documentation for using the Gliffy Confluence Plugin in our Gliffy User Manual.
For users of Atlassian OnDemand, please see:
Purchasing Gliffy as an Add-on to Atlassian's OnDemand
For users of Confluence in Atlassian Enterprise Hosted and JIRA Studio environments, please see:
Installing and purchasing Gliffy Plugins for JIRA Studio, JIRA Hosted, or Confluence Hosted
Please refer to the Gliffy Confluence Plugin licensing page
When you purchase a license, you are entitled to one year of software maintenance (product updates and support). Renewal licenses are sold at a discounted rate.
Our policy is consistent with Atlassian's.
Pricing is on a per node basis. For example, if you have two installations of Confluence, and you wish to run the Gliffy Plugin for Confluence in both, you need to purchase two licenses. If you plan to run clustered Confluence, you need to purchase additional node licenses from us.
New releases of The Gliffy Confluence Plugin will work with major Confluence versions that have been released in previous 2 years. For example, Confluence 2.8 was released on April 24th 2008, so new versions of Gliffy released before April 24th, 2010 will work with Confluence 2.8, 2.8.1,2.8.2, and 2.8.3. Versions of The Gliffy Confluence Plugin released after April 24th, 2010 will require a newer version of Confluence.
We'll support the Java versions that Atlassian is supporting for Confluence, as long as the Confluence version fits into our support timeline. For example, since Confluence 2.8 was the last version of Confluence that supported JDK 1.4, and Confluence 2.8 was released on April 24th, 2008, you can expect any versions of the Gliffy Confluence Plugin that are released prior to April 24th 2010 will support JDK 1.4. After April 24th 2010, we'll only support JDK 1.5 and better. This policy enables us to leverage the most up to date features in Java while still supporting versions of Java that are in popular use.
The short answer is that your Confluence license level has to match your Gliffy Confluence Plugin license level. There is a discussion on this topic in the forums.
Yes! When you download and install the Plugin, a 45-day free trial is automatically initiated.
You'll still be able to view the diagrams you already created, but you wont be able to edit them. You will not be able to create additional diagrams
You must have Administrator access to Confluence to enter license information. You will find the Gliffy License page by browsing to Administration>Gliffy Plugin Admin.
Our policy on this matches the policy that Atlassian has on this topic. Because of the low prices we offer our product at, we're unable to make changes to our EULA. The legal and management costs related to accommodating multiple EULA agreements, reviewing amendments or signing outside legal agreements is not possible. By having a single EULA that is fair to both sides, we are able to keep our costs down. If you have specific concerns about our EULA, we would love to get your feedback.
Gliffy proudly supports the open source community and offers a free license for qualified Open Source Projects.
Compare for yourself!
