[DMN Modeler] Import

Features described on this page

Feature

Hosting Type

Release Version

Blogpost

Import from Local File System

SERVER | DATA CENTER Cloud

initial

 

Import from Confluence Attachment

SERVER | DATA CENTER Cloud

initial

 

Import from Bitbucket

SERVER | DATA CENTER

3.10.0-ENTERPRISE

BPMN MODELER ENTERPRISE 3.12.0

Import from GitLab

SERVER | DATA CENTER Cloud

3.10.0-ENTERPRISE

BPMN MODELER ENTERPRISE 3.10.0

Gitlab synchronization with BPMN and DMN Modeler Enterprise

Import from GitHub

SERVER | DATA CENTER Cloud

2.19.0-ENTERPRISE

 

Import from Local File System SERVER | DATA CENTER Cloud

There are two different ways to import diagrams from the local file system in the diagram editor:

  1. go to File → Import → From File and select a .dmn file from your file explorer.

  2. drag and drop the file directly onto the diagram editor canvas

 

image-20240801-131040.png

 


Import from Confluence Attachment SERVER | DATA CENTER Cloud

Diagrams from other Confluence pages can be imported via File→ Import from Confluence page.
In this case you can choose whether you want to import all diagram versions or only the latest one using the Carry Version History toggle. Note that older versions of the exisiting diagram are not lost but are still accessible in the version management and dropdown after the import.

 

image-20240801-131130.png

 

Note that diagram versions imported from another Confluence page are not directly published on the Confluence page, even if you entered the diagram editor from the Confluence page view. You can change this by clicking Publish this version now in the message box showing up directly after the import. For more information on how versions are published on the Confluence page please refer to the section "Published and Unpublished Versions" of this manual.


Import from Bitbucket SERVER | DATA CENTER,
GitLab SERVER | DATA CENTER SERVER | DATA CENTER,
and GitHub SERVER | DATA CENTER Cloud

DMN diagrams can also be imported from your Version Control System (VCS). This way, you can always pull in the latest revision that lies in your VCS and keep on modeling straight away in Confluence - no need to switch tools!

To import a diagram from your VCS, you need to open the diagram editor go to File > Import from VCS, and choose your respective VCS. Now you can search for a repository, choose a git branch or tag, and select a .dmn file from there. To be sure, you can load a preview of the selected diagram, or you can compare it with the latest version of the DMN diagram in Confluence (if one exists), to see the differences. The screenshot below illustrates this dialogue using GitLab as an example:

 

IMPORTANT: The diagram will be copied once from the VCS to Confluence. If you make changes in Confluence, it will not be synchronized back to the VCS. Likewise, changes and new versions from your VCS are not automatically copied to Confluence.

Optional: It might happen that you import the same diagram from the same source multiple times, or even in a regular manner. For these cases, you can save your search/configuration from the Import from VCS dialog as diagram settings. If you do so, these settings are suggested as a preselection the next time you come to Import from VCS. However, they can still be changed before importing the diagram. They are only meant to save you time when you are often using the same configuration.

The default VCS sources can also be managed in the Diagram SettingsFile > Settings).