enhancement
major
minor
defect
minor
#26484
In-app template for grid and tables: Function "Verifier for use as list item" does not get component model
#26885
Constraints on declarative forms with arguments from a container reference lead to errors for new elements
#26922
With generated subject classes, a default provider of an attribute in a non-structure class does not get a create context
defect
minor
#25613
BPE: Creation of new process instances with mandatory fields not possible
If the type of a process instance defines an attribute that is marked as a required field in the model, that process cannot be started. The error message reads, "The attribute ... must not be empty," even though a value was entered in the GUI.
Analysis
After the introduction of Form Editor-based forms, fields are created twice in the form context, but only one variant is displayed and populated on the GUI. Logically, this leaves behind an unfilled (invisible) required field.
Workaround
You must not define required fields in the model for process instances (specifically, concrete derivations thereof); instead, you must explicitly set these fields to “required” in the form editor, if necessary.
Code Migration
- Any recorded test cases involving workflows must be adjusted: <named-member name="formDisplay"/> must be removed from references to workflow fields.
Test
- /com.top_logic.bpe.app/src/test/java/test/com/top_logic/bpe/app/scripted/TestMandatoryProcessAttributes.script.xml