major
minor
major
minor
#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.
enhancement
major
#27001
ProgressDialog: Better reaction possibility to errors in the background process
If errors occur in the background process, there is currently no way to report them (other than displaying an error message in the log). In particular, test scripts have no way of detecting an error situation, since the dialog is always closed using the same button (regardless of whether an error has occurred or not). Furthermore, it is not possible to terminate the background process due to an error without that error also being written to the application log.
Improvement
- Terminating the background process with a TopLogicException stops the progress indicator, is written as an error message in the displayed log, but is not written as an ERROR in the application log.
- If the process is terminated with an error, the button to close the dialog is "Close"; otherwise, it is "OK."
- There is a callback that is executed in the event of an error: `com.top_logic.layout.messagebox.ProgressDialog.handleFailure(DisplayContext) `, corresponding to the callback for a successful operation (`com.top_logic.layout.messagebox.ProgressDialog.handleCompleted(DisplayContext)).
Test
- No test.