This change is mainly to make the day-to-day workflow for implementers easier.
All flows need to end in a 'clean' way, meaning all exitpoints at some point need to be connected to either another 'regular' activity, or a 'Complete Handling' activity.
Besides the cumbersome 'click-and-drag' to connect all points, it also creates a clutter of mainly unneeded links and activities to end the flow.
What we implemented here is a pure UI change where we can quickly connect to a 'Complete Handling' activity, but not need to manually connect or have any links shown in the UI.
While already poking around in the same code area, advantage was taken to tackle two other issues that could use improvement:
For this functionality, two context menu items were added:
The context menu on activities:
When selecting this option, all unconnected exit points (e.g. regular or fault) will be automatically linked to the first 'Complete Handling' activity found in the flow.
On the flipside, if there is no 'Complete Handling' activity at all, this will not do anything except showing an error message:
|
The new visual for exit points that are automatically connected are the orange circles, like this:
To emphasize: this is a UI change only! |
If you select this option, all automatically connected exit points (e.g. regular or fault) will be cleared and be invalid again until reconnected, either manually or automatically.
Here are flow examples before this change, and after with the automatic connections applied:
A semi-fictive flow for Delta on QA.