Missing Input and Output Variables for productionTasks

[FlorianDue]

In productionTasks it is not possible to define/declare input and output variables. As a result, additional tasks must be defined for the use of conditions, even if the condition is only applied to a single service. This makes the petri nets unnecessarily complex, as places and transitions are introduced that are not required for the process.

As possible solution could be to either declare variables outside of Tasks as global variables (data type of the variable, variable name)

cr_data_type cr =
      {
            parts_count = 3,
            sheet_parts = [0,0,0]
        }
Task productionTask
    In cr:datatype
    Loop i To cr.parts_count
        Painting
            In
                cr.sheet_parts[i]
End

or it should be possible to define literal values as input for a production task, as allowed by all other defined tasks

Task productionTask
    In 
        cr_data_type{
            parts_count = 3,
            sheet_parts = [0,0,0]
        }
    Loop i To cr.parts_count
        Painting
            In
                cr.sheet_parts[i]
End

A similar concept should exist for output variables, so that the result of a pfdl process can be transferred to further processes

[ptrdtznr]

Not sure if I got it correctly. You are looking to define global variables and you still want to define/assign them as a variable in productionTask?

Nevertheless, what could be possible is that global variables are accessaible within task without the explicit definition/assignment.

[FlorianDue]

It is particularly about enabling input/output variables for the production task. Global variables would be one possibility to implement this

[ptrdtznr]

@maxhoerstr what do you think?