Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

https://www.youtube.com/watch?v=cCRJBDLpbVM&ab_channel=viadeeUnternehmensberatungAG

Features described on this page

Feature

Hosting Type

Release Version

Blogpost

Export

SERVER | DATA CENTER CLOUD

initial

 

Export to GitLab

SERVER | DATA CENTER CLOUD

3.18.0-ENTERPRISE

https://blog.viadee.de/en/gitlab-synchronization-with-bpmn-and-dmn-modeler-enterprise

Export to GitHub

CLOUD

Export  SERVER | DATA CENTER CLOUD

You can export your diagram as PNG, SVG and XML (.bpmn) file. This can be done in different ways:

  • in page view via the export buttons located at the diagram (BPMN and PNG)

  • in diagram editor and presentation mode:

    1. via the buttons in toolbar (XML and PNG)

    2. in the navbar via File→ Export (XML, PNG and SVG)

Furthermore, the table representation of the diagram can be exported as a CSV file via File → Export CSV while in table mode.


Export to GitLab SERVER | DATA CENTER CLOUD
and GitHub CLOUD

You may also want to export your BPMN diagram to a remote repository. A prerequisite is that the BPMN Modeler Enterprise is connected to your VCS.

To open the export dialog, press File → Push diagram to VCS.

The upcoming dialog is very similar to the “Import from VCS” dialog. Simply select your repository, select a branch and an existing file. If you would like to create a new file, select “As new File” and enter the file path, ending with the file’s name. The screenshot below illustrates this dialogue using GitLab as an example:

Remember that for each diagram, it is possible to specify a default repository, branch, and file via the diagram settings.

After pressing “Push” in the dialogue, the following steps are taken automatically:

  • A new, temporary branch named <selected branch>-BPMN-model-update is created

  • The changes are pushed to this temporary branch

  • A merge request is created to merge the temporary branch in the one that was selected in the dialogue (develop in the screenshot provided above).

  • If the merge request is acceptable, it is automatically accepted, and the temporary branch is deleted.

  • If the Merge Request is not automatically acceptable (due to running pipelines, or a merge conflict, …) a manual merge is required. In this case, you receive the following message that leads to the merge request.

Troubleshooting

You may come across the following messages:

  1. If you encounter the message that the VCS is not yet configured in the BPMN Modeler Enterprise, ask your Confluence administrator to establish a connection between Confluence and your VCS in the app configuration of the BPMN Modeler Enterprise. While this is not yet done, you see a message like this when opening the Push diagram to VCS dialog. An article for admins on how to establish a connection can be found in this manual here: [BPMN Modeler] Features for Confluence Admins.

  2. After configuring the VCS connection globally, you will be prompted to authenticate your own VCS account as shown in the below screenshot. You will need to follow the provided link, log into your VCS account, and allow the OAuth App created by your Admin access to your repositories. Once authenticated, you can push .bpmn files directly to the VCS.

  • No labels