Major
Detail
Major
Detail
#26382
Error messages "Duplicate tag name..." when starting an application in the IDE from a TL-Studio
#26405
TTypeRewriter logs warning "Unable to resolve items by external reference" also unnecessarily
#26431
Changed superclass relationship leads to changed attribute list in the form editor only after a restart
#26484
In-app template for grid and tables: Function "Verifier for use as list item" does not get component model
#26536
When rendering HTML from TLScript expressions, configured renderers are not taken into account
#26797
Transaction with user input: invisible properties of the form model cannot be assigned values (initialized)
#26885
Constraints on declarative forms with arguments from a container reference lead to errors for new elements
#26921
ClassCastException when evaluating security rules that refer to (non-structuredElement) singletons of a module.
#26922
With generated subject classes, a default provider of an attribute in a non-structure class does not get a create context
#26988
In-app documentation generator does not extract documentation for overwritten config properties
#27027
Declarative forms: SelectField disappears after upload if option list depends on mandatory property
#27042
MaintenanceJspBase should write to the log first, then to the client, instead of the other way around.
Bugfix
Detail
#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 mandatory field in the model, this process cannot be started. The error reads, "The attribute ... must not be empty", although a value has been entered at the GUI.
Analysis
After the introduction of the form editor-based forms, fields are created twice in the form context, but only one variant is displayed and filled at the GUI. Logically, this leaves an unfilled (invisible) mandatory field.
Workaround
You are not allowed to define mandatory fields in the model for process instances (meaning concrete derivations of them), but you have to set these fields explicitly to "mandatory" in the form editor, if necessary.
Code migration
- Possibly recorded test cases with workflows must be adapted: <named-member name="formDisplay"/> must be removed from references of workflow fields.
Test
- /com.top_logic.bpe.app/src/test/java/test/com/top_logic/bpe/app/scripted/TestMandatoryProcessAttributes.script.xml