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

7.8.4
TopLogic Release

2024-09-27

Enhancement

Major
#28209
TLScript: fill() also for strings
#28245
Instance editor: Generic form display for all types
#28267
Use transient objects as jump target
Detail
#28218
Visual marking of the handle to adjust the size of a layout
#28251
SecurityStorageExecutor for PostgreSQL
#28256
Configure Toolbar inApp
#28261
Migration processor invert-link-table: Enable restriction to individual reference
#28274
"Column with buttons" should not be exported
#28276
Offer local host name as alias
#28279
Action after selection in selector component

Bugfix

Major
#28227
Dialogs get +100 size for the core theme, regardless of the unit of size (px, %)
#28252
Most engine-provided views cannot be incrementally extended due to final="true" in layout XML
Detail
#27131
IllegalStateException: Can not set max validity '657' to frozen chain
#28093
Form initialization for read-only fields is ignored
#28190
Attributes of type "Color" are not displayed correctly in tables
#28216
The monospace font is not used in code blocks
#28222
DisplayAnnotations.isEditable() returns false for mandatory fields
#28228
AttributeUpdate does not take mandatory annotation into account
#28231
Browser crash due to Infoservice
#28236
Missing progress bar in progress bars
#28242
Error when value of drop-down control is updated in view mode
#28243
A calculated attribute that is marked "mandatory" is displayed as editable
#28247
Calculated color attributes are editable in Grid
#28253
Allow to inline layouts from Maven command line
#28257
NullPointerException instead of error message for invalid override in model file
#28258
Column selection in memory annotation for foreign key storage does not provide a meaningful selection
#28262
Declared API of SelectionPartModel should be completely "public"
#28268
Popup dialog with tree table for selection not usable
#28273
Script Recorder records expression as names for enclosing, nameless layouts
#28275
Error in Util.newOrderValue() may result in no ownerOrder being found
#28277
Rendering error for tabs with tooltip
#28284
Error if autoconf folder does not exist and the migration service tries to create a schema file
Bugfix

Detail

#28273

Script Recorder records expression as names for enclosing, nameless layouts

Code migrationScriptRecorder

If you create a layout in an object selection (tile layout, regardless of type) that consists of an enclosing layout and child layouts, the enclosing layout typically has no name.

If you now want to record a test with the script recorder, for example, the missing name leads to problems.\\ If you edit a field of a child layout, the script recorder records a tab path that is structured similarly to the following:

tab-path="1st level > 2nd level > [none(path/to/enclosing/contextTableInnerLayout.layout.xml#InnerLayout).title] > 4th level"

If the step recorded in this way is executed, the following error message appears

Missing resource '[none(path/to/enclosing/contextTableInnerLayout.layout.xml#InnerLayout).title]'.

Test

First you have to switch to design mode.\\ Then click on the burger menu in the main table bar (in the demo the bar with e.g. "Technical demo" and "Structures") and select **Add tab**.\\ In the new tab add a new component via the +, select **Tiles**.\\ After the creation click on the + again and select e.g. **Table as tile context**. (Other variants are also possible)\\ For example, **Person** can be selected as the type here.\\ Now click on an element of the tile view and then on the + in the top right-hand corner. You must now select **Layout** as the component.\\

Now click on the + for one of the component placeholders. Any element can probably be selected here, for the sake of simplicity we will now select **Select**. In the configuration, it is now only important to select the elements of the list, for example all(`Contacts:Contact.Person`)

Check whether 2 options exist (if not in Administration > Development > Model Editor > TopLogic > Contact > Contacts > Contacts > People > Person, create a new instance).

Now start the **Script recorder** under **Developer options**. In the script recorder, click **Start recording** (the red dot) and change the element in the newly configured view. In other words, select a different person when selecting our example. In the script recorder, the tab path should now be similar to the one shown above.

Code migration

Existing scripted test cases that navigate in tile views with dynamic object tiles must be adapted. A dynamic object tile is now always displayed with {0} in the recorded path instead of the possibly non-existent name of the tile component.

  • 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