Migrating a TopLogic application from 8.0.0-alpha1 to 8.0.0-alpha2
Audience: an AI coding agent (or developer) upgrading a TopLogic application project.
Sources: release notes https://dev.top-logic.com/tl/content/releases/TL_8.0.0-alpha2/ and the
TopLogic Trac tickets of milestone TL_8.0.0-alpha2 (ticket numbers are given as #NNNNN; the
per-ticket page is https://dev.top-logic.com/tl/content/releases/TL_8.0.0-alpha2/NNNNN/).
8.0.0-alpha2 is a small maintenance release. No ticket of this release is flagged
RequiresMigration; apart from the version bump there are no migration steps.
How to use this document
- Do the version bump (section 1) and then run the verification checklist (section 3).
- Section 2 lists behavior changes for information only; they need no change in the application.
- Ticket descriptions on Trac are partly German; this document translates the relevant content.
1. Build and platform
1.1 Version bump — mandatory
Set the TopLogic version to 8.0.0-alpha2 (parent tl-parent-app / tl-parent-core version, or
the tl.version property).
Detect:
grep -rn --include=pom.xml -e '8.0.0-alpha1' .
2. Further notes (no action required)
2.1 Flow chart: configurable initial zoom (#29229)
The component flowChart (template tl-graphic-blocks-server/flowChart.template.xml) has a new
optional property initialZoom (type com.top_logic.graphic.flow.data.InitialZoom). It sets the
zoom applied on first display, on a model change and on refresh. Values: FIXED_50, FIXED_75,
FIXED_100 (default), FIXED_150, FIXED_200, FIT_TO_PAGE, FIT_TO_WIDTH, FIT_TO_HEIGHT
(fit, never enlarging above 100 %), and FIT_TO_PAGE_ENLARGE, FIT_TO_WIDTH_ENLARGE,
FIT_TO_HEIGHT_ENLARGE (fit, also enlarging). Existing layouts without initialZoom behave as
before (100 %). Interactive zooming is unchanged. Optional — use only if asked.
2.2 Read-only attribute with fallback value shows the fallback (#28805)
For attributes with storage "attribute with fallback value" (AttributeWithFallbackStorage), a
read-only (immutable) field now shows the effective value, i.e. the fallback value when no
explicit value is stored; before, it showed nothing. To support this, AttributeUpdate now
initializes the visibility (disabled/mandatory) of an update before its value
(createUpdate(), editUpdateDefault(..), editUpdateCustom(..)), so a storage's
initUpdate(..) can query update.isDisabled(). Custom storage implementations that relied on
the old order should be checked, but no change is required in general.
Detect (only for reviewing custom storage implementations):
grep -rn --include=*.java -e 'void initUpdate(' .
3. Verification checklist
mvn clean installof the application (with tests if possible).- Start the application and read the startup log for configuration errors.
- Log in and open the views that use flow charts and forms with fallback-value attributes.
- Report to the user every step that was skipped or needed a decision.