Process input data support

[sbuettner]

Problem you would like to solve

The modeler supports and infers available process variables and data for output tasks based on output mappings and example data. This helps to support users when writing FEEL expressions for modeling purposes inside the same process.

When connecting processes via calling activities its opaque to the caller which data is expected from the process to call. In the following example the caller provides proper input mapping but its a tedious process itself as one as to make sure that all process variables that are used somewhere in the called process are covered.

It would be great if the modeler could infer the required process variables and support users during the input mapping.

A feature like this would also help when running processes from the modeler to prefill the input variables json.

Proposed solution

The modeler could infer required process input variables based on the data used in the process to call by analyzing all consumed variables inside the model. A more explicit approach would be some kind of process input schema meta-data attached to the start event(s)

Alternatives considered

There is currently no support for process input schema but maybe something simple and similar to the example data could help if that could be attached to start events.

Additional context

No response

[nikku]

Thanks for opening this issue.

This looks to me like another case of project / process application awareness.

CC @christian-konrad

[nikku]

Moving to backlog for the moment.