LTS Versions 11.210

In selections with the selection filter "empty" or "not empty", unexpected results occurred if empty strings were in the filter field. The filter expected NULL as a value in the database when filtering for "empty".

When importing certain floor schemes, an object reference error could occur if the import was not carried out directly after the geometry import. Area data was then not imported.

When printing cards, the sorting of lists that were, for example, filled with work steps and included in an LL print form was not always correct.

The coloring of the elements in the calendar (e.g. by type of measure or status) did not work correctly.

With a certain configuration of data localities, an error could occur when saving transactions in connection with the system package 'Operations' (1770): "Record cannot be saved: ExecuteNonQuery ..."

Creating PDFs for compound selections with a large number of CAD drawings did not always work correctly.

When importing stacked hatchings, e.g. in a logo, the display could be incorrect. The logo was displayed blackened, for example.

Regardless of whether it was turned on or off, hatching was invisible in the CAD viewer in some data worlds.

When importing new DGN drawings, stamps could sometimes be incorrectly positioned.

When duplicating a data world, an error "Object reference not set to an instance of an object" could occur, which in turn led to a crash of DataManagement.

When using the DMS and displaying documents, tags were retrieved multiple times. In addition, the documents were always reloaded when changing card areas within a record. When displaying a very large number of documents, this could have a negative impact on performance.

When importing test data, it could happen that import specifications were not applied correctly.

When generating an HTML email using the mail building blocks, the content was not correctly encoded and transferred to the email client.

If the following parameters were used together in a series of appointments:

• Validity correction is "Earlier"
• Update on appointment basis

it could happen that appointments that were corrected were deleted.

Fixed

Please also do a data world update.

For memo fields, you can also write the text in an additional text window. There was an error here: If the text window was used to create the text, then closed and the card saved, the text was deleted from the memo field and not saved.

TN-2412-00077

TN-2412-00316

When using the building block 'BrowserDialog', unexpected behavior occurred in which fields were deleted.

There is an additional trigger in the 'Data' area that is triggered when a person logs in or attempts to log in.

Parameters are:

• User
• Login source (fat client, web, etc.)
• Client
• Auth result (or the trigger only triggers for successful logins)

When installing DataManagement via ClickOnce, the installation could fail with the following error message: "The remote server returned an error: (404) Not found".

If the System Rule Editor was opened first without first opening the DataManagement, subsequently calling the DataManagement led to a crash of the DataManagement.

Referenced packages have been updated to implement a security update with a moderate severity rating. It is strongly recommended to upgrade to this version.

When displaying all users of a role in rights management, the first record was invisible, i.e. it was displayed one record less.

When creating customer packages (with package number 1), an error occurred and the System Rule Editor subsequently crashed.

Mobile

The new waveware MOBILE 2 app has left the BETA development stage and is released for productive use as of this version. The app can be installed via the Google PlayStore or Apple AppStore. To operate the new app, at least one waveware server 11.200.6798 (LTS release April '24) is required. The waveware MOBILE 1 app used libraries from Xamarin, whose support was discontinued by Microsoft. The new waveware MOBILE 2 app is based on .NET MAUI and can be installed and used parallel to the waveware MOBILE 1 app.

If you are already using waveware MOBILE 1, we recommend upgrading to the new app as soon as possible. Due to the discontinued support for Xamarin by Microsoft, Loy & Hutz will also discontinue support of waveware MOBILE 1 with this LTS release - the last supported version of waveware MOBILE 1 is therefore 11.210.141.64 (or another version from this LTS series). The next release (expected November '24) will no longer contain a waveware MOBILE 1 client. Further information: 'Mobile: Version Change and Upgrade Information'.
waveware MOBILE 2 Documentation: 'waveware MOBILE 2'.

Since new waveware versions may be released at irregular intervals, updates have been included in the waveware notification system. When a new version is released, all users with the global right 'Receive update notifications for waveware' will receive a notification.

New versions are checked automatically in the background. If a new version is available, the waveware Service Center can be opened directly by double-clicking on the notification.
Using Supervisor Options (System / Additional Basic Functions (1861) / System / Update Notification) you can switch the notification on and off and specify whether the update check should be limited to LTS versions.

The mail building blocks OpenLocalMailClient, OpenLocalMailClientWithMultipleAdresses, OpenLocalOutlook and OpenLocalMailClientWithMailDraft enable emails to be sent using a local mail program.

If the locally installed Outlook client was used, it was previously necessary to have .net Framework 4.8 installed. This no longer works with newer versions of Outlook. The building blocks mentioned have therefore been changed so that they generate a temporary *.eml file. This file is then opened by the program that is associated with this file extension (normally Outlook). The eml file can be opened by both the new and the old Outlook.

The time periods for LTS releases have been adjusted. Previously, LTS releases appeared at intervals of 6 months and were provided with critical security updates every 12 months.

Starting with this release (October '24), LTS releases will be released at 12-month intervals and will be provided with critical security updates every 18 months. This means that major updates only need to be performed every one and a half years in order to be able to operate the version safely with smaller updates.

When inserting multiple documents into a card at the same time using drag & drop, it could happen that an inserted document was not linked to the correct record due to the stacking of the cards. This was visible on the relevant 'Document' object in the 'Assignment' transaction, as the field of the assigned ID ('Object ID' or 'Transaction No.') was empty.

To edit the content of a memo field better, the text can be opened in a separate window. The context menu of this separate window differed from that of a regular memo field, so that, for example, the phrase catalog could not be called up.