Glossary User Guide - Version 3.4.1

 

Migration of data storage model

In this release we are moving to Active Objects, the new ORM (object relational mapping) layer to manage persistent data in Atlassian (You can read more about Active Objectis within this link)

This implementation will provide us better management of content stored by Glossary in order to expose and reuse them easily after. Active Objects enables easier, faster, and more scalable data access and storage than the existing Bandana and PluginSettings APIs.

This change does not impact features or the display of Glossary elements. It will only engage a migration operation during the installation to move data from old storage model to new database tables.

Highlight Abbreviations and Synonyms

To enable highlight of synonyms and/or abbreviations, a new parameter has been added to space configuration as displayed in screenshot below:

When selecting one of those options or both, pages content is highlighted either if it's defined as a word and as a synonyms and/or abbreviations.

You can find an example of highlight content below:

(lightbulb) Please note that if content is defined both as a term and an abbreviation or synonym both definitions will be retrieved and user can browse them.

Enable/Disable highlight per space

You can enable or disable highlight per space from Glossary Space configuration.

If disabled, no "Book" icons will be displayed in the space and auto-highlight functions are disabled.

(info) By default, Highlight is enabled for each space where glossary has been recently created.

Global Glossary configuration

To configure globally your add-on, you need to navigate to add-ons listing > Glossary add-on > button "Configure" as displayed below:

When you click on this button, a configuration interface is displayed. This interface enable user to:

  • Enable/Disable Glossary functionalities for multiple spaces
  • Enable/Disable Glossary highlight for multiple spaces

(warning)  Archived spaces in Confluence won't be displayed in the list.

Disable Glossary functionalities per space

Disable Glossary features per space will results on the following:

Space does not contain GlossarySpace contains Glossary
COMMUN
  • No Blueprint Glossary will be available to create new pages based on it
  • Glossary Configuration panel is no more available
  • No highlight (based on click or automatically) is available
  • No "add term" from highlighted text is available
  • Terms for disabled Glossaries are not available in global search

(info) If Glossary exists prior to disable action, glossary pages remains available so are the Glossary term Macros. User can hide them by applying a page restriction on the Glossary page.

To change current setting, you must select the link "Change the configuration" on the top of spaces listing. This will open the following dialog to select the corresponding spaces:

This dialog let you select all spaces in once or choose one by one.

Disable Highlight per space

Highlight button in space pages will be hidden and auto hoghlight will be disabled as well.

Please note that any modification in this section will affect space configuration and set it to false. 

Support of German localization

This release included a very significant feature "German Localization" which has been requested by many of our customers for some time now. 

You can contact us or raise to our attention any missing or incompatible translation via our issue tracker.

Bug fixes

Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.