11.210: Technical Changes

When defining a serial appointment, the duration can be used to determine how many follow-up appointments should be created.

The option 'How to fit the TODAY period plus [X] months to the end of the month' has been changed to 'How to fit the START DATE period plus [X] months to the end of the month'.

With the start date as the beginning, the view is more clearly defined.

Importing a defective backup file could result in the DataManagement crashing.

When displaying the mobile work step evaluation in waveware MOBILE 2, loading time was longer than average. In tests, calling a large work directive with over 150 steps took about 1 minute.

When evaluating work steps, a detail page can be opened, e.g. to enter descriptions for negative reviews. If the detail page was opened very frequently while the steps were being processed, the app could crash.

Expandable transaction lists, which displayed additional fields of the record when expanded, were not available in waveware MOBILE 2.

If the following parameters were used together in appointment series:

• Validity correction is “earlier”
• Update on an appointment basis

it could happen that appointments that were corrected were deleted.

Due to the fact that Microsoft has already discontinued support for Xamarin, Loy & Hutz is now also discontinuing support for waveware MOBILE 1. From waveware 11.210.510 onwards, the waveware MOBILE 1 app will no longer be released. Connections from the old app to the waveware system are no longer possible with this version of the waveware server. Instead, use the new waveware MOBILE 2 app: 'waveware MOBILE 2'.

The October LTS version 11.210.141 is the last waveware server version with which the old waveware MOBILE 1 app is compatible. If you want to continue using the app, you may update to a maximum of one version of this LTS series.

Protection against CSRF ("Cross Site Request Forgery") will be available from the next release, which is currently available. It will be released in December 2024, will always be switched on. Disabling this protection represents a significant security risk, so the option in the waveware server settings will no longer be available.

For protection, tokens are used that the server generates and communicates as part of the returned page. If you use Custom Pages and the 'Protection against Cross-Site Request Forgery (CSRF)' option is activated in your server settings, please make sure that the Custom Pages have been converted accordingly before the next version. More information: 'Protection against CSRF Attacks'.

Checking out and checking in documents in the DMS of waveware MOBILE 2 is currently not possible on Android due to a lack of permissions on Android.

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

The deactivation of a data world could also be carried out when the Designer or System Rule Editor was open.

If the System Rule Editor was first opened without first opening the data management, subsequently calling up the data management resulted in the DataManagement crashing.

Referenced packages have been updated to implement a medium-level security update. It is strongly recommended to update to this version.

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

When creating customer packages (with package number 1) there was an error and the subsequent crash of the System Rule Editor.

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.

When displaying the mobile work step evaluation in waveware MOBILE 2, loading time may be longer than average. In tests, calling up a large work instruction with over 150 steps took about 1 minute (in MOBILE 1, loading was completed on average after 1-7 seconds).

The expandable transaction lists known from waveware MOBILE 1, which displayed additional fields of the record when expanded, are not available in waveware MOBILE 2. These will probably be replaced by a new function.