[WOR-2728] Add initial documentation for BPMN coverage in Mendix#10977
[WOR-2728] Add initial documentation for BPMN coverage in Mendix#10977Remcovh wants to merge 3 commits intomendix:developmentfrom
Conversation
|
|
Remcovh
force-pushed
the
Rvh-bpmn-coverage-documentation
branch
from
d0abbba to
56c02cd
Compare
| <td><a href="/refguide/bpmn-coverage/#message-events">🟢 Supported</a></td> | ||
| <td><a href="/refguide/bpmn-coverage/#message-events">🟢 Supported</a></td> | ||
| <td><a href="/refguide/bpmn-coverage/#message-events">🟢 Supported</a></td> | ||
| <td><a href="/refguide/bpmn-coverage/#message-events">🔵 Planned (11.12)</a></td> |
There was a problem hiding this comment.
Should we even mention the planned version? Apart from making a commitment, there are also a lot of feature "promised" for 11.12, I'm pretty sure not all of them will be included.
| | Intermediate Boundary (Interrupting) | N/A | | ||
| | Intermediate Boundary (Non-Interrupting) | N/A | | ||
| | Intermediate Throw | N/A | | ||
| | End | Not supported. Mendix's [End Event](/refguide/end-event/) terminates the entire workflow and aborts any ongoing parallel paths, which is equivalent to a Terminate End Event, not a normal End Event. | |
There was a problem hiding this comment.
I would say Mendix End behaves exactly as a None End, it doesn't terminate the workflow if let's say there is an least on sub-process running.
There was a problem hiding this comment.
You are right. But it does end the process (main or event subprocess) when it reaches the end, correct? So as soon as you are able to have parallel paths with their own end (maybe v2) it acts as a terminate end event?
Also, can we create a terminate by calling a microflow that changes the workflow state to abort the workflow?
There was a problem hiding this comment.
But it does end the process (main or event subprocess) when it reaches the end, correct?
That's right, and that is what a None End is suppose to do - consume a token. Whereas a Terminate End cancels all tokens in the workflow.
Also, can we create a terminate by calling a microflow that changes the workflow state to abort the workflow?
Yes, you can do that. The only thing is that the workflow will be aborted rather than completed.
4 participants
No description provided.