-
Notifications
You must be signed in to change notification settings - Fork 7
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
correlationKey does not get loaded when there is no collaboration #122
Comments
Possible fixes would include:
|
we discussed attempting option 1, and seeing if it seems to work, including for the use case where you later want to use the editor to actually create a collaboration that is visible on the diagram. we believe that adding correlationKey nodes outside a collaboration node would result in invalid bpmn xml, so that is a point against option 2. |
Adding the collaboration tag in the xml does indeed not display in the diagram and bpmn-js does not remove it on save. When a new collaboration is added, bpmn-js does add a whole new collaboration which may not be a problem really. However, it seems like there is still another issue with this approach. It seems like the correlation key is not being used on the receive side. Even when it has the MainCorrelationKey, the message name is still being used for correlation key name. |
to repro in bpmn-js-spiffworkflow:
it is the same in spiff-arena, though if you add the element back after it is loaded by bpmn js (like by saving in the message editor), it will, in fact, be saved, since the issue manifests at load time, not download time.
The text was updated successfully, but these errors were encountered: