Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enforce setting exporter when using camunda-bpmn-js #32

Open
2 tasks
nikku opened this issue Jul 23, 2021 · 0 comments
Open
2 tasks

Enforce setting exporter when using camunda-bpmn-js #32

nikku opened this issue Jul 23, 2021 · 0 comments
Labels
backlog Queued in backlog

Comments

@nikku
Copy link
Member

nikku commented Jul 23, 2021

Describe the Problem

As stated in #1 (comment) and #1 (comment) it is best practice to serialize the exporter to the BPMN file when saving a BPMN diagram. It helps to track the origin (updater) of a diagram in case of errors.

Looking at our tool landscape:

  • The Camunda Modeler does it
  • The bpmn.io Demo does it
  • Other vendors do it

Proposed Solution

  • Require exporter and version to be set when using camunda-bpmn-js
  • Setup naming conventions for integrators and document them
@nikku nikku mentioned this issue Jul 23, 2021
21 tasks
@nikku nikku added the backlog Queued in backlog label Aug 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Queued in backlog
Projects
None yet
Development

No branches or pull requests

1 participant