合并BPM图的最佳实践 [英] Best practice to merge BPM diagrams

问题描述

我们在Java环境中使用Alfesco活动图。这些图是版本化的;我们确实使用了GIT。

We use Alfesco activiti diagrams in a Java environment. These diagrams are versionned ; we use indeed GIT.

通常我们会合并合并分支。解决起来确实很痛苦，因为我们必须比较文件的文本内容以检查差异。有时，重新应用更改要比合并更轻松。

Often we have merge conflits merging branches. This is really painfull to resolve, because we must compare the text content of the file to check differences. Sometimes it is less painful to re-apply a change than to merge.

是否存在合并这些图的最佳实践？

Are there best practices to merge such diagrams? Maybe tools to help?

推荐答案

理论上，您有不同的选择来比较 BPMN 格式：

In theory you have different options to compare process model diagrams in BPMN format:

• 比较两个BPMN文件-包含纯xml-使用任何现有的文本比较工具或IDE帽子，您都可以在日常工作中使用它们的源代码。


• 通过使用以下任意一种打开模型来进行手动图形比较现有的建模工具（例如 jbpm ， camunda ， kogito 等。）


• 或通过生成图像并进行比较。


• 使用提供以下功能之一视觉差异，例如 bpmn-js-differ 或 BPMNDiffViz 。

• compare the two BPMN files - which contains plain xml - with any of the existing text comparison tools or IDEs hat you may use in your daily work with your sourcecode.
• do a manual graphical comparison by open the models using one of the existing modelling tools (e.g. jbpm, camunda, kogito etc.).
• or by generating images and compare these.
• use one of the tools that provides a visual diff like bpmn-js-differ or BPMNDiffViz.

要解决此问题，请不要并行工作，也可以通过不构建BPNN的流程模型简化合并，以解决此问题。 xml，但作为（java）源代码受支持，例如与 jbpm 和 camunda 。

To come around this issue keep working not in parallel or simplify the merging by building the process models not in xml but as (java) source code as supported e.g. with jbpm and camunda.

还要检查此问题重复项：合并两个版本的bpmn（xml）文件

Check also this question duplicate: Merging two versions of bpmn (xml) files

这篇关于合并BPM图的最佳实践的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！