TopLogic - the automated application engine
  • Releases
  • Dokumentation
  • Github
  • Discord
  1. Home
  2. Releases
  3. TL_7.7.1
  4. #27640

7.7.1
TopLogic Release

2024-02-27

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
Bugfix

Detail

#27640

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

Code migrationModelEditor

If the TLObject class is hidden in the diagram, an inheritance arrow appears in the void when a new class is created.

Hiding TLObjet is a clumsy solution anyway. You hardly ever want to see this class, it only leads to diagrams looking as confusing as possible. However, there is no way to hide it permanently - it reappears with every relayout.

There are currently options to display technical names and "table interfaces".

The second option no longer has any function at all, as there have been no table interfaces for a long time. (Option should be removed).

None of the options show whether they are selected or not. (The icon should indicate whether the option is selected).

There should be an option "Show technical superclasses" - off by default. TLObject should only be drawn in a (third-party) diagram if this is checked.

If you hide classes via the eye, this should be retained beyond a relayout.

If you currently create a new association, the diagram jumps to it and moves the association to the center. This is unexpected, as neither a relay layout nor an automatic position change should take place when a new association is created.

If you drag a waypoint on the diagram, the edge disappears during the dragging process:

Implementation

Hidden diagram elements are displayed with a transparency of 30% if the option is set to show hidden elements.

Each element can be hidden and shown. Only those elements are shown that are necessary to display the original element. If an element is hidden, all dependent elements are hidden.

Migration

If tl-engine has been checked out in the Eclipse workspace, in particular the module com.top_logic.graph.diagramjs.client, then this should be recompiled with GWT in order to obtain the latest version locally.

Test

The model editor should be intuitive to use, in particular the new functionality of showing and hiding elements should be tested.

The toggle buttons in the burger menu of the model editor should work as expected. Their icon should reflect the status of the underlying boolean flag.

When a new edge is created, the view of the diagram should not move.

After a relayout, hidden elements should continue to be hidden. The set of hidden elements should only be "emptied" when the module is changed.

Assuming that hidden elements are displayed in the diagram, the model editor should behave as follows:

  • If a type with attributes is hidden, then all attributes are also hidden.
  • If a type with edges is hidden, its edges are also hidden.
  • If an attribute is shown in a hidden type, then only its type should be shown. Attached edges and other attributes of the type should remain hidden.
  • If a type with several edges is hidden and then one of its hidden edges is shown, the hidden type should be shown and all other edges should remain hidden.
  • Get Started
  • Github
  • Discord
  • Das Unternehmen hinter TopLogic
  • Softwareentwicklung heute
  • Kontakt

© Copyright – Business Operation Systems GmbH

  • top-logic.com
  • Nutzungsbedingungen
  • Impressum
  • Rechtlicher Hinweis
  • Datenschutz
  • DE
  • Login