Right now the converter adds all present input Pins as required in the created Assignment in case of a set action (e.g. set Sensitivity.Public = TRUE). This is done because the WebEditor has no option to specify which pins are required.

This however leads to cycles in the DFD where they shouldnt be (as can be seen in the WebEditor example model).

Short term i suggest we only add Pins as required that are actually named (e.g. set Encryption.Encrypted = request.Encryption.Encrypted). This however still means that WebDFD and DFD Metamodel are not semantically equivalent and information can get lost when transforming from one to the other.

Long term the WebEditor needs logic that allows us to specify the required input Pins for a set assignment (e.g. set Sensitivity.Public = TRUE when request).

PS: Is there a reason issues are disabled in the Converter Repo?