#26190 Multiple drop operations per component

Enhancement

Major

#26190

Multiple drop operations per component

#27706

TL-Script: Explicit method chaining

Detail

#27260

Bad example in the documentation of revisionAt(...)

#27626

DropDown: No icons are displayed

#27700

Allow dynamically loading ES6 modules from scripts

#27721

Automatic data migration for applications without branch support

#27735

PostgreSQL: Workaround for Method org.postgresql.jdbc.PgResultSet.updateClob(int, Reader) is not yet implemented.

Nice to have

#27667

Update gstream package to gson 2.10.1

Bugfix

Major

#21471

Overwriting attributes sometimes fails

#27741

Missing developer options in the Modern theme

Detail

#27337

Documentation for tile views is not displayed

#27528

Kafka prevents logging to std-out

#27640

Model Editor: Superclass arrow is displayed although superclass is not drawn

#27661

Incorrect error handling in I18N fields

#27672

Incorrect tooltip for tabs in the toolrow

#27673

TLScript: Copy(): Copy of historical objects not possible

#27693

Import should not be possible if base themes do not exist

#27695

Attempt to create a functional object type with an existing name leads to an internal error

#27697

Automatic data migration performs migrations to non-configured modules

#27725

TL-Sync application does not start if Kafka is not available

#27729

Backward references create a separate edge in the model graph

#27744

No visual feedback for table line drop

#27745

Tree drops cannot be recorded

#27764

Meta model: Missing type for association properties

#27766

Legacy structure modules cannot be deleted in-app

#27767

No crash, when a legacy attribute filter cannot be resolved

#27768

TLScript: Fallback for untyped expressions

#27773

Crash when importing the OpenAPI description from OpenAI

#27774

Tree table row not draggable, pop-up and label are

#27776

OpenAPI: Wrong encoding when constructing JSON request body

#27803

TLScript: Copy(): Copy of historical reference values not possible

#27805

Inconsistent behavior of the TL script function union()

#27807

TL script: log() is treated as page effect-free

#27808

BPE: Error during BPMN import if <association> links are placed before the linked parts in the XML

#27809

TL-Script: Crash when filtering literal map

#27810

CVE-2024-1597: Update PostgreSQL driver to at least 42.7.2, 42.6.1, 42.5.5, 42.4.4, 42.3.9 or 42.2.8

#27811

CVE-2024-26308: Upgrade commons-compress to at least 1.26

Nice to have

#27666

State Modification During rendering error in layout tests

Enhancement

Major

#26190

Multiple drop operations per component

Code migration DragAndDrop InAppDevelopment LayoutEditor

Currently you can only configure one drop operation per component.

You cannot differentiate the operation in-app depending on where the drag comes from.
You only have one common GUI operation after executing the drop, regardless of where the drag object comes from and regardless of the type of the drag object.

Code migration

The properties of the following layout templates and components have changed as follows:

Layout templates:

table.template.xml: tableDrop now has a quantity value and is now called dropTargets
tileTable.template.xml: tableDrop now has a quantity value and is now called dropTargets
grid.template.xml: tableDrop now has a quantity value and is now called dropTargets
treegrid.template.xml: tableDrop is now quantity-valued and is now called dropTargets
treetable.template.xml: tableDrop is now quantity-valued and is now called dropTargets
tileTreetable.template.xml: tableDrop is now quantity-valued and is now called dropTargets
tree.template.xml: treeDrop is now set-valued and is now called dropTargets
tileTree.template.xml: treeDrop is now quantity-valued and is now called dropTargets

Components:

TableComponent (see TableConfig): tableDrop now has a quantity value and is now called dropTargets
TreeComponent: treeDrop is now quantity-valued and is now called dropTargets
DocumentationTreeComponent: treeDrop is now quantity-valued and is now called dropTargets

Improvement

Multiple drop operations can be configured per component.
The first operation that is possible on the respective target object is executed.
A drop operation can contain a restriction that only activates it for certain source components from which the drag object originates.

Implementation

The user can configure a number of drop handlers on a drop-enabled component. In the case of a drop, the first handler in the list that is executable is executed.

Test

Configure two drop operations in a table or tree and check that the first permissible handler is executed.