In the version we will release in Fall 2024, there are some changes that are no longer compatible with previous versions. Additionally, a manual update is mandatory.
Once the Fall 2024 version is released in the marketplace, the following changes must be taken into account.
Global templates have been replaced by space templates
This is the biggest change. The global templates (also known as blueprints) are no longer available. Instead, we have transitioned the templates into space templates. The major advantage of this is that you can now use these templates in automations (e.g., automatically create a Customer Journey in Confluence when an epic is created or reaches a certain status).
For space templates to be created, the respective space must be enabled for enbl.it. A space admin can do this by selecting the language (German or English) in the space settings (1) and activating enbl.it in the space (2). The templates will be copied into the template area in the correct language. These templates should not be modified, as they may be overwritten during updates.
Page Structure
When enbl.it is activated for one of your Confluence spaces, a page structure will also be created (3). This helps you organize the space with structured content. A macro is available to automatically copy newly created pages to the correct location within the page structure for easy subpage creation.
Quick Actions
To help you quickly create one of the enbl.it artifacts, you can find Quick Actions (1) in the sidebar. This allows you to create an enbl.it artifact without having to navigate through the content tree first.
Objectives are dead, long live Product Goals
Previously, enbl.it enforced a strict guideline on how artifacts had to be linked together. One significant issue for many of our customers was that an initiative could only be linked to a single objective.
We’ve addressed this in the current version by replacing objectives with product goals. Product goals can now be linked to one or more initiatives and are no longer part of the hierarchy but instead stand above the structure of initiatives, customer journeys, and personas.
The direct link between initiatives and customer journeys, however, remains unchanged.
Customer Journey Repository
This brings us to the next enhancement. In the page structure, there is a new entry called “Customer Journey Repository” (1). The idea is to make it easier to manage customer journeys in this repository initially. From here, you can conveniently create new customer journeys (2) and later move them into the appropriate initiative.
This repository can also be the target of automations, such as Jira automations, Confluence Whiteboard, or Confluence Databases.