With the tl-bpe module, processes can be modeled and executed. Currently, this is only possible in a completely generic view that cannot be integrated into specialized application views.

Improvement

The layout editor should offer a template with which a process view can be embedded in the application. A process view is a special form that works on a process instance as a model, can only be edited by one actor and has a next button that can be used to trigger the next process step.

• Layout templates for "Start process" and "Advance process".
• The component for "Start process" can optionally be configured with the start event of the process to be started (previously, the start event must always be delivered via the model channel of the component). However, the model channel may also be required to provide the context for the new process object.
• Process steps should be able to use the standard form (or forms defined in other process steps) (without having to make a copy of the form definition). The form layout should be adopted, but the visibility/editability of fields should be customizable.
• It should be possible to configure the label of the process button via the edge in the workflow.
• The labels of the diagram elements that are used for GUI control should be consistently internationalizable (task names, edge names)
• It should be possible to carry out your own operations when advancing (without having to paint a complicated script task after the manual task)
• The form of the advance dialog should be adaptable in order to display additional fields (e.g. "Comment"). The custom operation when advancing should have access to these fields.
• The status object that represents the current process step should be customizable (derivable) so that additional attributes (e.g. comment) can be added to this object.
• BPMN workflows in the /WEB-INF/workflow/ directory are automatically imported once when the application is started.

Test

• View in tl-demo: Technical demo > Components > Workflow