-
Notifications
You must be signed in to change notification settings - Fork 12
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
receiveTask instantiate
attribute is ignored
#346
Comments
Hi @paule96 , thanks for your feedback. Yes it looks you are right. We need to improve the validation algorithm in this point. |
@rsoika thanks for the fast feedback :) Let me know if I can help |
@paule96 I think I have fixed this issue. Maybe you can have a short look at the new validation method: open-bpmn/open-bpmn.metamodel/src/main/java/org/openbpmn/bpmn/elements/Activity.java Line 115 in f1d96f3
I don't know the specification by heart, but do you think there is a similar case for outgoing message flows on a Task Element? I still validate that we have at least one outgoing sequence flow - which should be correct for my understanding....? Here is the code for the new unit test: Line 42 in f1d96f3
I used you model as a reference model in this test. |
Method |
As far as I understand the code should be valid. (I'm also not so deep into the BPMN spec) So it would be good if the validation method stays like that. (both sides should be an activity) |
Ok, thanks for your feedback. We can leave it like it is for now. The validation method is very new and currently covers only some cases. I think we can improve the validation step by step in the future. Thanks again for your valuable feedback!! I will prepare a new VS-Code Extension update soon. |
For now it is working 🥳 Do we want to close this issue and make a new one for handling messages and message flows in general? |
Hi @paule96 One background note to the project structure: |
In the BPMN specification the following is written:
Page 161
But if you set the
instantiate
the open bpmn editor still complains about the misconfigured task:The following xml was used to produce the error:
The text was updated successfully, but these errors were encountered: