Separate predefined transaction boundaries from configuable ones

[ingorichtsmeier]

Display the predefined transaction boundaries on user tasks, receive tasks, ... differently than the async before or anyc after.

Maybe in a different color or in a diffent line direction (up or down).

That would make it easier for newbees to understand the influence on it.

If both is checked, (for example async before on user task), display both.

[falko]

+1

In fact, the transaction boundaries configurable with asyncBefore and asyncAfter are the only ones that are really before or after the flow node. The implicit TX boundaries of wait states are actually in the middle of the flow node behavior.

If we would again go back to a line-based visualization as we use them in our trainings and in the original implementation (see screenshot below), we could visualize the implicit TX boundaries as a line in the middle of the flow node (maybe underneath instead of directly across the shape).

The line-based visualization also gives better readability because it doesn't cover the shape.

[falko]

The original code is available here: https://github.com/camunda/camunda-bpm-process-test-coverage/blob/master/core/src/main/resources/bpmn.js-report-template.html