Input/Output Variable Mapping

Camunda 7 Topics Discussion & Questions
8

Hi Mike,

Thanks for explaining your use case. I’d like to propose two alternative solutions:

  1. Instead of the tasks SUCCESS and FAILURE, you could have execution listeners on the sequence flow or on the end events that set a variable to the desired value (e.g. set variable process-result to either success or failure). Then query the history data by that variable. That way, you do not have tasks in the model that do not contribute to the process and are only there for technical reasons (i.e. being able to query the history).
  2. If your prefer a visual representation in the process model, then a popular approach is to use blank intermediate throw events to mark milestones in a process. So the model would look like the one below. This is maybe better than using tasks, as a task in BPMN suggests that something is being done in the process, whereas an event suggests that something has happened (in this case: the milestones have been reached). For these events, you can also use input/output mappings or execution listeners to set the desired variable.

grafik

It is not supported in the sense that data objects have no runtime semantics in the engine. However, the engine also does not complain about them. It will simply ignore them. They won’t help for the use case you explained.

Cheers,
Thorben

1 Like